12:04:41 <BenjaminR> well definitely the case is that the list for the content wizard wont be generated on demand. if you add a fce you will have to clear all caches and hit the content wizard to make the list regenerate and contain the new fce types
13:09:12 <pRiMU5> BenjaminR: this isnt a new fce. but the tab (gd elements) is only available if there is at least one content element on the page. ;) thats really weird
13:19:33 <Guest|94014> Hi, i'm using staging releases from GIT for all extensions. Typo3 Version is 6.2.4. I recreated the example from http://fluidtypo3.org/documentation/templating-manual/templating/creating-templates/page-template.html . Now i do not see the grid in backend, but it seems to be here, as i can select the fields (Content + Sidebar) in columns field when
13:20:58 <Guest|94014> One thing is that i removed "{namespace v=FluidTYPO3\Vhs\ViewHelpers} " from layout and templates, as this throws an error when using it: Could not analyse class:FluidTYPO3\Vhs\ViewHelpers\Content\RenderViewHelper maybe not loaded or no autoloader? (1289386765)
13:21:37 <soee> error because the viewhelper path changed
13:23:47 <soee> Guest|94014: what VHS version are you using ?
13:33:28 <Guest|94014> 'version' => '1.9.1', from staging branch
13:34:52 <NamelessCoder> Guest|94014 you must update to 2.0+ in order to use namespaces
13:37:09 <NamelessCoder> btw, staging is mostly for confirming our releases right before they happen. Normally you'd use master or TER version in production and development branch for all new projects and for local development, as far as compatibility requirements for your project allows.
13:38:18 <NamelessCoder> Guest|94014 here you can just "git pull" and you'll get version 2.0.1
13:39:40 <Guest|79870> @soee: this is me again, i got logged out..
13:40:01 <Guest|79870> so the error went away with update to 2.0.0, but still in backend no grid: http://i.share.pho.to/876521da_o.png
13:40:09 <NamelessCoder> Guest|79870 I responded: you must update to 2.0+ in order to use namespaces, btw, staging is mostly for confirming our releases right before they happen. Normally you'd use master or TER version in production and development branch for all new projects and for local development, as far as compatibility requirements for your project allows.
13:40:14 <NamelessCoder> here you can just "git pull" and you'll get version 2.0.1
13:41:08 <NamelessCoder> backend grid is not related to VHS unless your template contains other deprecated ViewHelpers and/or you also upgraded Flux, in which case you should read the pre-release notes (esp. about flux:form.content no longer doing what it did before)
13:43:03 <Guest|79870> for flux i use 'version' => '7.1.0',
13:43:17 <Guest|79870> will try with develop branch
13:43:36 <NamelessCoder> on development branch your core must be 6.2.4+ or git master
13:44:02 <NamelessCoder> important change notes here: http://fluidtypo3.org/blog/news/flux-71-changes.html
13:44:35 <Guest|79870> just one thing, i did git pull for vhs, but still have 'version' => '2.0.0', in ext_emconf.php
13:45:28 <NamelessCoder> it's just a formality ;) but you should switch to development so you're prepared for when Flux 7.1 comes out
13:46:58 <NamelessCoder> if you want to stay on staging: I just merged the branches now so you can pull again
13:52:39 <Guest|79870> i'm now on develop with flux and vhs, still no luck with visible grid in backend. i'll switch to develop with other extensions also now
13:57:37 <NamelessCoder> if you have EXT:builder installed you can do "./typo3/cli_dispatch.phpsh extbase builder:fluidsyntax --extension myext" in CLI to check all templates, or use the BE module.
14:02:04 <NamelessCoder> if the template file is small then no need to worry.
14:02:17 <NamelessCoder> if it's big, consider putting the uncompilable ones into Partials
14:02:43 <Guest|79870> it's very small, basically it's the example from http://fluidtypo3.org/documentation/templating-manual/templating/creating-templates/page-template.html
14:03:07 <Guest|79870> should this example work with development versions and core 6.2.4?
14:03:20 <Guest|79870> i removed xml namespace tag
14:03:51 <NamelessCoder> yeah those have double namespace declarations which error out currently
14:04:00 <NamelessCoder> it's fixed but docs not re-compiled
14:05:01 <NamelessCoder> enabling debug mode in flux extension config may give more clues
14:05:12 <Guest|79870> ok, but i removed xml part already, still no grid in backend. On frontend it works!
14:05:24 <Guest|79870> i enabled debug mode, all green here
14:05:41 <Guest|79870> Flux View FluidTYPO3\Flux\View\ExposedTemplateView is able to read stored configuration from /home/adrian/Zend/workspaces/DefaultWorkspace11/typo3-base/app/typo3conf/ext/nc3d_template/Resources/Private/Templates/Page/Page.html
14:06:26 <Guest|79870> and curious is, that i can select "Sidebar" in Column field when i edit a content item. Just backend view shows only one column
14:06:44 <NamelessCoder> page properties may define not-None or not-empty as backend layout. The grid in page templates have the lowest possible priority.
14:12:01 <Guest|79870> @NamelessCoder: sorry, this i don't understand
14:15:08 <NamelessCoder> in page properties there's a field to select the currently used backend layout on this page and subpages (not the fluidpages template, it's under "Appearance"). If any page in rootline of your page has selected a backend layout record to use on subpages, it gets used. If you current page has selected a backend layout to use on this page, that gets used. If both this page and all pages in rootline have selected an empty value or the "None"
14:15:08 <NamelessCoder> option (both are empty values) then the fluidpages flux:grid gets used.
14:17:50 <NamelessCoder> if all that's in order please gist your template file's Configuration section
14:21:39 <Guest|79870> (facepalm) thanks a lot, i had a backend layout on root page used. Works like a charm now!
18:01:33 <artisticMink> Hello, by using flux, is there any way to render content while editing a content element? In example, show an image a user just selected via flux:wizard.link.