IRC logs

20160407

• 04:58:43 <mddz> hi there
• 04:59:22 <mddz> what to do if language labels of Page Layouts are not resolved in the backend page settings?
• 05:07:32 <cweiske> are you using the extensions from TER?
• 05:07:35 <cweiske> or from git?
• 05:09:39 <mddz> git
• 05:09:50 <cweiske> there is an open bug for this issue
• 05:09:54 <cweiske> the TER version works
• 05:10:39 <cweiske> https://github.com/FluidTYPO3/fluidpages/issues/313
• 05:10:48 <mddz> ah I see
• 05:10:53 <cweiske> oh, it's closed
• 05:11:15 <cweiske> so it should be solved if you're running latest git
• 05:11:19 <mddz> so is it fixed?
• 05:11:38 <cweiske> so it should be solved if you're running latest git
• 05:11:48 <mddz> I did not pull the newest version from git for some weeks
• 05:11:57 <mddz> will try that out
• 05:12:24 <mddz> btw, what is the recommended way of updating the extension?
• 05:12:29 <cweiske> via TER
• 05:12:42 <mddz> should I deactivate the extensions before I pull from git and then reactivate after?
• 05:12:43 <cweiske> git master can always have problems and bugs
• 05:12:57 <cweiske> that depends
• 05:13:11 <cweiske> after updating, you should always clear class cache and compare database
• 05:14:30 <mddz> compare the database manually? Or is there a TYPO3 function for that?
• 05:14:38 <cweiske> install tool -> compare database
• 05:18:55 <mddz> ok, thank you :)
• 07:04:09 <moger> I have a multidomain TYPO3 instance with 4 trees (root levels) and 4 provider extensions. I'm trying to limit the availability of the page template sets to the respective trees.
• 07:04:38 <cweiske> understandable
• 07:04:43 <cweiske> but I have no idea how to do this
• 07:05:08 <moger> by debugging through the code, i found out that plugin.tx_myprovider.view.enable = 0 works to archive that.
• 07:05:42 <cweiske> cool
• 07:06:06 <moger> so far so good - it works on all subpages of each tree.
• 07:06:24 <moger> But not on the root pages. there, the "first" provider always "wins".
• 07:06:45 <cweiske> what do you mean by "wins"?
• 07:07:06 <moger> in the available layouts, i always have only the first provider.
• 07:07:35 <cweiske> this is strange; it works fine with multiple providers here
• 07:08:08 <moger> that's because of \FluidTYPO3\Flux\Service\FluxService::getViewConfigurationForExtensionName delivers wrong settings.
• 07:08:15 <cweiske> http://fotos.cweiske.de/screenshots/2016-04-07%20typo3%20page%20layout%20selection.png
• 07:09:58 <moger> yes, if i keep all providers enabled, of course i have all of them available everywhere.
• 07:10:49 <moger> but once i disable some, but only in subtrees, the configuration which is read by flux differs from the typoscript configuration which can be seen in the backend (template analyzer / object manager)
• 07:10:53 <moger> very strange.
• 07:25:27 <moger> I debugged some more. the wrong pageId is determined by \TYPO3\CMS\Extbase\Configuration\BackendConfigurationManager::getTypoScriptSetup
• 07:25:48 <moger> now I need to find out why.
• 08:29:47 <mddz> Ho do I add css classes to the wrapping div of ContentCore elements?
• 08:52:39 <mddz> ok, I think the easiest way is to just override the ContentCore Layout
• 12:10:43 <drlimbo> hi there
• 12:11:41 <drlimbo> does someone has an idea why image-croping works well in the install tool, but on my website f:image and v:uri.image doesn't resize my pictures?
• 15:29:00 <Obiwan> Hi, somehow i can't render the output of an ext base-plugin (t3sheaderslider) with typoscriptObjectPath=... within fluid pages. But I see the output if i append it in e.g. page.10. Any suggestions?
• 15:30:07 <Obiwan> *grabs a beer*