05:14:29 <syssi> @NamelessCoder_ Hi Claus! There seems to be a regression at variable.set (vhs 2.3.3/master).
05:15:13 <syssi> This way of building an array works fine: <v:variable.set name="test" value="{0: 'bar'}" />
05:15:39 <syssi> In the past this was possible also: <v:variable.set name="test" value="{foo: 'bar'}" />
05:16:45 <syssi> Today (vhs 2.3.3) the last statement validates to a string (value: "{foo: 'bar'}").
05:18:18 <syssi> So I'm unable to create associative arrays atm.
05:28:25 <NamelessCoder_> 95% sure that's because you have a syntax issue in the array
06:03:26 <syssi> I have tried: <v:variable.set name="test" value="{foo: 'bar'}" /> and <v:variable.set name="test" value="{'foo': 'bar'}" /> without success.
06:33:26 <NamelessCoder_> parameter type is "mixed" which means it is up to Fluid to detect what is being passed: https://github.com/FluidTYPO3/vhs/blob/development/Classes/ViewHelpers/Variable/SetViewHelper.php#L66
06:34:02 <NamelessCoder_> if this is broken, any ViewHelper that accepts "mixed" will be unable to receive an associative array - in other words, it'll be something changed in Fluid itself
06:35:07 <Guest|4135> Hi! I'm trying to create a own variant of image with fluidcontent_core. Is there anywhere an example available how to do that?
06:37:10 <NamelessCoder_> hi Guest|4135 :) the README.md of fluidcontent_core shows how to add new variants - and to get started, just copy the template from fluidcontent_core into your own extension and edit it from there.
06:37:48 <NamelessCoder_> if all template paths and registrations are correct, fluidcontent_core will detect your template and add an option in the "Variant" selector
06:54:19 <syssi> @NamelessCoder_: I understand. The problem must be located at fluid (!= vhs).
06:58:19 <NamelessCoder_> hmmm... no new features there so if anything, this would have to have come as a side effect of some bug fix in fluid
07:00:10 <syssi> I will try to reproduce the issue on a clean install at first.
07:09:13 <Guest|4135> NamelessCoder_: Sorry, I got a telephone call... I managed it, to create a variant of Text. That works fine. But I am in trouble with Image. I am not able to figure out, how to output the images in my template variant
07:09:53 <NamelessCoder_> check the template that ships with fluidcontent_core - and use the default fields for images in the content element
07:14:51 <Guest|4135> I looked at Templates/CoreContent/Image.html. Do I have to copy the whole file to my extension and modify the sections Preview and Main?
07:15:14 <NamelessCoder_> that's the easy way to go yes :)
07:24:15 <Guest|4135> after copying the file and the dependent (Properties/{Header,Container,Images) und Content/Image I get the error: Oops, an error occurred! Code: 20150625132056382d8077
07:33:02 <NamelessCoder_> can't tell the problem from that - you need to disable the ProductionExceptionHandler. TYPO3 is in production mode regarding errors and won't throw exceptions, instead it gives you the time plus some random chars as "error message"
07:33:33 <NamelessCoder_> but you don't need to copy partials etc. if you add fluidcontent_core's partialRootPaths and such to you own extension's view paths
07:41:00 <Guest|4135> I thought, that the ExceptionHandler ist diabled. [SYS][productionExceptionHandler] is empty.
07:43:12 <NamelessCoder_> setting the context setting to Development should set all parameters correctly
07:59:37 <Guest|4135> Thank you very much! Just setting Development in the Backend did'nt show up the whole error message. But setting it in webserver config helped. Now I could find the error... Typo in Layout Path. Now it works fine :-)
11:33:32 <syssi> is there a way to render also the parent page by v:page.menu?
11:35:59 <syssi> Set the pageUid and manipulating entryLevel & levels does not help.
12:03:19 <Daniel^^^> Hi! Can I add own FCEs? I need something like a 2 and 3 column grid layout with a variable number of rows. It will be nice if I can do colspans, too