08:40:11 <FrankUnderwolf> Hi. I'm having trouble with the "builder" extension. It produces no working setup for "FCE" type elements. Before I file a bug report, I wanted to know if there's anything else I can try to have it fixed.
08:41:10 <FrankUnderwolf> Haven't used IRC for a while so first I'd like to know, is this the right place to ask questions about fluid?
08:49:18 <FrankUnderwolf> I'm on a fresh install of TYPO3 6.2.15, with Builder: 1.0.0, VHS: 2.3.3, Flux: 7.2.3, Fluid Backend 1.0.1, Fluid Pages 3.3.1, Fluid Content 4.3.3, Fluid Styled Content 1.3.0, all installed with FluidTYPO3 site kickstarter 1.5.2
08:50:09 <FrankUnderwolf> I have created a provider extension. It works fine except that it ignores its own example.html FCE template.
08:50:48 <FrankUnderwolf> more precisely: the template works fine as well, except its "main" section is being ignored.
08:51:53 <FrankUnderwolf> the field in configuration works, preview works (I can see what I put in), main does not work. It does not produce the output from the template (e.g. <h3>I am a content element!</h3>)
08:52:27 <NamelessCoder> FrankUnderwolf make sure you run the installation/update script for fluidcontent_core so it writes AdditionalConfiguration.php
08:57:04 <FrankUnderwolf> Thank you, NamelessCoder. It says in the documentation that I run that script by clicking on the extension name in the TER. But that's not possible
08:58:55 <NamelessCoder> not the name itself but the green "update" arrow. It's the "site" extension that you configure by editing extension settings
08:59:08 <NamelessCoder> (green arrow next to fluidcontent_core)
08:59:44 <FrankUnderwolf> omg I have never done that before :D let's see...
09:03:14 <NamelessCoder> there's a longer explanation for that
09:04:04 <NamelessCoder> the tl;dr is that because this is a content rendering extension it has to add TS in a particular way and the only way to assure this (when you're not a core extension) is to put this special entry in AdditionalConfiguration.php (because this is the only place that works in the perspective of inclusion order)
09:05:05 <FrankUnderwolf> I see! Thank you, this helps getting me started.
09:05:10 <NamelessCoder> the TYPO3 core does this for the css_styled_content extension, one of the reasons why that ext was too tightly coupled (special support in TS handling classes in EXT:core)
09:05:42 <NamelessCoder> it's supposed to improve soon, though. I'm not exactly sure *how* they're going to achieve that (it's quite complex because it has load order involvement) but, that's the word.
09:05:51 <FrankUnderwolf> and for historic reason CSSSC still gets special treatment FSC does not
09:05:57 <NamelessCoder> e.g. fluid_styled_content of the new core also has to do this exact same thing
09:06:47 <FrankUnderwolf> I think I have read something like this somewhere while searching for a solution to my problem, but somehow this flew right by me. In one ear, out the other.
09:07:05 <NamelessCoder> that's not entirely true I think. I have a very nagging suspicion that: FSC only works without this consideration because a) it is a core extension and thus loads before local ones, b) it provides content elements which other core extensions don't require to be present.
09:07:44 <NamelessCoder> I suspect FSC still has the exact same problem as FCC does - the only difference being that because FSC is a system extension it is less affected by the load order issue...
09:08:14 <NamelessCoder> if you locate the original merge request for that feature there's a commenting history about this very thing
09:10:04 <FrankUnderwolf> I see. Well this helped tremendously, I can now start converting my projects to Fluid FCEs. So happy :D thanks again.