04:31:24 <TYPO3ua> I have code: {items.1.item.image) .. {items.2.item.image) .. {items.3.item.image)
04:31:35 <TYPO3ua> I need this ... {items.{itemIteration.cycle}.item.image) but this is not work ...?
04:31:42 <Guest|37930> MyNameContentController seems to be ignored. ContentController leeds to the error... Cannot redeclare class FluidTYPO3\\Fluidcontent\\Controller\\ContentController. I'm confused. ;)
04:33:21 <Guest|37930> ContentController with own namespace seems to be ignored too.
04:49:57 <Guest|33596> Hello! I've just update all of my FLUID TYPO3 Ext. After changing some code. everything works ... unfortunately not all. my flux elements are totally confused. I add the new "FCE1" and after save and close, the element change to "FCE2" f.e. I think there's a problem with fluidpages, because my Backend Layout didn't show their names like "left colum
04:49:57 <Guest|33596> n" `<flux:grid.column colPos="0" name="Slider" colspan="2" />` or is it a problem with flux?
04:53:33 <mrboe> @Guest|33596 the dev-branch is fixed
04:53:56 <Guest|33596> I try it with a new Installation TYPO3 7.1 and the new FLUID TYPO3 Package. The same. I don't see the names of the backend layout columns like 'main' or 'right' `<flux:grid.column colPos="0" colspan="3" name="main" />`
04:55:18 <Guest|38326> The dropdown values for content type and column only show me an INVALID VALUE
04:55:40 <Guest|38326> the column select shows also the number 18181
04:56:29 <Guest|38326> well, if I add content to the fluidcontent grid, everthing works fine, but when I want to change the content type, there's just this Invalid Value
04:58:04 <Guest|33596> hey mrboe, so I'll pull the development branch from fluidcontent. I will try it .. and hope the problem is also fixed at my instance
05:01:13 <Guest|37930> Hi. I have a question about an own Flux ContentController.
05:01:17 <Guest|37930> in the documentation it's written the Class should named ContentController. Do I have to adjust this?
05:01:24 <Guest|37930> MyNameContentController seems to be ignored. ContentController leeds to the error... Cannot redeclare class FluidTYPO3\\Fluidcontent\\Controller\\ContentController. I'm confused. ;)
05:01:29 <Guest|37930> ContentController with own namespace seems to be ignored too.
05:06:10 <Guest|33596> Hi <mrboe> . yes. my problem is also solved. the name of the backend layout columns still not there, but here i can wait for a new update of fluidpages ... the problem with the FCEs is done. thanks a lot
05:15:14 <Guest|38326> Well that was not the problem. I still have the INVALID VALUE options in content-type and content-column dropdown. The flux object is <flux:form.content name="foo" label="bar" />. do I have to use another element instead?
05:23:10 <pedda> i'm facing a behaviour, i thought it was already fixed, where assets via ts and assets via fluid are not merged correctly
05:23:28 <pedda> i pulled the latest version of vhs in my project
05:25:20 <pedda> when i debug $assetSettings in AbstractAssetViewhelper in Line 301 i get a debug output for each asset i included via fluid
05:25:53 <pedda> those 2 which were included via ts are listed within each debug output as if they were properties of each asset included via fluid
05:26:22 <pedda> as if the asset merging of ts based and fluid based assets would miss the right level of array items
05:30:02 <pedda> anyone facing the same behaviour ?
05:30:59 <pedda> i realized there are the ts based assets guys and the fluid based assets guys, i belong to the second group, as i want to unclude assets only if a certain fce is used for instance
05:31:11 <pedda> but then if i use extensions with ts based assets things get strange
05:45:50 <patricktzzz> hi.. are there any notes for updating to fluidcontent 4.2 ?
05:46:00 <patricktzzz> because after updating, i can't choose the Fluid Content type any more
05:52:41 <pedda> patricktzzz did you upgrade flux also ?
06:04:05 <patricktzzz> yes, i updated all extensions in extension manager (flux, fluidpages/fluidcontent)
06:04:06 <braguzz> ext manager and language gives me 'Version number in composer manifest of package "fluidcontent_bootstrap" is missing or invalid'
06:24:20 <braguzz> I've lauched the 'update extension list' and ... boom!
06:25:21 <pedda> braguzz: I have not access to ext manager :( <- ??? if you can do thid: braguzz: I've lauched the 'update extension list' and ... boom!
06:32:25 <mrboe> if you want to use TER releses from yesterday you have to switch to fluidboostraptheme banch 2.0 (not stable yet) after you switched from fluidcontent_bootstrap to fluidboostraptheme
06:32:57 <mrboe> you also have to use fluidcontent dev branch bacause the TER version has a bug
07:10:41 <Kalypso63> i just a have a little question with the new version of fluidpages (3.2.0).
07:12:28 <Kalypso63> If have 2 templates (Landing pages & standard) and i just set my root page with pages layouts (rootpage : Landing pages & all child : Standard)
07:14:20 <Kalypso63> but when i want to edit and set some options in my flux configuration on child page, the configuration is not goof. This i my home page configuration which is load
07:15:09 <Kalypso63> i see some new features on ConfigurationService.php and function resolvePageProvider
07:15:58 <Kalypso63> if the field tx_fed_page_controller_action is empty the configuration which is loaded is not the main conf but sub conf
10:16:22 <denyskoch> is there a way to change page templates from plugin controller? I have 2 fluigpage templates, 'Default' and 'Default with Sidebar'. On the page there is plugin, which need to switch the Template of the page from 'Default with sidebar' to Default.
10:26:59 <pedda> @denyskoch i'd rather consider a 100% width plugin layout and make the plugin template handle the rendering of the sidebar.. vioa partial or sth
10:29:39 <pedda> so you can teach your plugin to load a partial if plugin state = whatever
10:30:19 <pedda> or use view (if necessary) and move the somext-plugin-template-file to your provider extension, to keep the plugin reusable among projects
10:52:15 <pedda> you assign landing page templa to your root page, all other child pages get Standard page layout assigned
10:52:44 <Kalypso63> with the new version of fluidpages (3.2.0), if you choose on page layout configuration the option parent decides, the page load the subconfiguration instead of page configuration
10:53:00 <pedda> if you try to set flux options of standard page layout (so setting those for a certain child page of landing page) the values for landing page are set instead ?
10:53:49 <Kalypso63> yes, flux options are not used
10:54:10 <pedda> flux options are used, but of a different file than expected!
10:54:18 <Kalypso63> i think is due to resolvePageProvider function
10:54:37 <Kalypso63> the function test if the sql field tx_fed_page_controller_action is empty
10:54:42 <pedda> PageProvider = PageController of your provider extension
11:02:54 <pedda> sorry Kalypso63 never experienced your issue, neither do i use page flux options nor do i have a project with fluidpages 3.2 running
11:04:35 <Kalypso63> I upgrade fluidpages yesterday but is on developpment staging. I just see that anathor person have the same problem and push it on issue project. So just wait...
11:26:29 <pedda> NamelessCoder you have a minute ?
11:31:04 <NamelessCoder> there we go - sorry about the wrong tag
11:31:24 <NamelessCoder> pedda if it is only a minute, sure
11:31:41 <pedda> did you ever face ts based and fluid based assets not merging correctly?
11:32:31 <pedda> imagine ext:A assigning assets via TS and Ext:B relying on an Assets.html partial where assets are included by the help of viewhelpers
11:33:00 <NamelessCoder> if one context is cached and another is not, merging is prevented
11:33:12 <NamelessCoder> you can still use dependencies but for technical reasons the files cannot be merged
11:33:22 <pedda> when i debug $assetSettings in AbstractAssetViewhelper in Line 301 i get a debug output for each asset i included via fluid
11:33:31 <NamelessCoder> other than that no - they should transparently merge together
11:33:46 <NamelessCoder> TS assets don't go through the ViewHelper
11:34:04 <pedda> each of those outputs contains the ts based assets as if they would be properties of the currently debuged output
11:36:05 <NamelessCoder> if your assets with the same name exist in both places then yes: those defined in TS are applied on top of those defined in Fluid, those that don't exist in Fluid are created directly from the TS
11:36:08 <pedda> while mainCss.path is still valid
11:36:59 <pedda> there are two assets at the bottom in the debug output
11:37:22 <pedda> if this is expected, i'm fine with this, as everything works fine.. but i was wondering if this is wanted behaviour
11:39:13 <NamelessCoder> the intention is that TS has the "final word" over any other assets. The logic first loads all the assets that were NOT defined in TS, then loads the TS and applies attribute changes to any assets that were previously defined (so the result becomes a combination of attributes you set in fluid/php, overwritten selectively with those you set in TS). Finally, any assets that weren't already created in fluid/php are created as php assets based on the
11:45:27 <pedda> which is included via static ts in backend
11:45:40 <jost> Hi... just updated to flux 7.2.0... Now my template for <flux:widget.grid/> does not work any longer, because that viewhelper has been made useless. How do I influence backend preview rendering now?
11:46:03 <NamelessCoder> yeah but what is the location you used? plugin.tx_vhs.settings.asset.xyz.path = ... and so on?
11:47:39 <NamelessCoder> yes: it is expected, albeit a bit confusing.
11:48:00 <NamelessCoder> the reason is that your array contains those entries that weren't picked out because they had corresponding fluid/php assets.
11:48:20 <NamelessCoder> ...and we merge the settings internally in a way that those values end up there
11:48:47 <NamelessCoder> shouldn't hurt anything at all and they should still pop up as proper assets - it's just the entries that are redundant/inherited
11:50:02 <NamelessCoder> I suppose this can be avoided by checking asset attributes against the array, only transferring those array values that are named like asset attributes
11:50:25 <pedda> well .. there is no bad behaviour
11:53:18 <NamelessCoder> I'm not *that* sorry. Was working on a FAL driver...
11:54:26 <drlimbo> someone has an idea, why there is an "<p class="bodytext"></p>" before the content when i show RTE-Content with <f:format:html>? - in the RTE-Source it starts with a H2
11:55:07 <NamelessCoder> you probably add a line break in your template, drlimbo
11:55:15 <NamelessCoder> {value -> f:format.html()} is always safe
11:56:14 <NamelessCoder> then the RTE must contain the line break
11:56:33 <NamelessCoder> is H2 allowed by your RTE proc func?
11:56:49 <NamelessCoder> if not, that'd be removed and you may have an empty line
11:57:03 <drlimbo> yes, it also renders the H2 in the frontend (but add the empty p tag before)
11:57:36 <NamelessCoder> try checking the RTE in source mode. I've sometimes had those starting spaces and the RTE couldn't delete them with backspace/del
11:57:59 <drlimbo> i checked in source-mode, theres nothing before the h2
11:58:55 <drlimbo> also after saving the rte-field in backend, it starts with a h2 -> the empty p-tag is added while rendering the frontend i think
12:00:40 <NamelessCoder> hmm - in that case I'm out of guesses
12:01:38 <drlimbo> lib.parseFunc_RTE.nonTypoTagStdWrap.encapsLines.addAttributes.P.class > <- removes the class="bodytext"
12:02:36 <NamelessCoder> but why it adds it in the first place... dunny, sry
13:35:37 <JustAPoring> I looks like the lack of page.bodyTag makes it default to a plain <body>|</body>
13:41:38 <gbod> JustAPoring: What do you want to achieve?
13:42:41 <JustAPoring> gbod: I wanted the complete template in html files for ease of use - I am currently working on a newsletter template which means I have to do dirty stuff like inline styles on the body tag.
13:43:11 <JustAPoring> In the end it doesn't matter that much to me if I have to set it in TS, I just thought it would be nice to have everything in one template