11:50:18 <mrboe> hey guys - i installed the builder ext to check my extension. i got thetese errors, but i dont know what to do? any hints? file: https://gist.github.com/misterboe/b491c02384b05d26e92e error:http://snag.gy/pJVEq.jpg
11:51:49 <mrboe> what does the warnings mean? and which viewhelper is wrong
12:49:25 <Guest|14805> Hi there, i have a problem with flux/fluidcontent, he doesnt reder the field in backendform only a "The title" field is rendered, not the fields defined in the template, any ideas? I have two extensions in one page for different trees in tree one the Text.html works fine, but in tree2 it doesnt render the fields, any ideas?
12:50:18 <BenjaminR> deny: fluidpages renders first - the third party exts that modify header overrule it (append or overwrite depends on the 3rd p ext)
12:51:06 <BenjaminR> v:page.header.meta contains some documentation about the behaviour
12:51:30 <braguzz> I moved mysql on a dedicated server without success..
12:51:52 <braguzz> apache still 100% cpu trying to erase cache
12:56:08 <Guest|14805> i have 2, each has an extension which provide typoscript files and templates for fluidpages and fluidcontent
12:57:02 <Guest|14805> and in tree2, where the templates are read from extension2, the fields are not display, what works is the selector for the contentelement and wizardtab is fine, but no fields are displayed
12:57:31 <Denyerek> BenjaminR, I have read that. What difference is there using v:page.header.meta instead of just putting>meta> tags into the template? Presumably because the VH ones are parsed alongside anything done in the typoscript ?
12:57:35 <BenjaminR> maybe some templates (TS) not included in tree2
12:58:24 <Guest|14805> no, he reads the Text.html and give me the corrrect items to choose in "New content Element"
12:59:55 <Guest|14805> any idea where to debug the reading of xml name="Configuration" ?
13:00:18 <BenjaminR> Deny: the difference is that it is a fluid viewhelper and because of this can be used anywhere and in any context/condition you d like. in the end it simply uses the pageRenderer to add meta tags
13:00:50 <BenjaminR> with the restriction that the plugin has to be cached
13:02:45 <Denyerek> and so if I use asset to add my CSS, then order and dependencies are still accounted for
13:03:28 <Denyerek> So that v:asset.style call doesn't actually have to be in the <head> part of the template
13:03:38 <Denyerek> Does my page template even *have* a <head> section ?
13:03:47 <Denyerek> I get the feeling I should install the bootstrap package and dig through that.
13:04:14 <Guest|14805> my provider extension has no classes, its only typoscript and html files, any other ideas?
13:04:17 <Denyerek> is there a "best practices" extension anywhere that's the de-facto best reference to use ?
13:04:35 <Denyerek> Guest|14805, (please set your name) - that's normal.
13:04:45 <Denyerek> If it's just a basic container, that's pretty much all it'll have I think.
13:04:52 <Denyerek> Especially if you created it with Builder.
13:05:59 <BenjaminR> Exactly Deny. Guest: EXT:builder can check all your templates. install it and it will add a backend module which is easy to understand
13:06:15 <Guest|14805> ok ill try, (how can i change name?)
13:06:38 <BenjaminR> */nick MyNick (without the star)
14:53:59 <Denyerec> randomresult - do you know if the bootstrap_pages and bootstrap_content packages are good places to learn how things work ?#
14:54:10 <Denyerec> Or is there a "best practice" example package I can grab?
14:54:30 <randomresult> well... the example package is good
14:57:48 <BenjaminR> Denyerec: but as you are new to it start with development branch on all exts. there support for 4.X has been dropped and namespaces has been introduced
14:58:07 <BenjaminR> its the feature of all FluidTYPO3 extensions
15:35:01 <BenjaminR> Deny: just reference them relative to the css stylesheet (as you are used to) - paths will be changed by fluidcontent automatically if need to cache it
15:35:48 <Denyerek> Even paths in the CSS to images and such ?
15:36:31 <Denyerek> so if they're in /resources/public/stylesheets and the images are in /resources/public/img I can happily use reletaive paths in the css ?
17:26:57 <tpinne> today I started to work on my project again since last week. I changed nothing to the sources. Core is the same git commit so are every fedext extensions
17:27:24 <tpinne> cleaning all caches before starting to work I now get the following exception wich I can't get rid off
17:27:28 <tpinne> UnexpectedValueException: The package "fluidpages" depends on "_flux" which is not present in the system. in /var/www/TYPO3.CMS/typo3/sysext/core/Classes/Package/DependencyResolver.php on line 146
17:31:18 <tpinne> sorry for bothering. Sometimes the moment you ask the question you find the answer :)
19:43:38 <Torstenn> Hi there, i'm running two pagetrees and each has its own fluidpages/content providerextension, the problem is in the second extension in backend are no fields displayed which are configured in <flux:form> section, any ideas or expirience in having two template provider extensions?
20:15:58 <Torstenn> I've debugged it and the problem is that at some point the collections key is unset in typoscript, any idea why this happens?
20:30:16 <Torstenn> if i disable the rootpage of tree1, all works in tree2, funny thing ^^
20:46:34 <Torstenn> Ok the problem is that the typoscript in backend for tx_fluidcontent is read over "$this->configurationManager->getConfiguration(ConfigurationManagerInterface::CONFIGURATION_TYPE_FULL_TYPOSCRIPT)" which only reads the first siteroot page ...
20:47:03 <Torstenn> is this a bug or must i implement the typscript for fluidcontent all in siteroot 1?