06:32:35 <toph> Hi everyone. I upgraded my FluidTYPO3 extensions from GitHub (master branch) and now I'm just getting a fatal error: Call to a member function resolvePrimaryConfigurationProvider() on a non-object in typo3conf/ext/flux/Classes/Service/FluxService.php on line 373. What do I need to look at?
06:38:30 <Kalypso63> have you upgrade fluidpages too (version 3.2.0) ?
06:39:14 <toph> yes. did a fresh git clone on both.
06:39:44 <Kalypso63> clear cache system via install tool and compare database too
06:42:12 <toph> Oups, rookie mistake. Forgot to compare database. My bad.
06:42:40 <toph> However, now I'm getting: Uncaught TYPO3 Exception
06:42:40 <toph> #1: PHP Warning: strpos() expects parameter 1 to be string, array given in typo3conf/ext/flux/Classes/Utility/ExtensionNamingUtility.php line 27
06:43:55 <braguzz> I've update some ext but I got this Could not analyse class:Tx_Vhs_ViewHelpers_Extension_Path_ResourcesViewHelper maybe not loaded or no autoloader?
07:05:35 <NamelessCoder> you're rendering your menu manually but nowhere are you defining any <ul> or <li> tags, you only define a link that should be generated and this link will always be an <a>
07:05:45 <NamelessCoder> if you want the ul/li there, you have to add them
07:06:33 <NamelessCoder> the other thing is you should consider not using <f:link.page> to render the page link. In {subItem} you will have the {subItem.link} property which contains a pre-rendered link created exactly the way f:link.page would do it.
07:06:43 <NamelessCoder> (you can save a viewhelper call so you should)
07:08:27 <NamelessCoder> last: if you expect an ul > li > a structure and do not need any class names (from your example it doesn't look like you do) then the automatic rendering of plain and simple <v:page.menu /> (levels>1) will create exactly that output (with some added css classes)
07:08:55 <NamelessCoder> if you expect a nav > a structure you can manipulate "tagName" and "tagNameChildren" on v:page.menu
07:09:15 <NamelessCoder> (the automatic rendering fits many cases but not all)
07:13:47 <Jomungand> i was reffering to https://worksonmymachine.org/blog/a-guide-to-menu-rendering-with-fluidtypo3
07:14:19 <Jomungand> btw, my nick before was jonasjo, we already talked about that ;)
07:15:16 <Jomungand> what else then instead of <f:link.page> ?
07:45:16 <Jomungand> ah, ok, i guess it is faster? or what is the advantage here?
07:46:26 <NamelessCoder> yep, faster because link is already built and you don't need to do that again
07:48:42 <toph> I have a new site with all the latest (master) versions from git and I'm using fluidcontent_core instead of css_styled_content. I have created a provider extension with a custom content object, which correctly gets picked up in the display. However, for some reason, only the header is rendered in the frontend. Any ideas?
07:49:40 <NamelessCoder> run the fluidcontent_core install/update script from EM, toph
07:51:49 <toph> Configuration and preview in the backend work fine. Just the rendering doesn't.
07:52:10 <NamelessCoder> if you want the FCC handling of header/wrapper rendering you'll need to either copy the Layout from fluidcontent_core, replace your Layout root path (if this is possible) or name your own Layouts in a way that you can add the fluidcontent_core layoutRootPath so it gets checked after your own layoutRootPath (plural names in TS array)
07:52:59 <NamelessCoder> the key here is: your Layout doesn't use v:tag and doesn't have the small conditions required to show/hide header and to render it with the appropriate H(n) tag
07:52:59 <toph> No, the header is fine. It's the content itself that's not rendered at all.
07:55:21 <toph> Here's my layout file (just the standard one, in my_provider_ext/Resources/Private/Layouts/Content.html): https://gist.github.com/potofcoffee/0f545c2f669616ffac88
08:38:18 <NamelessCoder> that, and load the static TS file from fluidcontent_core, should be enough to render everything correctly
08:38:55 <NamelessCoder> your problem could be that fluidcontent_core is rendering the Default.html template and not the fluidcontent plugin because of missing TS.
08:45:18 <Jomungand> in the New content element Wizard. how do i remove Text & Images since there is no element for that in fluidcontent?
09:24:02 <toph> All of this is set, TS is loaded, cache is cleared.
09:24:21 <toph> One tiny difference however: My AdditionalConfiguration.php says this:
10:17:54 <Jomungand> it was. an now it seems to be broken. also pages just get rendered if you save them. talked with @NamelessCoder about it already ;)
10:42:30 <Jomungand> well im gone. i will be back later :-P
11:09:43 <toph> @Jomungand: It actually does render quite a lot: All of the CEs defined in fluidcontent_core render finde. I also installed fluidbootstraptheme and the page templates from there render fine as well (menu, etc.)--not the FCEs, however.
11:16:29 <toph> Okay, I must be looking at some weird caching issue here -- cleared the cache dozens of times without success, and now, with no other changes, all of a sudden it works.
11:16:42 <toph> Go figure... Well, at any rate, thanks guys.
11:17:15 <Torsten85> Hey, just saw that flux ect. is now marked compatible with typo3 7.1 ... can anyone confirm that drag & drop ect. is correctly working?
11:18:04 <Torsten85> the ajax request issued by a drop action in typo3v7 seems to be very different from the way typo3v6 does this
11:23:22 <Kalypso63> Hi @NamelessCoder !! Have you got an idea or tips to resolve this issue https://github.com/FluidTYPO3/fluidpages/issues/239
11:24:38 <Kalypso63> ConfigurationService.Php -> resolvePageProvider() : the problem comes her
14:07:20 <Danny^^^P> Hi! I startet to migrate my templates to the latest version and Typo3 7.1. In my template I defined a backend layout with one column. But in Backend I see the default 4 columns. is this still a bug or have i missed something?
16:18:06 <Jomungand> can anyone point me to a working example of a manually rendered menu with at least three level using <:vpage.menu> ?
21:08:32 <Jomungand> is it by chance by mistake that 3.4 Using variables and 3.4.1 Form values are missing from the documentation on https://fluidtypo3.org/ ?