08:29:18 <artisticMink> Hello, after upgrading to flux 7.1 i'll ran into the problem that my custom page controller which belongs to the provider extension get's called, but no one of the corresponding actions get called. Yet, the site renders flawlessly. Default actions seem to get used instead of my custom ones. Did some conventions change? Sadly bootstrap_pages seems t
08:29:18 <artisticMink> o be out of date. My controller is pretty straight forward: http://pastebin.com/nRQAQV8X Any help much appriciated.
08:31:42 <thierry> Hello, in a v:page.menu and the <f:for each loop inside, is it possible to access the page settings, and not "only" the standard fields ?
09:32:28 <thierry> OK, I give it a try, thanks Xaver
10:07:47 <artisticMink> xaver: Thanks for the response, so i have to announce my custom controller in ext_tables.php?
10:15:28 <artisticMink> xaver: You where right. The lines where the providers get registered was commentet out for some reason. Though, outcommenting them results in 'Class 'Tx_Flux_Core' not found in' Oh well, i'll sure have a great afternoon. Let's start digging. Thanks for your help.
10:23:31 <artisticMink> For the logs, solved the error by using the correct namespace to call flux core (FluidTYPO3\Flux\Core::registerProviderExtensionKey). Still no luck on calling controller methods.
10:46:21 <thierry> @xaver: but, a "limitation" of Fluidpages: the settings aren't available on translated pages. That means: such settings must be "language independant" (dates, colors, ...), but no fields like "title", "label", ...
11:05:16 <thierry> Big "old mistake" of TYPO3 to have a separate table for pages translations ...
11:05:42 <thierry> From the redactor point of view, having x languages version in the page is not easy easy to understand
14:59:48 <artisticMink> Hello, i upgraded to 7.1 from 6.x with the issue of old content elements getting rendered in the FE but not showing up via BE->New Content Element. I've gone trough the migration sheets as well as making sure it's not a cache issue. Tried to establish a new CE from the documentation example, no success. I'm a little lost right now.
15:05:16 <artisticMink> Got the error, my bad. Clarified in Migration to Flux 7.1, Documentation.