10:05:41 <GRIMMCREATIVE> New vhs Version out :) Is this Version already the right one to use fluidcontent_core too?
10:06:14 <SuburbanWorrier> bjo3rn: you pointed out that an error I had last week was a mere warning and shown because I had different reporting settings. Wanted to say thanks and confirm that you were right. :)
10:49:18 <xaver> only idea i have is mp4. I think firefox started the support late. ogv/ogg was the first support
10:49:33 <xaver> tantebootsy: you are welcome to write something :)
10:50:13 <xaver> maybe we should replace empty sites with a tutorial howto add something ;)
10:50:58 <tantebootsy> no i think it's a missing attribute. my console says "<source>-Element hat kein "src"-Attribut. Laden der Medienressource fehlgeschlagen. fluidtypo3.org
10:50:58 <tantebootsy> Alle Kandidaten für die Ressource konnten nicht geladen werden. Medien-Laden pausiert."
11:09:35 <tantebootsy> if you have an ObjectStorage represented as checkboxes within the view you need to test if the checkbox is checked which needs to be via a viewhelper. i need this very often - maybe something for your vhs-library?
12:42:00 <cedricziel> if you dont find yourself having the problem fixed by then: ring the bell again and you can describe what's happening (or not) in greater detail. deal?
12:44:24 <Guest|59436> yes its a good deal :p but i need the dev version, is that correct?
12:48:04 <Guest|5988> hello, I write my bachelor thesis about creating templates and content elements with fluid and I want to write about fedext. Give it any materials about the history?
12:48:30 <Guest|59436> i will be back in 1 hour. THen i am going to try it.
14:18:31 <cedricziel> use the static method ::var_dump on the object
14:19:01 <cedricziel> okay Guest|59436: You may have to battle with outdated fluid templates
14:19:15 <cedricziel> please recheck all the steps neccessary to register your provider extension
14:19:48 <cedricziel> 1.) ext_tables : is there a registration on flux for your provider extension? Does it call the correct method?
14:19:58 <cedricziel> 2.) can you select a page layout in the page properties?
14:20:36 <cedricziel> 2.) please recheck your page template re the grid (same applies to fluidcontent elements) and corrct usage of flux:grid.column et al
14:21:38 <cedricziel> 4.) you can use the EXT:builder and/or flux debug setting in EM to check wether your templates are correctly using the viewhelpers
14:22:08 <Guest|59436> hm i just get an error "is not a valid template resource URI".
14:22:37 <Guest|59436> and i can choose the layouts in the page properties
14:23:11 <Guest|59436> this error is for a content element which i have built with flux
14:23:20 <Guest|59436> but this element works all the time before
14:28:21 <Guest|59436> and in the BE, all Elements are destroyed in the settings section
14:32:30 <Guest|59436> uhhm the flux usage has changed from flux:flexform.grid.row to flux:grid.row?!
15:10:17 <nimius|thephpjo> i am hitting a small issue: I am having a wizard.link field in the backend. However, it only gives me values i cannot use (e.g. only page-ids). Is there a viewhelper to render these or do i have to write one myself?
15:12:10 <cedricziel> you dont have to, but it's a viable option. you _need_ a viewhelper for those fields as the result is _always_ a number or a cryptic string you'd have to post process.
15:12:18 <Guest|59436> do i need a folder called Content in the Elements folder for my fces?
15:12:39 <cedricziel> you could as well hook into a custom controller action and process the link there
15:12:51 <cedricziel> do you have objections against vhs?
15:13:05 <nimius|thephpjo> no. I am just careful not to use to many extensions
15:13:21 <cedricziel> vhs does no harm, nor does it add any overhead
15:13:22 <nimius|thephpjo> i like keeping things slim
15:13:32 <Guest|59436> next one.. "Could not analyse class:Tx_Flux_ViewHelpers_FormViewHelper maybe not loaded or no autoloader?" never heard this errors?!
15:13:51 <cedricziel> Guest|59436: you seem to be migrating from a old state
15:13:58 <nimius|thephpjo> … i think i'll just "borrow" the typolink viewhelper. It's not that complicated
15:14:12 <cedricziel> Content templates reside always in Resources/Private/Templates/Content
15:14:21 <cedricziel> Elements was abandoned long ago
15:14:51 <cedricziel> regarding your error: did you change the namespace import accordingly to the namespaces?
17:45:35 <moger> it is no extbase controller but a utility class which is called by a signal/slot. can anyone tell me what i -roughly- have to do to take ext:view into play?
17:51:22 <GRIMMCREATIVE> question: what happend with: Development stage rewriting of LLL files in FLUX
17:52:59 <GRIMMCREATIVE> oh - do i need this now: https://github.com/FluidTYPO3/flll
17:58:14 <GRIMMCREATIVE> wow - freaky - no more LLLs now :D
17:58:58 <danilobuerger> GRIMMCREATIVE switched to flll?
19:53:42 <ltrebing> I’m using fluidcontent v3.1.0 and have an annoying issue with saving records
19:54:38 <ltrebing> whenever I save a record in the backend (no matter which kind of record it is), the system spends a lot of time inside \Tx_Fluidcontent_Service_ConfigurationService::getPathConfigurationsFromRootTypoScriptTemplates()
19:55:27 <ltrebing> is this a known issue with v3.1.0 (and Typo3 v4.5)?
19:57:24 <danilobuerger> we are dropping support for 4.5 ltrebing so i am guessing even if its an issue with fluidcontent you will probably have to fix it yourself if you want it fixed... as we are dedicated to 6.x ... sounds harsh but supporting 4.x was taking too much time
20:01:07 <ltrebing> danilobuerger: I’m not expecting a fix, just asking whether it’s a known issue
20:40:39 <Outdoorsman> I just have to say... TYPO3 6.2 with fluid/flux/vhs/etc. is really great stuff. I just keep finding more things that make me go, wow!