04:20:29 <s-andersen> I have created a controller for my provider extension, to pass on a GET var to template. However, it seems that fluidpages cache the result of the controller on a per page basis. So the code only works when the page is uncached i.e. backend user is logged in. Any ideas on how to prevent this?
05:36:49 <cedricziel> enable no_cache in the page properties?
06:31:25 <s-andersen> cedricziel: Thank you for the hint. I remembered that fluidpages in page.5 is defined as a USER function. Using typoscript to convert it to USER_INT when the GET-var is present did the trick
06:54:19 <benjamin_654> yes, the element goes to the new position but after a reload it is not moved
06:54:57 <cedricziel> pls report an issue in fluidcontent
06:55:51 <s-andersen> cedricziel: development context doesn't work either. Well if it disables all cache it does the same as setting no_cache in page properties. Or actually it performs a little bit better, because the page is cached, but not when the parameter is set.
06:55:55 <benjamin_654> i am not sure what the cause is, i would first like to have this confirmed by someone else
06:56:29 <cedricziel> pls report an issue in fluidcontent
07:03:29 <cedricziel> I dont know why so many people fear issue creation. my coworker himself is too shy and wastes hours and hours trying to find solutions in software made by 3rd party.
07:04:41 <benjamin_654> most of the time when something does not work its not a bug but a wrong configuration on my side..
07:05:23 <cedricziel> we dont judge you, nobody does. Even if there is an easy solution, issues are legit questions and completely neutral
14:25:44 <Guest|66332> hi together, how can i use info of a field form individual page Configuration (e.g. input-field within section Configuration) within the viewhelper vhs v:page.menu?
14:29:04 <Outdoorsman> I'm not sure if this is what you're talking about but I believe this might be what you're looking for... <v:page.menu entryLevel="{settings.entryLevel}" useShortcutData="TRUE">
14:37:48 <Guest|66332> not exactly ... <v:page.menu.directory as="menu" pages="23"> within I can iterate through all items with <f:for each="{menu}" as="menuitem"> ... and i can use for example {menuitem.uid} ... but i dont know how to use the information of the flux-page Configuration, which is saved in a flexform
14:41:58 <NamelessCoder> Guest|66332 see https://fluidtypo3.org/viewhelpers/flux/master/Form/DataViewHelper.html
14:49:22 <Guest|66332> thanks ... but i am afraid i dont see how to use this within <v:menu ... (i am not a "hard coder") ... are there examples how to use it somewhere?
14:56:42 <Guest|66332> i tried it this way: within <v:page.menu .. ... <flux:form.data table="page" field="tx_fed_page_flexform" uid="{menuitem.uid}" record="{field: 'settings.keyvisual'}" \>
14:57:27 <NamelessCoder> you'll need to combine that viewhelper with manual rendering of menus - there's an example of the menu rendering here: https://fluidtypo3.org/library/code-examples.html?tx_fluidshare_display%5Bgist%5D=2&tx_fluidshare_display%5Baction%5D=display&tx_fluidshare_display%5Bcontroller%5D=Gist&cHash=d501a3d334ac0d9a1b6a00fa8f3da8b4 and you then add flux:form.data inside the f:for (it works the same way as f:for, with an "as" argument) and supply table
14:57:27 <NamelessCoder> and record arguments. Table is pages and record is of course each menu item.
15:06:45 <Guest|66332> ok thanks, the menu-example i did use already, and i am very happy about these expamles, i will try ...
15:41:24 <Guest|66332> @NamelessCoder ... Thank you ... I seems to work ;-)