04:20:53 <MacPhil> you could redirect the php errors to a file
04:22:13 <MacPhil> my webserver configuration is hidding the php white errors from my log :D so i set the above
06:08:01 <potofcoffee> I think I figured it out. Looks like it was simply a timeout error with fcgi.
09:04:01 <Defos> Hey lads! Can I access nested FCEs? e.g. I have a FCE which has one grid. In this grid I have multiple other FCEs. How do I access the flux elements of the inside FCE?
09:05:38 <xaver> Defos: where do you want to access them?
09:07:24 <Defos> In the outer (wrapping) template which has the single grid
09:10:07 <xaver> you mean soemthing like this https://github.com/bootstraptheme-for-typo3/fluidbootstraptheme/blob/development/Resources/Private/Templates/Content/Row.html
09:43:17 <xaver> in wizard it is mixed - use same order in element select and not based on provider
09:43:56 <xaver> you would need to split it yourself, but i would improve to build your default provider and mix is with a individual one
10:32:52 <arnekolja> I read that TYPO3 CMS 7.5 or 7.6 will provide Fluid based content elements as core functionality. What does this mean for fluidcontent_core? Will it get dropped, or does it serve a complexer purpose?
10:34:06 <xaver> arnekolja: depends on implementation - put i think it will will be continued. But we use core tables - should be no problem to switch
10:34:37 <arnekolja> okay. I'm looking forward to seeing it in action :)
10:34:38 <xaver> nested content is something else - we would like to use a nativ core feature, if it is useable in all cases...
10:34:58 <arnekolja> you mean like fces with grids?
10:35:17 <xaver> you can remove csc and install fcc - image with text is missing
10:35:54 <xaver> yes, or also accordion. 1 wrapper and content elements inside
10:35:56 <arnekolja> yeah, but missing image with text is quite a problem for editors who are used to it. tried it and failed communicating it :D
10:36:29 <xaver> most webs are responsive and text with image is horror - create needed elements as FCE
10:36:30 <arnekolja> yes, I think the timeframe wont allow it to make the first iteration an overall solution
10:36:41 <xaver> it is tested and optimized without 1000 options
10:37:07 <arnekolja> i know you're right … just fighting with the agency-internal editors.
10:37:14 <xaver> you can't test everything in image with test
10:37:23 <arnekolja> dont know right now … but image+text can be hidden, right?
10:38:13 <xaver> i build an FCE Contact with image and text or Product image and text
10:38:39 <xaver> i git it should be hiddden, i don't know if it was released
10:38:39 <arnekolja> btw, is there a performance "problem" with fcc? i noticed that pages containing multiply nested fces with images caused two installations to load the affected page for a looong time (pages module in BE)
10:39:30 <xaver> fcc is not nested - should be faster - less TS
10:40:04 <arnekolja> i mean i had fces with grids and those grids containing images added via fcc
10:40:46 <xaver> depends on cache and some other stuff - we added new caches few months ago
10:40:56 <arnekolja> e.g. a four-column grid, each col containing a two column grid with text in the one and image in the other column. that about 10 to 15 times and the page loaded around 20 seconds in BE
10:41:07 <xaver> if you have a testable reasonable performance issue - report it :)
10:41:49 <arnekolja> okay. maybe i'll reconsider using fcc again :) it's so great in theory, but i failed on image+text and performance a few months ago. maybe it is better now :)
10:42:32 <arnekolja> image+text shouldnt be a problem if its hidden. so i'll check current versions and/or permissions for that
10:43:02 <arnekolja> i'm also a fan of providing specific fces instead of offering each possible combination via generic elements.