09:58:51 <cedricziel> Denyerec: most functions dont support chaining as you'd need a object returned. in php, you could mock this for plain functions via closures
10:06:43 <jlumpe> bjo3rn: everythign works now as expected :)
11:12:32 <Guest|89010> I tried to add the xsd-schemas to my flux-templates. The problem is as soon as I add a <div> or <html>-structure around my fluid-tags (as suggested) the template seems corrupted.
11:13:56 <Guest|89010> The template still shows up in the page-settings, but with no label and when i select it the template the configuration-tab gives some errors like "Data Structure ERROR: No proper configuration!"
11:48:40 <BrianJ> jlumpe If 'postVarSets' is 'fixedPostVars' then my URL works but throws an error: Reason: Segment "golf-i-dyrehaven" was not a keyword for a postVarSet as expected on page with id=9220.
13:01:27 <benjamin_654> hi, is there a way to get information about the column/grid a flux-ce is inside? (eg. for different width) I see there is a variable {_all.grid} - what´s this for?
13:32:38 <danilobuerger> jlumpe a combination... most of them in a single tree since same content... north america on its own tree... but yeah there are some issues with that ...... about c&p we did a lots of fixes (> 20 bugfixes) for all commands (new / localize / d&d / etc) already and c&p is the only one left
14:48:34 <gencha^> I'm currently building a site with fluidbootstraptheme and fbtcustomiser. When I add a new template to my extension, it doesn't show up when I create a new content element
14:52:07 <gencha^> Erm, yeah, so my question is, is there some sort of common mistake people make that results in this behavior or is fbtcustomiser really only able to override but not add functionality
14:52:33 <jlumpe> i didn't use fbtcustomiser yet :(
14:53:51 <jlumpe> but i assume it is used to override existing templates
14:55:02 <gencha^> yeah, it is. that part works fine. i would have assumed that i can also add new templates though. and i'm pretty sure i can, i'm just not doing it right
15:30:17 <jlumpe> Note that {arrayVariable.{offset}.name} is not possible due to the way Fluid parses nodes; the above piece of code would try reading arrayVariable.{offset}.name as a variable actually called "arrayVariable.{offset}.name" rather than the correct arrayVariable[offset][name].
15:58:54 <pedda> assuming you already use a provider extension, fluidbootstrap can be seen as a template-swiss-tool providing you with some bootstrap components
15:59:40 <pedda> unlike vhs being a swiss knife for creating custom themes with some logic
16:03:17 <jlumpe> pedda: if you read the docs, they state that you can use fbtcustomiser to excent fluidbootstrap easily (including adding new components)
16:03:50 <jlumpe> all i'm saying is that the wording feels wrong, because you cannot just download the extension and add a new template. it won't work since it doesn't register itself as a provider
16:03:56 <jlumpe> so that step is just missign on the docs
16:22:16 <pedda> general question: if a customer asks you to fix some css issue on an android 2.3.x device, what do you do?
16:22:18 <BenjaminR> randomresult: pm me for bootstraptheme-for-typo3/fbtcustomiser#5 if you like
16:22:19 <FT3BOT> Issue 5: Should register itself as a provider extension https://github.com/bootstraptheme-for-typo3/fbtcustomiser/issues/5
16:23:24 <jlumpe> BenjaminR: the issue was just that the docs specifically state that you can add content, and the steps do not involve registering the extension as provider extension
16:23:37 <jlumpe> but of course, updating the docs would also resolve the 'issue'
16:24:36 <BenjaminR> jlumpe i will ask randomresult for his opinion but i think we demonstrate ext:view here and its not meant as skeleton for fluidcontent/fluidpages
16:24:52 <BenjaminR> what wouldnt be needed anyway because of ext:builder