04:10:03 <braguzz> I've only add something inside the header part.
04:11:02 <braguzz> it wotks when I add content, but when I edit content that I've inserted, I got not the list
04:11:21 <braguzz> for example if I insert wrapinheader = No,Yes
04:11:46 <braguzz> when I insert new content I see a dropdown with No and Yes
04:12:23 <braguzz> if I insert Yes and save, when I reedit that content I see only 'Yes' in dropdown
04:14:57 <bottoni> All that´s done in header is selecting the heading level (1-6). It sounds like your new values No,Yes are somehow used as a replacement for the integer values 1-6 and that´s maybe why the error message reads 'Invalid value'
04:16:10 <braguzz> mmm, I dont think heading level are there
04:16:51 <braguzz> my primary idea is to insert some other variable
04:17:21 <bottoni> that´s the default. Selecting the level and adding classes. Adding Fluid variables is not possible from there
04:18:08 <bottoni> I would suggest building own content elements FluidTYPO3 offers all to do it without effort. And from there you are totally free to build what you want
04:18:54 <braguzz> yes but I want that user can choose to wrap header
04:19:33 <bottoni> yes I´m quite sure since I didn´t read sth like that until now. Maybe someone here can correct me. But I think what I described is the scope of the fluidcontent_core TS
04:20:28 <braguzz> someone some days ago told me that this is the way to do
04:20:44 <bottoni> You can´t achieve the styling by making the class available the default way?
04:22:35 <braguzz> I'd like that the user choose to wrap or not the header so he choose h2 and headline-right
04:22:59 <braguzz> result should be <div class="headline-right"><h2>title</h2></div>
04:23:36 <braguzz> it should work probably I miss something in constant or in setup TS
04:28:59 <bottoni> I could imagine reading {settings.header.className} and adding the wrapping conditionally with Fluid. So you would add settings.header.classNames = wrapinheader ore maybe something more readable in your TS
04:44:57 <braguzz> can you try my setup in one of your env?
04:47:14 <robsonrobi> I have a custom FCE build with flux. In the configuration exist an inline FAL an multiple input fields. My goal is, when i localize the element, i do not want the FAL be localized, instead the original FAL of the mother language should be used. i recognized the attribute "localizationMode" = 'keep' but it has no effect. Am i missgin soetinh, can an
04:47:43 <robsonrobi> I have a custom FCE build with flux. In the configuration exist an inline FAL and multiple input fields. My goal is, when i localize the element, i do not want the FAL be localized, instead the original FAL of the mother language should be used. i recognized the attribute "localizationMode" = 'keep' but it has no effect. Am i missing something, can
04:48:24 <robsonrobi> i do not know how to move on with that topic...
04:48:27 <braguzz> I've understood your problem and is enough for me ;)
04:48:29 <bottoni> Did that and it is as expected. I don´t see anything selectable in backend since settings.header.wrapinheader won´t be processed in any way
04:49:12 <braguzz> but why it works when I add new content?
04:50:08 <braguzz> look at that https://slack-files.com/T024TUMLZ-F09T263RN-fb9cae2d45
04:51:10 <bottoni> I can´t tell it has no effect with exting content and with new content on my side
04:52:04 <braguzz> have you inserted in setup with [global] ?
05:13:26 <braguzz> you know.. when everithing else fail, read the manual
05:13:32 <drlimbo> after upgrading flux-family all my FCE's doesn't have an icon =( is there something new? i thought without specyfy an icon, all will use the default icon
05:25:00 <bottoni> braguzz and if it still fails, read the code
06:22:27 <robsonrobi> no idea at all ? I have a custom FCE build with flux. In the configuration exist an inline FAL and multiple input fields. My goal is, when i localize the element, i do not want the FAL be localized, instead the original FAL of the mother language should be used. i recognized the attribute "localizationMode" = 'keep' but it has no effect. change the
06:22:27 <robsonrobi> file reference in the source show render that new image in the translation Am i missing something, can anybody assist?
07:32:59 <jost> Can someone tell me, how well workspaces are supported in the newest versions of flux and fluidcontent? Especially when using nested content?
07:39:11 <drlimbo> im also interested in that question jost
07:39:38 <drlimbo> i think me had a project with flux and fluidcontent WITH workspaces, and i don't remember any problems
07:40:05 <jost> drlimbo: I have a case here, where virtually nothing works
07:40:22 <jost> Either I am doing something wrong, or the compatibility is not so great
07:42:07 <drlimbo> for example, we use a 50% - 50% FCE with two containers containing elements and plugins
07:42:26 <drlimbo> it just looks a bit messy if you have a lot of changes made to "publish"
07:43:00 <jost> We've had problems especially with moving content elements around, they frequently got lost... and they did get lost in live and draft at the same time, while only editing in draft
07:44:11 <jost> and when trying to publish or discard the changes later, exceptions occurred (about missing templates or content elements)
07:45:35 <drlimbo> i just had the problem with missing templates on another project, because the FCE's was organized in Subfolders whats not working anymore
08:05:47 <braguzz> I also have the problem of the missing icons.
08:05:49 <braguzz> after upgrading flux-family all my FCE's doesn't have an icon
08:23:34 <jost> braguzz: at some version the way you set the icons changed
08:24:25 <bottoni> see the derecated warning: https://fluidtypo3.org/viewhelpers/flux/master/FormViewHelper.html
08:24:58 <jost> the icon="..." attribute was removed, instead you need to set the icon in the "options"-attribute: options="{icon: '{v:extension.path.resources(path: \\'Images/contentelement-icon.png\\')}'}
09:40:23 <braguzz> I have this <flux:form id="ListaImmagini" options="{useTypoScript: 0, group: 'Unify', icon: '{f:uri.resource(path: \'Source/Icons/icon-twitter.png\')}'}">