07:12:32 <rawai> Installiert man css_styled_content + fluidpages_bootstrap alles ist OK
07:13:56 <rawai> jedoch der Fehler liegt wohl in den TS settings der fluidpages_bootstrap denn wenn diese eingebunden werden erscheint der Fehler
07:16:22 <rawai> fluidpages_bootstrap +fluidcontent_bootstrap without the TS settings are working but as soon as you include those TS settings the complete site is TYPO3 6.2 Fluid Flux based site is failing
07:19:33 <rawai> nevertheles in the bakcend you still get typo3_src-6.2.0/typo3/sysext/lang/Classes/LanguageService.php line 250
07:20:27 <rawai> getting this error by going WEB - Page - choose Rootpage - ERROR
08:05:46 <rawai> Updated 5 days agoof both fluidpages and fluidcontent bootstrap
08:50:49 <misiak> Hi, i was going thru flux 7 migration manual (i used the php migration script), but i have still white page on FE when i insert any FCE on page. Any idea what else can be wrong?
09:21:10 <misiak> and another interesting thing: i can see the same FE via View Modul in BE correctly
09:26:17 <misiak> i am working with updated ft3_empty 0.0.1 which was working well in previous flux and typo3 version
09:26:55 <misiak> is there any another example for flux7 and typo3 6.2 for testing?
09:35:35 <misiak> randomresult i turned on the development settings in install and i get: Fatal error: Call to a member function calcPerms() on a non-object in /typo3conf/ext/flux/Classes/ViewHelpers/Be/ContentAreaViewHelper.php on line 72
09:36:45 <randomresult> so maybe u use an outdated viewhelper
09:39:47 <misiak> randomresult but BE flux debug is OK...all green
09:42:18 <randomresult> try to move all templates out... then add one after another and see when this happens. that is what i would do AFTER i asked someone who has a @ infront of his name. :)
10:58:01 <xaver> any problems with fluidcontent and solr search index ...
11:05:22 <BenjaminR> really dont think so because NamelessCoder is working strongly with solr
11:07:09 <mrboe_> anybody have had the problem that you could not create a new "text" element inside a FCE but able to drop a text in (6.2; all latest dev)
11:07:37 <mrboe_> the "plus" symbol is not clickable
11:14:10 <misiak> mrboe_ i have problem with FCE in typo3 6.2 with FE rendering but i also have that plus symbol problem as u wrote, but its so not important than FE rendering..is FCE FE working OK for u? I have flux7.
11:42:36 <alex_schnitzler> There has been the possibility to link headlines. How do I handle this with fluidcontent?
11:43:34 <BenjaminR> Hi alex! I started with fcc yesterday so i am not very experienced with it yet but i would guess you will have to overwrite that Properties/Header template?
11:46:17 <NamelessCoder> yep, that's the way (remember to also override the header output partial)
11:46:39 <alex_schnitzler> Well, first of all there is no link field any more
11:46:43 <alex_schnitzler> How do I get that back?
11:46:57 <adi77> I upgraded to flux7 and now all fce's show a additional rte field after the flux elements. Although i did not define it in the fce template. What could be wrong? I upgraded to flux7 and now all fce's show a additional rte field after the flux elements. Although i did not define it in the fce template. What could be wrong?
11:47:21 <NamelessCoder> in Properties/Header.html partial you can add an flux:field.input with flux:wizard.link which is how the core's field would appear
11:47:56 <xaver> anybody gets this error in backend - edit page http://nopaste.chaoz-irc.net/view/a8f153bf - only on all pages
11:48:20 <NamelessCoder> in Content/Header.html Partial you then check if a link exists and if it does, wrap your H*, container or text in header with v:link.typoLink (iirc name)
11:49:51 <alex_schnitzler> NamelessCoder: Do I have to adjust plugin.tx_fluidcontentcore.view.overlays.templates.templateRootPath first?
11:50:14 <NamelessCoder> yes, ideally - you can also override the old school template path
11:51:25 <alex_schnitzler> Don't get that. Do I have to adjust the templates path only or do I have to adjust template/layout/partials paths?
11:53:28 <BenjaminR> where is the typo my friends: {v:content.resources.fal(field: 'settings.image') -> v:iterator:first() -> v:var.set(name: 'settings.image') -> v:if.type.isInteger(value: settings.image)}
11:55:03 <NamelessCoder> alex_schnitzler to be perfectly clear: your current use case suggests you need to override OR overlay the partialRootPath. Whether you choose to overlay or override is of less significance, as long as you are a ware of how the two stategies work. You must overlay or override two templates: Properties/Header.html and Content/Header.html partials.
11:55:14 <BenjaminR> settings.image is a variable so without ''
11:56:22 <alex_schnitzler> NamelessCoder: Do you have information about the difference between overlay and override?
11:57:00 <BenjaminR> NamelessCoder alex_schnitzler: EXT:view has some good documentation about that feature not?
11:57:03 <alex_schnitzler> Currently I overlay the template path only
11:57:05 <BenjaminR> and overwrite is what we know from history
11:57:13 <NamelessCoder> alex_schnitzler overriding requires you to contain *all* the partials of the original extension in the path which you override. Overlays allows you to place only the files that should be different, in the path you register as overlay.
11:57:35 <alex_schnitzler> I see. I want to overlay!
11:57:43 <NamelessCoder> sounds like you do want to overlay ;)
11:57:53 <NamelessCoder> but you'll need to overlay the partialRootPath, not the templateRootPath
11:58:52 <alex_schnitzler> Thanks, now I get it and it works.
12:04:23 <alexander_dick> hi guys. i have a quick configuration (TS) question...
12:04:55 <alexander_dick> context: provider extension with page templates, content elements etc.
12:05:04 <alexander_dick> settings defined via plugin.tx_foo.settings
12:05:45 <alexander_dick> settings are accessible in frontend but not in the flexform config of my content elements (<f:section name="Configuration"> )
12:06:04 <BenjaminR> NamelessCoder: id like to hear your opinion about that v:if.type.isInteger - idea about that is to make it able to render that fce from extensions and pass settings.image. settings.image is integer only if its not rendered from outside
12:06:16 <alexander_dick> the {settings} object is NULL
12:07:18 <BenjaminR> alexander_dick use v:var.typoscript(path: 'plugin.tx_yourext.settings') -> v:var.set(name: 'settings')
12:07:27 <BenjaminR> plugin settings are not available in be
12:40:38 <xaver> hp typo3/cli_dispatch.phpsh extbase builder:fluidsyntax :( Version number in composer manifest of package "fluidpages_bootstrap" is missing or invalid
12:41:17 <BenjaminR> cant help you with that - its refactored actually
12:57:41 <xaver> BenjaminR: this is the problem <flux:field.input name="theme.googleDataLayer" label="Google Data Layer (optional)" transform="array" inherit="0" size="50" placeholder="key:val, key2:val2"/>
12:59:05 <soee> when inside grid using 2 columns and they have colspan=3 and colspan=9 why do they render 50/50 width ?
12:59:15 <xaver> transform="array" without a entry in DB XML Flexform causes a error
13:19:25 <xaver> if a empty Flexform entry is DB it works
13:20:03 <NamelessCoder> it should contain a JS-as-string function call which fx respects "requestUpdate" and eval. There is no apparent cause for this error.
13:24:58 <NamelessCoder> I want to say it's a core bug in creating the $iOnChange variable - possibly, arguments were added to a method and one or more calls were not adjusted, somehow making $iOnChange contain what should be $defaultValue (which is inherited from parent page if empty, which would make the inherited variable an array instead of a string which is the normal behavior for an "input" type field.
13:25:36 <NamelessCoder> but the catch is, you should avoid transform="array" on inputs for this very reason. Rather, v:iterator.explode the value in your view
13:25:56 <NamelessCoder> transform="array" makes great sense on fx "group" type fields.
13:50:03 <xaver> i use exploade later to splite the key=>value
14:07:38 <FT3BOT> Issue 143: [BUGFIX] Remove bodytext RTE field from fluidcontent elements before TYPO3 6.2 https://github.com/fluidtypo3/fluidcontent/issues/143
15:23:08 <mrboe_> Windows Episode 8 "Retrun of the Start Button"
15:25:18 <BenjaminR> btw re-using a fce template in a third party extension first time: <v:render.template file="EXT:vmtemplates/Resources/Private/Templates/Content/HeaderImage.html" variables="{settings: {image: {url: 'fileadmin/headerImage-small.png', alternative: 'MEC G', width: 1280, height: 216}}}" paths="{v:var.typoscript(path: 'plugin.tx_vmtemplates.view')}" />
15:39:30 <Stephan> Grettings! Is there a place where i can find the *xsd files for fluid flux vhs? The links on the dokupage are broken/ the files doesn´t exist.
15:40:17 <BenjaminR> Hi Stephan. cedricziel might be able to help you
15:43:05 <Stephan> Ok, i will contact him in a single chat. Thanks
15:43:32 <alexander_dick> http://forge.typo3.org/issues/57472 isn't getting any love either
16:13:38 <NamelessCoder> Stephan http://fluidtypo3.org/schemas/
16:36:31 <Stephan> You are my hero of the day NamelessCoder ;)
16:39:22 <mrboe_> @NamelessCoder if i use <f:render section="BE{split -> v:format.case(case: 'split')}" - i must have a empty section called BE
16:41:22 <mrboe_> is that normal - if i dont have that the my
16:41:41 <mrboe_> sorry if i dont have that section my backend is broken
17:28:12 <rahulthewall> Where do I find the list of extensions that I need to install on the new website
17:28:16 <rahulthewall> the old website had a handy list
17:29:02 <ad_on_is> hi, i have a funny question about flexform
17:29:13 <Outdoorsman> flux vhs fluidcontent fluidpages are the main ones I believe
17:29:26 <ad_on_is> is it possible to somehow style the output, using something like $TBE_STYLES['colorschemes'][0]='red,yellow,blue,olive,green';
17:30:01 <ad_on_is> i.e when using registerFluidFlexFormPlugin()
18:03:51 <BenjaminR> What is wrong with this condition <f:if condition="{v:var.typoscript(path: 'plugin.tx_vmtemplates.settings.contentArea.inheritance.footer')} == '-1'">
18:04:10 <BenjaminR> debugged output for v:var.typoscript in configuration section and it is '-1'
21:35:30 <Guest|29327> I have an issue with fluidcontent. I always get the error 'The default controller for extension "Fluidcontent" and plugin "Content" can not be determined. Please check for TYPO3\CMS\Extbase\Utility\ExtensionUtility::configurePlugin() in your ext_localconf.php'
21:36:10 <randomresult> Guest|29327 version of all. t3 flux fluidcontent fluidpages vhs
21:36:59 <Guest|29327> (it's in an ajax request, implemented with the eid dispatcher)
21:37:00 <randomresult> Guest|29327 u use TER or GIT versions. if Git which branch?
22:16:20 <Guest|59069> vhs 1.8.4 and got a problem with loading the FCE in an ajax request using eID
22:17:12 <Guest|59069> If i try to load the content object with the RECORDS function I get the following error: The default controller for extension "Fluidcontent" and plugin "Content" can not be determined. Please check for TYPO3\CMS\Extbase\Utility\ExtensionUtility::configurePlugin() in your ext_localconf.php
22:17:35 <Guest|59069> Can somebody help me to fix it?
22:43:03 <danilobuerger> Guest|59069 you might want to update your extensions