03:18:46 <batjony> does someone know anything about if the current fluidtypo3 extensions will be usable in farther versions of Typo3 CMS ?
03:21:23 <batjony> I have a lot new typo3 projects and I have to decide whether to start them with the fluidtypo3 extensions, or with something like typo3-themes.org
03:34:18 <bottoni> Hi batjony as far as I know there are no such plans for T3 v6 and 7. FluidTYPO3 is a very active project and offers you much more than a simple theme. It´s very deeply integrated TYPO3
04:34:05 <bottoni> NamelessCoder regarding last weeks issue, I raised max_input_vars after moving to another environment to 50000 and even higher but the problem persists and I don´t get a "Invalid CSRF Token" message. What is a reasonable setting?
07:58:15 <Guest|11324> Hi! I'd like to build an custom container for frontend elements like the documentation tells to do for a textpic. But how can I do this? By now, I have just dealed with Variants and Versions.
08:27:09 <bottoni> Hi Guest|11324, did you read the fluidcontent_core docs? https://github.com/FluidTYPO3/fluidcontent_core
08:29:48 <artisticMink> Hello, is there a up-to-date, 7.x-ish example for fluidpages? I checked git, but the example seemed pretty out to date, still has the tx_myextension_pathto_controller convention.
08:33:18 <Guest|11324> bottoni:Yes I have read this docs. With the help of them I could do the variants and versions. But not the container, mentioned in the chapter "Special note about the Textpic "
08:49:45 <bottoni> Guest|11324 well to have a textpic element would mean creating a variant of text with all options your layout needs to control text/image flow. The containers mentioned in the docs would mean creating a wrapping content element providing only the markup for the flow of text and image and leaving it to the editors to fill his container with separate text and image content elements. I personally choose the te
08:49:45 <bottoni> xt variant as editors most often don´t like having too much to think about which has to be inserted where
08:55:36 <Guest|11324> The textpic version I need is just a simple one. Text and Image should be displayed in a two or three column layout. Therefore I'd like to add such a new element in the general Tab, which the editors can choose. But I don't know how to start building this new element (wrapper)
09:04:15 <bottoni> The standard way would mean creating a text variant but this wouldn´t place your custom text variant under the general tab. You could make your own element as described here https://fluidtypo3.org/documentation/templating-manual/templating/creating-templates/content-element.html I recommend reading the whole chapter 3 of the docs
09:06:34 <bottoni> Placing it under the general tab should be possible with the <flux:form/> options attribute. There´s a group option which controls the tab position. I always use that for my custom tab so it´s just a guess whether there´s an id string for the general tab
09:24:04 <Guest|11324> Thank you! I will read and try :-)
09:36:43 <artisticMink> I created a PageController, however no Action gets rendered, not even the defaultAction. I made sure my provider is registered with my vendor and extension key as well as initializeView is called. What may i have missed?
09:47:07 <bottoni> template names and controller actions correspond?
09:48:17 <bottoni> and your templates are in Resources/Private/Templates/Content ?
09:49:02 <artisticMink> bottoni: Yes, since it is a page controller they're located in Templates/Page/. Also, the proper templates, selected in the backend, get rendered on page call.
09:50:06 <artisticMink> Just their correspocting middleware doesn't, which i need to assign some variables and check for mobile devices.
10:01:56 <bottoni> just checked one ov my providers nothing special in there. You mentioned all necessary steps. Did you clear system caches or manually deleted typo3temp/Caches/ and related db tables?
10:04:28 <artisticMink> bottoni: I cleared the cache manually, however i didn't check the tables. Let me take a look at the db.
10:23:14 <artisticMink> bottoni: No, even being rude and terminating the script via die(); does not have any effect, so i strongly assume the actions are never called. However, the php file in which the PageController class resides is definetly executed.
10:23:59 <artisticMink> bottoni: http://pastebin.com/15gQDMNe Yes, from what i can tell everything is proper. It worked well on Flux 6.X which i migrated from to 7.1 I went trough the migration sheets in the docs carefully.
10:43:25 <bottoni> Can´t spot anything incorrect. Is it the same with 7.4 and the latest versions auf the flux family?
10:52:41 <artisticMink> bottoni: I didn't go higher then 7.1 by now but i guess it's worth a try. Is there a release version of 7.4 or should i just check out the latest master?
10:53:43 <bottoni> yes there´s a release: http://get.typo3.org/7 or https://typo3.org/download/
10:56:23 <artisticMink> bottoni: Alright, i'll give it a try. Thanks for your help on the subject.
11:11:43 <Guest|11324> bottoni: I managed to build the Custom Content Element. Thank you very much! But it is not places under the "Typical Page Content" Tab. I used the group attribute and now I have two Tabs named "Typical Page Content". Do you have any other idea? That's my flux:form definition: <flux:form id="twoCol" options="{group: 'LLL:EXT:cms/layout/locallang_db_
11:28:57 <bottoni> That´s what I mentioned I didn´t try yet to place my custom elements under the general tab yet. I´m quite sure that the locallang label won´t do. Maybe it´s possible with an id string but I have no idea if it is nor which one would be correct. I always name my custom tab after the customer or use separate tabs if I have multiple groups myself