11:54:30 <friggingee> I just stumbled upon a strange behaviour of FCEs when saving image relations in 6.2.3
11:54:50 <friggingee> I got a simple image gallery FCE which uses FAL relations to add images
11:55:48 <friggingee> see https://gist.github.com/friggingee/dbe112e955f1192f519c
11:56:39 <friggingee> if I add an image in the backend, the backend-preview shows the image count as “NEW1234567890abc, NEWabc1234567890”
11:56:54 <friggingee> the pi_flexform value also reflects this data
11:57:59 <friggingee> although the frontend output is correct, this makes it impossible to use any conditions on the image field, also the BE preview output is broken by this
11:58:19 <friggingee> am I doing something wrong there or is this intended behaviour?
11:58:47 <friggingee> I’m using EXT:fluidcontent 4.0.0
11:59:26 <friggingee> EXT:flux 7.0.0 is also installed, runnning on TYPO3 6.2.3
12:00:24 <friggingee> for the pi_flexform, see: https://gist.github.com/friggingee/91b4e169b774c73c7f5e
12:01:10 <soee> what condition do you want to use ?
12:02:52 <friggingee> e.g. <f:if condition=“{f:count(subject:’{settings.image}’)} > 1”>
12:03:31 <friggingee> since the value saved is cleary not an integer and would be transformed to whatever the integer value of the random NEW-string is, this fails to work
12:04:10 <friggingee> however, if I re-save the CE after initial creation, the value gets updated correctly
12:22:56 <friggingee> @soee have you ever experienced this behaviour before?
12:23:06 <friggingee> google doesn’t seem to know anything about it
12:33:35 <friggingee> debugging shows this to be intended behaviour
12:34:07 <friggingee> at least I can’t seem to find any hint on any kind of preprocessing of the newly created FAL relations on save
12:34:50 <friggingee> this behaviour happens on creating a completely new CE and when editing and adding a new image to an existing one
12:47:14 <friggingee> although adding an image to a CE which already has at least one image attached to it, the data is being processed correctly
15:05:11 <Torstenn> Hi there, anyone has an info what the flux copy feature should cover? e.g. copying an ContentElement from outside a column element into a column element doesnt work
15:15:24 <Torstenn> i there, anyone has an info what the flux copy feature should cover? e.g. copying an ContentElement from outside a column element into a column element doesnt work
15:58:42 <Outdoorsman> Hi Torstenn. Just so someone replies to you, I will at least say that I don't know the answer to your question... sorry
16:03:34 <Outdoorsman> Hello randomresults and mrboel. What's the latest on fluidbootstraptheme? Are more people starting to help out on the project with you?
16:58:51 <friggingee> if anyone has any kind of information on my question of today, 12 pm, I’d also be glad to get some feedback… it really seems to be a bug in flux
17:06:03 <jftr> Hi, I have an issue regarding vhs. I use TYPO3 6.2.4 and vhs 1.9.1 (from TER). Whenever I try to use a view helper, I get the following error message: Could not analyse class:FluidTYPO3\Vhs\ViewHelpers\Media\ImageViewHelper maybe not loaded or no autoloader?
17:06:12 <jftr> Does anyone have a clue what's wrong?
17:12:55 <jftr> Obviously the namespace is correctly resolved. However the class seems not to be loaded. Does anyone know why that could be?
17:28:45 <xaver> jftr: do you use namespaces or tx_... stuff
17:30:25 <jftr> Neither. Currently my extension consists only of one content element.
17:31:28 <jftr> In ext_tables.php I call `\FluidTYPO3\Flux\Core::registerProviderExtensionKey`
17:38:34 <jftr> Is there a way to define either of Namespaces or the tx_... notation even if I don't have any PHP code yet?
17:51:39 <jftr> I get the very same error if I try to validate builder itself in builder.
17:52:05 <jftr> "Could not analyse class:FluidTYPO3\Vhs\ViewHelpers\Form\SelectViewHelper maybe not loaded or no autoloader?"
17:52:17 <jftr> Does anyone have a clue what the issue could be?
17:56:25 <jftr> Oh, xaver, you were talking about xml/fluid namespaces. That actually solves the problem: Instead of declaring namespace v in the opening div tag, I add a namespace declaration in curly braces: {namespace v=Tx_Vhs_ViewHelpers}