03:15:57 <feelx75> good morning. When I copy a CE I don't have a "paste-after icon" anymore between other CE's. I have only a paste-in-icon on the top of the page. What could cause this? I have to paste it on the top and move it... this way it works... but why?
07:53:06 <matt1808> Hi Everyone. I am having a problem with inheritance of values in page templates. I need to disable the inheritance of certain values to subpages. Ive tries adding inherit="FALSE" inheritEmpty="FALSE" and inherit="0" inheritEmpty="0" and various combinations but not had any luck. How can I do this?
08:42:44 <matt1808> Can anyone help with my inheritance problem??
08:50:12 <matt1808> The case I am looking at is to do with the inheritance of objects within a section in the page configuration. I am using this to add multiple buttons to the top of the screen. Basically I dont want these buttons replicated to child pages.
08:55:14 <NamelessCoder> matt1808 this stackoverflow thread may be of use to you: http://stackoverflow.com/questions/22073264/section-in-fedext-fluidpage
08:57:57 <NamelessCoder> the TL;DR - our only way to achieve inheritance is through default values of fields and those exact types of fields (section, object) don't support default values (e.g. a list of fields which must be created if no value is saved).
08:58:52 <Guest|57732> Hi. I'm running in a problem deploying a website to a customers site. It seems that the vhs-Viewhelpers doesn't produce any output. Any ideas where to figure this problem out?
08:59:05 <Guest|57732> local and on staging it works perfect.
08:59:27 <NamelessCoder> Guest|57732 if by vhs viewhelper you mean the v:content.* ones, then there are two things to check:
08:59:57 <Guest|57732> <v:content.render column="1" /> is the problem, correct
09:00:01 <NamelessCoder> if you use CSC, make sure the extension is installed and you have the TS from it loaded (and that you don't destroy the TS somehow through site setup)
09:00:18 <Guest|57732> we use fluidcontent_core instead
09:00:23 <matt1808> Thanks, my problem is that it is beign inherited. I have https://gist.github.com/anonymous/0d32bc986aa91a1a7a57 in a partial that that is used by all page templates. If I look at the page config of a sub page, it is empty but when i look at the front end, it is inheriting the configuration from the parent page
09:00:35 <NamelessCoder> if you use FCC, make sure the typo3conf/AdditionalConfiguration.php file was created and contains the code from FCC's shipped file, make sure FCC is installed and finally, make sure the TS is loaded.
09:01:12 <Guest|57732> hmm. I'll double-check this, but I'm pretty sure it should be in place...
09:01:16 <NamelessCoder> key difference: typo3conf/AdditionalConfiguration.php - can be initialised by running the update script for FCC via EM.
09:01:50 <matt1808> The partial in the frontend for adding the buttons - https://gist.github.com/anonymous/7cc94b65bc129255ab2c
09:01:58 <NamelessCoder> if you have pending DB schema changes that would make queries on tt_content fail, fix those of course. It may not break the BE but still prevent FE from loading records.
09:02:43 <Guest|57732> db compare tracks no issues...
09:02:58 <matt1808> Is the problem with the way I am referencing the objects in the front end??
09:03:04 <NamelessCoder> matt1808 correct - the problem with support for inheritance is entirely in the editing of the fields. We can't pre-fill sections with objects so you won't see what you would get in FE when you edit in BE.
09:04:01 <Guest|19542> sorry; accidentally closed this window. ;-)
09:04:34 <Guest|19542> thanks for your help; you were right about additionalConfig - the customers it has overwritten these...
09:05:05 <NamelessCoder> the stackoverflow thread has an alternative suggestion which builds on content sliding and a custom content element in a custom colPos - it's approximately the same amount of overhead and editing complexity, but explaining it to editors is very different in the two cases...
09:06:42 <NamelessCoder> matt1808 it's less than ideal but it's the best we can do under the circumstances of TCEforms ;)
09:07:22 <matt1808> Would you suggest moving this to a CE rather than in page configuration? Is there a way to check for the objects exist on the current page?
09:10:42 <NamelessCoder> I would actually let this be decided by your customer. The CE slide solution is good if you know that the customer will want to change these at points in the page tree, but it is somewhat harder to explain to the customer how that will work. The page inheritance solution is good if you expect these objects to only be defined and changed on the top page and never on sub pages and you can explain to the customer that even though the section/object
09:10:42 <NamelessCoder> is empty on sub pages in BE, it will still be available in FE.
09:12:42 <NamelessCoder> I suspect your use case sort of treats these objects as if they were practically content elements that you edit inline, are inherited and have very simple options. So using CE+sliding is sensible here - assuming you can educate your customer ;)
09:19:07 <matt1808> Hmmmmm... time to have a rethink about this. I think adding a CE might make it more difficult for the editors to know what they are doing. As the number of this buttons will be limited to a max of three, I might try removing the section/object configuration and then use three sets of fields for button1, button2 etc. This would then allow for the in
09:19:07 <matt1808> heritance of these fields to be managed??? I'll give it a go and see what happens, if not, a CE it is. Thanks for your help with this. Cheers
09:21:45 <NamelessCoder> matt1808 makes perfect sense to use three sheets if you're already wanting to fix the number of buttons
09:21:56 <NamelessCoder> since sections don't support maxItems that's perhaps an even better way
09:32:41 <matt1808> I'll give it a go. Thanks for all your help
09:46:15 <matt1808> One final question. i have named my varaiables settings.button1.text, settings.button2.text etc. Is there a way to loop though these with a for statement incrementing the number, rather than creating three <f:if condition="..." statements?
10:06:07 <Guest|57655> When i add the "enabledControls" param to my IRRE in my FCE Configuration i get the error "Wrong configuration in table tt_content" when i try to add new relation records.
10:06:12 <Guest|57655> My Code: <flux:field.inline
10:25:02 <fger> hi guys, how can i access the iterated array/object for options inside a f:form.select or v:form.select viewhelper in the fluid template ?
10:25:23 <fger> use case: we want to add a data-parent attribute to each <option> - element
10:25:48 <fger> its value should be the key of the current rendered option
10:27:51 <Guest|57655> @Xatenev: heres the pastebin http://pastebin.com/9bkjP3mH
10:28:31 <Guest|57655> Once i add the enabledControls param the error appears. If i leave it empty ("{}") or dont add it it works fine (i need the delete option as the hide option actually doesnt work)
10:34:58 <Guest|57655> i see my error beign discussed several times in this channel but never a solution was logged.
10:35:06 <Guest|57655> does noone have any intel on this?
10:36:31 <Guest|57655> the enabledControls actually work and the delete icon is correctly shown and it works
10:36:38 <Guest|57655> but once i add the setting i cant add new records anymore
10:37:16 <Guest|57655> the main issue why i found this issue is the fact that hiding records in a FCE based inline relation doesnt work at all
10:37:28 <Guest|57655> the records gets shown hidden and once i save and reload its unhidden again
10:46:41 <Guest|57655> So i think i have to use the workaround and hide/delete records using the WEB=>List view as the constellation of IRRE inside Flexform inside FCE is not working.
10:51:00 <fger> anyone can answer the data-attribute / option -array question ?
11:12:54 <Outdoorsman> fger maybe additionalAttributes="{foo: 'bar'}" is what you're looking for? https://fluidtypo3.org/viewhelpers/vhs/master/Form/SelectViewHelper.html
11:13:31 <Outdoorsman> I haven't tried using this, I just browsed the documentation looking for something that looked like it might be what you're looking for.
11:29:50 <fger> well, yes, but how can I access the option-keys/values for the current loop inside the v:form.select.option viewhelper for example ?
11:30:00 <fger> i wanted to stay inside the fluid template
11:41:31 <Outdoorsman> I can't get overlays to work for the life of me!!! Don't know what I'm doing wrong. Everything looks correct.
12:30:22 <NamelessCoder> Outdoorsman how much have you solved so far? Still trying to overlay page templates?
12:31:19 <Outdoorsman> I'm stiiiiill trying to get overlays to work.
12:34:21 <Outdoorsman> This is totally ignored... overlays.provider_extension.templateRootPaths.10
12:35:07 <NamelessCoder> yes - that is by design; the "overlays." array only supports the singular naming (they were invented to allow multiple paths before the plurals were possible)
12:36:20 <NamelessCoder> you should be adding these paths directly in "view." of the extension you want to overlay, just skip the whole "overlays.provider_extension." part.
13:38:25 <frustration> Greetings, I'm trying to use T3 6.2.9 and "FluidTypo3", however I'm struggling with viewhelpers not beeing loaded. Are the extensions listed in TER all compadable with 6.2.9 or do i have to use specific versions of the extensions together ?