09:46:31 <jlumpe> i assume i do need the intermediary page between the root and "test"
09:47:03 <jlumpe> So I'll just rename Home to root, exclude it from the pagepath and be done with it i guess?
09:47:21 <bjo3rn> I don't think so. this is what works for me in all pages: https://www.dropbox.com/s/bzhd6ivi4vtjdjw/Screenshot%202014-06-13%2009.50.03.png
10:57:39 <Guest|82906> Hey guys, i have a problem. I made an extra extension which includes a Template, with Templates-Partials-Layouts. But in T3 the Template is not displayed. https://gist.github.com/anonymous/17a67f0396057f5271fa this is my setup for this ext
11:17:31 <Guest|82906> but i need to register it in the ext tables of my main extension correct?
11:17:36 <jlumpe> do FCEs suffer from caching issues? that is: sometimes they load, sometimes they're broken, and i can change my template around to figure uot what's wrong, but it makes no difference?
11:18:09 <bjo3rn> Guest|82906 register it in the extension containing the templates.
11:18:38 <bjo3rn> jlumpe that's danilobuerger or NamelessCoder country I'm afraid.
11:19:21 <cedricziel> jlumpe: there's aswitch for that in flux EM config
11:19:41 <cedricziel> ach.. same typo over and over again .. "a switch"
11:26:54 <jlumpe> 1225709595: Template could not be loaded. I tried "/www/htdocs/w0120a21/conceptfactory.de/public/typo3conf/ext/fluidcontent_core/Resources/Private/Templates/CoreContent/Fluidcontent_content.html"
11:27:13 <jlumpe> hhappens when nesting fluidcontent_core in an FCE
11:36:03 <Guest|50799> Sorry guys... i just told you that my templates of my subext are not displayed.. now i have the same problem with FCEs. but i already register it with \FluidTYPO3\Flux\Core::registerProviderExtensionKey($_EXTKEY, 'Content');
11:37:24 <jlumpe> cedricziel: i'm just trying to add a FCE to the page
12:13:42 <dasFelix> ahh... in array form there is variable extensionName--- {form.extensionName}
12:29:15 <jlumpe> anybody availabe to assist with a (for me) major issue?
12:29:39 <jlumpe> FCE just won't render any children. I also tried to used the Row element from fluidcontent_bootstrap - same issue, nothing is r endered
12:51:46 <jlumpe> ok i could narrow my issue down: the main section of the content element is rendered, but flux:content.render does not return anything
12:52:11 <jlumpe> i also tried it with 2 columns with fixed names - notihng is being returned
12:57:10 <jlumpe> cedricziel, xaver, danilobuerger: is is normal that in the backend when adding content to a column the name of the column is being posted instead of the name of the content area as defined in the config?
16:04:45 <dasFelix> hmm... I am looking for a dropdown multilevel navigation example with <v:page.menu> ... do you know a resource. I struggle with the construction :-/
16:07:00 <dasFelix> I can realise this with typoscript and include that by <f:cObject typoscriptObjectPath="lib.mainNavi" />
16:07:01 <dasFelix> ... but I'd prefer a fluid/vhs/fedext-only solution
16:09:11 <xaver> dasFelix: use as and do your own foreach
16:09:20 <xaver> you can build everyhting e.g. bootstrap
16:14:25 <dasFelix> thx @xaver I think something with my for as construction is wrong. I'll try
16:15:14 <xaver> Denyerec: your tree bug is gone :)
16:33:03 <cedricziel> xaver.. i'm a bit disappointed... no findbugs, no pmd no nothing plugins for bamboo
17:05:54 <NamelessCoder> cash2m no, no such possibility except the old {namespace=...} declaration. If you add these for autocompletion in your layouts, they will be output. However: if you have a need for autocompletion in your layout it suggests you put too much code into the layout - perhaps you should move some to shared partials.