02:39:26 <ndee> I added an input field "settings.nav_icon" in a page template. In my layout, where I render my v:page.menu, I would like to access that value. Is that possible?
03:40:04 <Danny^^P> Hey! I'm using <f:render partial="header" arguments="{_all}" /> in my Layout. In the partial I like to use something like <v:asset.style... But the tag is not rendered. It is just printed into html. What will I have to do, that it is correct rendered?
06:52:31 <Guest|54558> Hi! I've build a new template with fluid. I like to use the default FCEs like Text, Text with picture etc. How can I template them? or will I have to build them complete by my own again?
07:40:01 <NamelessCoder> Guest|54558 if you used fluidcontent_core you can replace individual templates. If you didn't, you're probably using css_styled_content and your only option to "template" the built-in content types is to modify their TypoScript object structures.
07:45:28 <boOgiE> is there a "special" section name for direct_mail in plain version
07:46:19 <boOgiE> i get these message instead of the content: [Nicht angezeigte Inhaltselemente: fluidcontent_content ]
07:52:15 <boOgiE> does anybody know what i'm talking about?
07:57:05 <Guest|54558> NamelessCoder: Thank you! I looked at fluidcontent_core and tried first with variants. I have definied one and can select them. But in frontend I get only "Oops an error occured"
07:57:44 <NamelessCoder> disable the production exception handler to get an error message that isn't useless
07:58:53 <Guest|54558> ah, found it... there was a typo. Now it works. Thank you very much!
08:38:29 <boOgiE> can someone help me plz, i try to explain my issue: i'm using fluidTYPO3 with my own defined content elements. everything works fine except the plain version of directmail. In these template the fluid content elements are not parsed, i get "[Not displayed content items: fluidcontent_content ]"-Error message instead. does anyone know how to fix it? i hope my explanation was understandable
08:44:48 <NamelessCoder> boOgiE direct_mail isn't finding the rendering instruction for plugins - I assume this would also affect any other non-core CE.
08:46:28 <NamelessCoder> internally, the rendering instruction gets created from ext_localconf.php just like any other plugin. It gets added as TypoScript definitions (see core's configurePlugin etc. methods) and it appears those definitions aren't available.
08:47:09 <boOgiE> ok, thanks for the hint, i try to fix that :)
08:47:21 <NamelessCoder> - unfortunately there could be a thousand different reasons why this is happening, so you *will* need to hunt for explanations on the web about custom plugins with direct_mail - I'm sure someone else has experienced this
08:47:43 <boOgiE> never used plugins with directmail before -.-
08:48:43 <NamelessCoder> I'm guessing now, but direct_mail may be using a custom page type or a simulated frontend context which causes your TS to be cleared somehow.
11:16:36 <NamelessCoder> haven't used direct_mail for at least two years and it's kind of off topic. #typo3 might help.
11:16:49 <Xatenev> NamelessCoder: ye i asked there aswell :) ^^
11:16:53 <Xatenev> Just thought u maybe know about it
17:08:19 <Guest|7764> Hi! I've played around with fluidcontent_core and defined some own variants of the Text Content Element. I'd like to do something similar with the image element. But how can I get the images in my template?
17:56:34 <NamelessCoder> Guest|7764 the v:resource.* ViewHelpers - or a custom controller (the latter is often a better idea for performance, the former a better idea for extendability)