09:48:19 <soee> hmm i did and upgrade to latest TER versions flux, fluidcontent, fluidpages, vhs on one server and now i dont have my pages layouts in backend just 4 default columns
09:48:32 <soee> though in page properties the one from fluidpages is selected
10:23:39 <foooobear_> i have been upgrading a site from 6.1 to 6.2 and following that, flux and vhs. since then i am getting errors with a custom content element.
10:24:59 <foooobear_> Fatal error: require_once(): Failed opening required '.../src/typo3conf/ext/flux/Classes/Service/ContentService.php' in ../src/typo3_src-6.2.4/typo3/sysext/core/Classes/Core/ClassLoader.php on line 17
10:25:14 <foooobear_> when view a page in backend page module
10:25:27 <bjo3rn> all extensions are the current ter versions?
10:41:09 <bjo3rn> well: fed is dead, gridelements not required, everything else is good today.
10:42:11 <foooobear_> that's good news. but for me it's coming a bit too late. i have to finish up this project and most likely won't use TYPO3 for a new project anymore
10:42:17 <bjo3rn> anyway, I have around 10 sites in production build on ft3 and I'm quite conservative coming from tv.
10:42:38 <foooobear_> despite working with typo3 for about 10 years...
10:43:02 <bjo3rn> that's more thatn twice the time I do ^^
10:43:12 <bjo3rn> where do you switch to after TYPO3?
10:43:51 <foooobear_> it depends, drupal, processwire, sometimes rails or silex, symfony only depending on nature of the project
10:44:40 <bjo3rn> I see. I dropped Drupal after v6 and switched to TYPO3. apps with sf2.
10:45:16 <bjo3rn> speaking of which. got to get back to work. cya
12:04:41 <Xatenev> Ive got this error The key "TYPO3\CMS\Fluid\ViewHelpers\FormViewHelper->formFieldNames" was already stored and you cannot override it.
12:04:57 <Xatenev> when i delete the <form> tag around my search, it works again, but its no form anymore
12:05:02 <Xatenev> its definetly not nested in another form
12:22:18 <erredeco> is there a complete example somewhere ;) ?
12:24:56 <NamelessCoder> sorry: array_flip, not array_reverse
12:31:01 <TorstenFink> hi, in fluidpages, ext_localconf.php Line 27-33, wird das backendlayout eingebunden, dort ist eine prüfung auf kleiner gleich 6.2 das erscheint mir falsch und müsste wohl nur kleiner sein, seht ihr das auch so?
13:14:49 <bjo3rn> so this condition is for future t3 versions?
13:19:03 <NamelessCoder> yes: it measures "core must be AT LEAST 6.2 but we'll prepare for 6.3, 6.4 etc."
13:19:28 <NamelessCoder> since the pattern used there, is introduced in 6.2 and is expected to stay - even to be propagated to other areas
13:19:46 <bjo3rn> then it's all good and I'll stfu ^^ thanks
13:36:58 <soee> devlog shows this: The singleton "FluidTYPO3\Flux\Configuration\BackendConfigurationManager" needs a prototype in "queryGenerator". This is often a bad code smell; often you rather want to inject a singleton.
15:00:49 <TorstenFink> Hi, i'm using the TER Versions of flux, fluidcontent and fluidpages with TYPO3 6.2.4, i don't see the "Paste" Icon in the Pagemodule, is this a bug or a feature?
15:01:52 <TorstenFink> its missing after each content element
15:27:35 <foooobear> i have just installed fluidcontent and fluidpages now have the folloing exception when viewing the frontend: #1225709595: Template could not be loaded. I tried "/Users/.../relaunch/src/typo3conf/ext/fluidpages/Resources/Private/Templates/Page/Default.html"
15:28:39 <foooobear> am i missing something, i was checking out the builder for creating a content provider extension
15:29:47 <foooobear> i do not plan to use fluidpages
15:31:19 <NamelessCoder> foooobear if you selected to include page templates in your provider extension generated by builder, a dependency is added for fluidpages. The error you see indicates that no page template is selected in the root line
15:33:06 <foooobear> i was generating the ext with the --content 1 --controllers 1 arguments
15:33:30 <foooobear> are the page template implicit here?
15:39:16 <foooobear> Tx_Flux_Core::registerProviderExtensionKey('portal_slider', 'Content'); was added. however the error persists after removing that line
15:39:50 <foooobear> i'm using 6.2.4 btw with flux 7.1.0
15:41:54 <NamelessCoder> in your provider extension's ext_emconf.php, if fluidpages is listed in dependencies the extension was generated with page support enabled. You can remove this depedency in the ext_emconf.php file or you can recreate the provider extension, explicitly adding "--pages 0" to arguments. Then in extension manager, uninstall fluidpages and add whichever page rendering you yourself prefer to use.
15:43:00 <foooobear> but is the FR supposed to break only by installing the fluidpages extension?
15:43:19 <foooobear> i removed the pages dependency
15:43:21 <NamelessCoder> The error you see indicates that no page template is selected in the root line
15:43:31 <NamelessCoder> if fluidpages is installed a template selection is required
15:45:13 <foooobear> ok, thanks. i removed fluidpages. now i got rid of the error
15:47:51 <foooobear> btw. before upgrading flux i was using
15:48:57 <foooobear> is that deprecated or something? after the update all backend previews are broken
15:50:27 <foooobear> broken meaning: the preview template is applied to every content element on the backend page
15:51:07 <NamelessCoder> perhaps you set the expected CType incorrectly or were actually intending to use registerFluidFlexFormPlugin
15:51:44 <foooobear> well, it was working all fine unil i updated to 6.2 and flux 7.1
15:52:53 <foooobear> i could not find any documentation on that except the docblock comments
15:56:00 <NamelessCoder> maybe you set fieldname to NULL - I can't say without knowing your code
16:00:07 <foooobear> sure, but it should still work without any adjustments after the upgrade to 7.1?
16:00:57 <foooobear> that's what i wanted to know. so i know if i should look further into it.
16:01:41 <NamelessCoder> that depends on which values you passed. Bugs have been fixed, also in the typo3 core, which affect (among other things) resolving of a Provider attached to a specific field
16:03:51 <NamelessCoder> if you share your old registration code I may be able to help
16:08:25 <NamelessCoder> array('templateRootPath' => '/path/to/templates') etc.
16:08:47 <NamelessCoder> whether or not they are required depends on your template file's usage of partials and layouts
16:09:38 <foooobear> ok, i will try that. the flexform is loaded though, as is the template
16:12:48 <NamelessCoder> same form also being displayed when editing any content type?
16:18:25 <NamelessCoder> I'm interested in why https://github.com/FluidTYPO3/flux/blob/development/Classes/Provider/ContentProvider.php#L89 returns TRUE for other list_types and content types...
17:23:29 <foooobear> NamelessCoder: i think i found the bug
17:23:57 <foooobear> i'm sure this commit introduced the regression: https://github.com/FluidTYPO3/flux/commit/34ff5982b54b02437fcfef3a1ad9a8c5915105fa?diff=split
17:24:28 <foooobear> if i revert the changes, i the preview is only applied to the correct content element
17:26:07 <foooobear> i'll try to narrow it down to the exact condition. should i try to make a pull requesT?
18:31:49 <bjo3rn> foooobear absolutely. PRs are always welcome.