06:00:45 <feelx75> Hi Channel :) I'm using Flux/fluidtypo3 github (dev branch) and T3 6.10-rc1. Is there any known issue with drag and drop of content elements between flux columns. Sometimes the green 'destination-bar' is missing. Sometimes the dropped CE disapear. CE are normal T3 elements (text/header or images).
06:48:24 <Kaimane> Hey guys. Trying to get json data via ajax from extbase controller action. How to disable the "parsetime" output in the last line?
06:49:30 <Kaimane> Set ['FE']['debug'] to 0, config.debug = 0 but parsetime is still rendered.
07:22:54 <Torsten85> hey... is it possible to specify fluidcontent elements with "allowedContentTypes" inside flow:grid?
08:22:12 <feelx75> Torsten85, you mean flux:grid, right?
08:22:48 <feelx75> Torsten85, please refer to: https://fluidtypo3.org/blog/news/coming-changes-in-flux-72.html - See Typoscript overrides (at the bottom)
08:23:31 <feelx75> Torsten85, "Although this feature is still on the drawing board and cannot be described in detail (...) will for example allow the integrator to use TypoScript to control which page/content template may be used, as well as selectively override settings like the sorting value of Fluidcontent elements or the allowed content types inside a Fluidpages-enabled page template's Grid.
08:25:09 <feelx75> I think there will be a feature sometimes... i.E. with the flux:form.options VH. Actually I don't know a way... but just found this above in the blog
08:32:10 <NamelessCoder> Torsten85 set on flux:grid.column, attribute options="{Fluidcontent: {allowedContentTypes: 'C,S,V'}}" where the C,S,V part is a comma separated values list of tx_fed_fcefile values that are allowed.
08:40:48 <Torsten85> NamelessCoder thanks for your help, but I can't get it to work. Is there an example somewhere?
08:48:10 <Torsten85> I think I missing something. How should the variables attribute on a flux:grid.column tag look like if I only want to show one specific fluid content element? all other elements (text, image ....) should be hidden
08:54:05 <Torsten85> NamelessCoder Me again.. I think I found a bug! here you return the array key "tt_content": https://github.com/FluidTYPO3/flux/blob/development/Classes/Hooks/WizardItemsHookSubscriber.php#L111
08:54:39 <Torsten85> but here you still traverse to that key (which is non existent) https://github.com/FluidTYPO3/flux/blob/development/Classes/Hooks/WizardItemsHookSubscriber.php#L138
09:01:41 <feelx75> Torsten85, maybe it works like this? https://www.snip2code.com/Snippet/198359/Allow-Deney-Fluid-Content-FCE-s-in-colum
09:14:08 <Torsten85> feelx75 yes this works for columns inside page templates but not inside content templates due to the bug i mentioned.
09:16:54 <cedricziel> Torsten85: Give me a second to traverse your previous conversation :9
09:17:22 <Guest|66253> hi i use v:page.menu to build an menu... my menu does not include the L param for languages... when i use v:page.languageMenu to build a language-menu it is included... are there any settings for v:page.menu to support languages?
12:43:51 <shaggz> Hey guys, is there a way to simply link the sections in a fluidcontent element?
12:44:47 <shaggz> I'd like to set an anchor for some content elements to jump directly to tit
12:48:27 <NamelessCoder> I don't think it's possible but you can of course always manually type an anchor link
12:50:04 <shaggz> Would you recommend to use fluidcontent_core instead of csc?
12:50:24 <NamelessCoder> it completely depends on your requirements for other exts.
12:50:44 <NamelessCoder> a lot of other exts depend on csc and you can't use both at the same time
12:51:20 <NamelessCoder> if you prefer TS to define how your content should be rendered, CSC is your friend. If you prefer Fluid, FCC is the better choice.
12:53:05 <shaggz> Okay, then I have to check if I have to choose CSC because I really don't like the TypoScript ;)
12:53:39 <NamelessCoder> plan your dependencies ahead, then there won't be any headaches later ;)
14:20:55 <f000> Hello... I'm trying development branches of flux, vhs, fluidcontent and fluid pages because of performance issues with (now deprecated) flux.widget.grid. After upgrade I can't see any elements in Page->Columns view. It shows just "(Not assigned)" in the content area... Do you have any clue how to solve it?
14:23:32 <NamelessCoder> f000 did you read https://fluidtypo3.org/blog/news/fluidcontent-and-fluidpages-released.html?
14:26:18 <f000> NamelessCoder: sure, with master branches of flux etc. there were no problems
14:30:21 <f000> NamelessCoder: if I select "Page Layout: Fluidpages" there is no content and if I select "Page Layout: None" there are 4 columns with content my FCEs in the Normal column
14:40:50 <NamelessCoder> did you also see https://fluidtypo3.org/documentation/templating-manual/appendix/migration/to-flux-71.html#after?
15:01:36 <f000> NamelessCoder: my page template is like <f:section name="Configuration"><flux:form id="default">...</flux:form><flux:grid><flux:grid.row><flux:grid.column /></flux:grid.row></flux:grid></flux:form></f:section>
15:01:55 <f000> NamelessCoder: I think this might be the problem
15:02:16 <NamelessCoder> your flux:grid.column must have a columnPosition value
15:04:19 <f000> NamelessCoder: This looks like I need complex update of tt_content table :(
15:05:20 <NamelessCoder> SQL schema? If so, that's definitely important
15:14:09 <f000> NamelessCoder: I thought to change tt_content colPos... but I was wrong.. now I tried to just add colPos parametr and it works!!! thank you!
15:37:00 <NamelessCoder> it should contain a vendorName entry, that block
15:37:53 <NamelessCoder> if you have a provider extension which contains controllers and those controllers extend that old class, change it to the new one
15:43:12 <f000> yes vendorName was the issue... now everyting works... thank you again!
15:45:40 <f000> NamelessCoder: can you say when we can expect relase of Flux 7.2?
16:16:21 <NamelessCoder> well it all depends on how quickly we can get the last issues closed - if you want to take a look at some of it, the todo list is: https://github.com/FluidTYPO3/flux/milestones/7.2
16:17:08 <NamelessCoder> you can also help just by testing the reported problems in those issues - some may have been closed by other fixes
17:24:15 <Outdoorsman> I'm getting this error from my provider extension which overlays fluidbootstraptheme...
17:24:44 <Outdoorsman> #1225709596: The template files "/home/some_directory/public_html/typo3conf/ext/fluidbootstraptheme/Resources/Private/Layouts/Page.html", "/home/some_directory/public_html/typo3conf/ext/fluidbootstraptheme/Resources/Private/Layouts/Page", "/home/some_directory/public_html/typo3conf/ext/provider_extension/Resources/Private/Extensions/Fluidbootstraptheme/Layouts/Page.html", "/home/some_directory/public_html/typo3conf/ext/provider_extension/Resources/
17:24:44 <Outdoorsman> Private/Extensions/Fluidbootstraptheme/Layouts/Page" could not be loaded.
17:25:33 <Outdoorsman> There's a more information link that points to this info: http://typo3.org/go/exception/CMS/debug/1225709596
17:28:59 <Outdoorsman> I have no idea why it's looking for Page.html, that file doesn't exist in my provider extension and the text "Page.html" doesn't exist anywhere in any of the other files. I don't get this error when I uninstall my provider_extension, so fluidbootstraptheme is working properly.
17:36:58 <Outdoorsman> Here's an error in Apache error log...
17:37:00 <Outdoorsman> PHP Fatal error: Class 'Tx_Fluid_Core_Parser_SyntaxTree_TextNode' not found in /home/some_directory/public_html/typo3conf/ext/view/Classes/Override/Parser/SyntaxTree/ExtendedViewHelperNode.php on line 86, referer: http://www.example.com/typo3/backend.php
17:38:09 <Outdoorsman> I'm still working on the same issue from yesterday NamelessCoder though this error started happening when I uploaded the extension you modified for me.
17:39:18 <Outdoorsman> I'm using PHP 5.4.16, Apache 2.4
18:20:59 <NamelessCoder> yeah - I assume you're just using it for EXT:news so do the same with that as you did with fluidbootstraptheme to override templates without having to copy all of them
18:23:29 <Outdoorsman> Okay... I've uninstalled view and modified setup.txt.
18:24:15 <NamelessCoder> don't forget to unset the existing view setup like the other one - I'm not sure it uses the plural names for paths.
18:25:55 <Outdoorsman> Ahhh I was wondering about that very thing, the plurl paths thing.
18:26:57 <NamelessCoder> the singular naming is considered legacy and gets used as fallback
18:28:03 <Outdoorsman> Well I'm still gettting the same "The template files __ ___ ___ __ could not be loaded."
18:31:49 <NamelessCoder> with the right paths or the ones from EXT:news only?
18:32:49 <Outdoorsman> I don't even ahve EXT:news installed or configured on this site yet.
18:43:35 <NamelessCoder> Page.html doesn't exist in fluidbootstraptheme/Resources/Private/Layouts/ here in my copy. Did you create it in your own Layouts folder? If not, it is expected to fail.
18:44:06 <NamelessCoder> possible Layouts are: Content, ErrorPage, FCE, FrontPage, Render or WithSideBar
18:44:30 <NamelessCoder> you probably want one of the FrontPage, Render or WithSideBar values as <f:layout>
18:53:51 <NamelessCoder> but another Q is: are you sure you want to add a *new* page template selection instead of *replace* an existing one from fluidbootstraptheme?
18:54:23 <NamelessCoder> if you want to *replace* you need to rename the file so it matches the name of the template file in fluidbootstraptheme - and you should make sure to use the same "id" value for flux:form in your override.
18:55:39 <NamelessCoder> in particular, "Render" may be a very bad name to choose as it also matches the default action used to render the page. You'll be better off in the long run with more appropriate names. Name length is not an issue ;)
18:56:07 <Outdoorsman> So I think that Templates/Page/Render.html and Templates/Content/Example.html were both created when I used Builder to create the provider extension and that <f:layout name="Page" /> was still in there from Builder.
18:56:41 <NamelessCoder> yeah I think Builder is actually creating that file. It needs a touch-up too, because it sets the old singular name template paths
18:56:42 <Outdoorsman> I can just delete Templates/Page/Render.html if I haven't customized it right?
18:56:58 <Outdoorsman> It will fall back to the fluidbootstrap theme one.
18:57:16 <NamelessCoder> if you delete the file and any pages currently have it assigned as template file and it doesn't exist in fluidbootstraptheme then yes, an error will be shown (until you select another page template)
18:57:53 <NamelessCoder> in this case it does exist so that should be fine
18:58:42 <Outdoorsman> Well I'm out of time now. I have an appointment to be at thanks for your help. I'm not getting that template errors any more although the overlay doesn't seem to be working yet. At least I can move on to debugging that now. What an ordeal a simple line made.
18:58:56 <Outdoorsman> I would NOT have understood that without you.
18:59:12 <Outdoorsman> I have to run... have a good one and thanks for the help again!
18:59:21 <NamelessCoder> it's easy to get off track and not really see it until much later, after you've been through everything else