IRC logs

20150610

• 06:52:57 <Guest|72191> Hello
• 06:58:17 <Guest|72191> I am about to migrate a 4.7 fed template to fluid
• 06:58:48 <Guest|72191> and I have a section like this which needs to be ported
• 06:58:49 <Guest|72191> <f:section name="Configuration">
• 06:58:50 <Guest|72191> <flux:flexform id="sliderHome" label="Slider Home">
• 06:58:50 <Guest|72191> <flux:flexform.grid>
• 06:58:50 <Guest|72191> <flux:flexform.grid.row>
• 06:58:50 <Guest|72191> <flux:flexform.grid.column>
• 06:58:50 <Guest|72191> <flux:flexform.content name="left" label="Bloc 1 - Gauche" />
• 06:58:50 <Guest|72191> </flux:flexform.grid.column>
• 06:59:21 <Guest|72191> would this be mapped to this in the latest fluid version?
• 06:59:22 <Guest|72191> <f:section name="Configuration">
• 06:59:22 <Guest|72191> <flux:form id="sliderHome" label="LLL:flux.sliderHome">
• 06:59:22 <Guest|72191> <flux:grid>
• 06:59:22 <Guest|72191> <flux:grid.row>
• 06:59:22 <Guest|72191> <flux:grid.column label="LLL:flux.sliderHome.bloc1.left">
• 06:59:23 <Guest|72191> <flux:form.content name="left" />
• 06:59:23 <Guest|72191> </flux:grid.column>
• 06:59:49 <Guest|72191> because it shows up in the backend, but there should be content elements inside the columns and they are empty
• 07:33:46 <NamelessCoder> Guest|72191 see https://fluidtypo3.org/documentation/templating-manual/appendix/migration/to-flux-71.html
• 08:02:31 <Guest|72191> I found that doc but it seems that the colPos column needs to be changed by hand
• 08:02:37 <Guest|72191> in the database
• 08:02:57 <Guest|72191> so I created a test element, saw the colPos that was associated to it, then updated the other elements with this new colPos
• 08:03:12 <Guest|72191> which is strange, as I assumed it only uses the "name" property
• 08:24:30 <NamelessCoder> flux child content uses "name" and stores the value not in colPos but in tx_flux_column (parent UID stored in tx_flux_parent)
• 08:24:55 <NamelessCoder> there's an EM upgrade script to do the colPos conversion btw
• 08:49:50 <Guest|72191> I saw that it should use the "tx_flux_column" field, and it does show the selection in the backend. but in the frontend it always complains about colPos and in the backend the column does not show the elements, at least not until i update the colpos myself
• 08:50:08 <Guest|72191> where can I find the EM upgrade script?
• 08:54:40 <Guest|72191> found it :)
• 09:01:17 <Guest|72191> ok. so i executed the update script and now it can't find my template, although the value of the field is still the same
• 09:01:18 <Guest|72191> Resources/Private/Templates/Content/Index.html
• 09:01:26 <Guest|72191> it always points to Index.html
• 09:02:02 <Guest|72191> although my file has a different name and the value is specified in tx_fed_fcefile
• 09:21:16 <Guest|72191> so Index.html needs to be always defined, even if it is not used
• 09:21:18 <Guest|72191> it works now
• 09:21:35 <tpinne> Hi guys, what's the currently preferred way to make flux:field.inline.fal work inside flux:form.object?? I found some github issues for this with hints to check if the record is new. But what would be the correct displayCond or if condition to make that work?
• 09:26:30 <tpinne> And that each object can have its own fal record referenced :-/
• 09:35:11 <tpinne> Never mind... Did some further reading and I think it's not possible at all yet. So I will work around that issue
• 09:52:36 <Guest|72191> the old <fed:data.var maps to <v:variable.register.set ?