00:30:38 <Outdoorsman> I do hav a question still being new to TYPO3 6.x having jumped straight from 4.7.x. How do I utilize the Relations tab that's present on on CE's, what's the practical application?
00:33:13 <NamelessCoder> you can add child content elements without closing an FCE you're editing - when you add the child content it has selectors to choose the column name of the parent
00:33:28 <NamelessCoder> and you can handle localization in that tab as well
01:39:27 <Outdoorsman> Relations are waaaaay too cool. Nice.
02:25:50 <Outdoorsman> NamelessCoder. I found a potential issue with workspaces in fluidpages. I created a new issue there... https://github.com/FluidTYPO3/fluidpages/issues/191
09:52:51 <pRiMU5> ok. with that, its working with fullpath. but ill get an error too when i am saving.
09:53:05 <pRiMU5> #1: PHP Warning: explode() expects parameter 2 to be string, array given in /var/www/ghs2014/typo3_src-6.2.3/typo3/sysext/core/Classes/TypoScript/Parser/TypoScriptParser.php line 225
11:23:35 <Kaimane> With fluidcontent_core I add a new CE with ctype 'text'. Tab 'appearance' shows two tabs. One of it 'Container'. When I activate class 'container' save and reload frontend there is no wrapping element with class container. Is that a but or my mistake?
11:27:40 <Kaimane> Or does container mean something entirely different?
11:39:58 <pRiMU5> mrboe: no its working. ive changed all my templates...
11:49:28 <pRiMU5> thanks. for my usage i need an object. and for every object i need 2+ images.
11:49:59 <pRiMU5> btw. have you ever used the v:media.image? in the doku it says: src = Path to the media resource(s). Can contain single or multiple paths for videos (either CSV, array or implementing Traversable).
11:50:22 <pRiMU5> but when i transmit the viewhelper the csv from my object, it says, that the image could not be loaded.
11:50:39 <pRiMU5> Could not get image resource for "fileadmin/user_upload/IMG_0189.JPG,fileadmin/user_upload/IMG_1152.JPG
11:50:49 <pRiMU5> a bit confusing. i thought i can use csv
11:53:28 <pRiMU5> i will go through the class and take a look whats happening there.
11:54:54 <mrboe> if you use objects you first have to use something like "for each oject"
12:42:34 <Kaimane> Sry for asking a second time: is there a quick fix for wrapping a ce with a div by selecting a container class in EXT:fluidcontent_core?
13:54:31 <Kaimane> Found the bug why fluidcontent_core does not wrap a content element with e.g. a div tag.
16:24:50 <Kaimane> cedricziel: I added the prefix to the pull request. but how is it possible to change the commit title?
16:27:39 <BenjaminR> Kaimaine: are you use any gui with git?
16:30:38 <Kaimane> BenjaminR: no. i am absolutely new to github and use github.com for now :-/
16:31:06 <BenjaminR> then you will not be able to fix the commit messages. i think we should help you here and take over
16:31:31 <BenjaminR> do you want to comment on the github pr and tell us that you are using github.com for your pr?
16:31:41 <BenjaminR> then one will taker over here i guess
16:49:05 <cedricziel> i need my github graph to become a little greener
16:56:43 <Kaimane> Thank you cedricziel for squashing the commits together.
17:19:13 <artisticMink> Hello, i just updated to the most recent version of flux, vhs and fluidpages. Now on editing a page i recieve this error: http://pastebin.com/t63pinwj Could this reffer to an namespace problem in my templates which got ignored before?
17:29:58 <artisticMink> Fixed the namespaces. Really seems like a semantic problem. Ugh. And here we go.
17:31:51 <NamelessCoder> I personally fixed that bug almost a year ago ;)
17:31:58 <artisticMink> Oh well, it's probably http://fluidtypo3.org/blog/news/flux-71-changes.html. I should have read it first before updating.
17:32:20 <NamelessCoder> it's your core version, no looking up the alias when class is an alias of another
17:32:54 <NamelessCoder> correct it by updating the core or by using the proper namespace (and be careful not to use aliased viewhelpers in general). Core update recommended.
17:33:38 <artisticMink> I probably missed the core update. Thanks.
17:38:41 <ltrebing> NamelessCoder: have you maybe seen my question here yesterday? xaver suggested that I ask you :)
17:39:30 <NamelessCoder> you may need to repeat your question
17:40:29 <ltrebing> NamelessCoder: I’m trying to minimize my template records, so I thought that instead of having two static includes (one for fluidcontent_core and one for my provider extension) I could have just one for my provider extension and then include the fluidcontent_core stuff there via INCLUDE_TYPOSCRIPT
17:40:39 <ltrebing> but then tt_content.list is broken
17:41:16 <ltrebing> so apparently including it via the static include thing triggers some magic that doesn’t happen otherwise
17:41:41 <NamelessCoder> the FCC TS is loaded using so-called contentRender-identified templates
17:41:53 <NamelessCoder> those are loaded in pretty much the most insane way you can imagine
17:41:55 <ltrebing> so it’s just not possible with less than two static includes?
17:42:12 <NamelessCoder> summa summarum: they must be loaded this way and you can only override, not exchange, the loaded config
17:42:28 <NamelessCoder> see generated AdditionalConfiguration.php in your typo3conf
17:43:06 <NamelessCoder> this file identifies the template that must be loaded before all plugin statics regardless of method used, also preceeding the quite unwanted ext_typoscript_setup.txt load order
17:43:30 <NamelessCoder> CSC does the exact same thing simply because it has to :/
17:44:27 <NamelessCoder> using INCLUDE_TYPOSCRIPT is almost exactly the same as including an additional TypoScript template. Some might even say it's less consistent, because a special flag has to be enabled on the TS parser to process includes.
17:45:16 <NamelessCoder> in the end it has the same impact - two files must be read, as includes. But you do save ONE iteration of the static inclusion loop ;)
17:45:19 <ltrebing> ah, so basically that famous AdditionalConfiguration line ensures that the core does something *after* loading this particular template but *before* loading any other templates?
17:45:55 <NamelessCoder> the line in additionalconfiguration has only a single purpose: when core builds TS it builds a special name for the static resource. If this name is present in that array, it is shifted to the beginning of includes
17:45:55 <ltrebing> what I prefer about INCLUDE_TYPOSCRIPT is that I have only one entry point in the database and everything else is nicely tracked by Git
17:46:27 <NamelessCoder> true - it's about the same in the end. When it's possible, that is :)
17:46:54 <NamelessCoder> that TS inclusion method is the least pretty thing about FCC
17:47:23 <NamelessCoder> without it though, no plugins could render
17:47:34 <ltrebing> so I guess it might be possible to get the same result by changing the AdditionalConfiguration line so that it points to my provider extension TS instead of that of fluidcontent_core?
17:47:44 <NamelessCoder> yes, that's one way to solve that
17:47:54 <NamelessCoder> then you'd have zero includes
17:48:19 <ltrebing> wait, wouldn’t I still need to have one for my provider extension?
17:48:29 <NamelessCoder> that may be wrong: you'll have one include. It still has to be added as template to be loaded properly
17:49:25 <ltrebing> that’s another thing that confuses me: if the FCC template thingy is already referenced from AdditionalConfiguration, why do I still need to reference it from the template record as well
17:49:54 <NamelessCoder> short answer is "look at the core code around contentRenderTemplates"
17:50:29 <ltrebing> but I guess I should just accept this as a matter of fact, grumble a bit about this ugly legacy stuff, and carry on doing actual work
17:50:32 <NamelessCoder> basically this array is not an inclusion instruction and cannot be used as one. It's a registry, identifying a specific inclusion as "must come before everything else"
17:51:11 <NamelessCoder> the core gives CSC privilege by including this definition in the core itself. I can't do that for FCC.
17:51:31 <NamelessCoder> so even with CSC you still must load the TS, just like here, or it's just not present
17:52:00 <NamelessCoder> I suppose I can make sense of that decision but the mind boggles why it was implemented this way, requiring such low level configuration
17:53:08 <NamelessCoder> anyway, do what I do: shake your head, be happy it works and that the install script I wrote can create this file - and exploit this knowledge for your own benefit if you ever run into something similar
17:53:35 <ltrebing> yeah, looks like that’s the best option
17:53:38 <NamelessCoder> 't check for this file on every request, of course
17:54:47 <NamelessCoder> took me a full day to find out why, in the perspective of loading order, it had to be done this way and how to do it for non-system extensions - so yeah it should be the optimal way