15:29:00 <pRiMUS> can any1 tell me, why my fluid content elements appear in the tab "plugins" and the view of the tab seems broken. in another typo3 instance its working fine in an own tab.
15:48:44 <batjony> if i have a flux form and inside it flux fields with attribute required="1", i could still save the fce without filling anything in these fields
15:49:14 <batjony> how can I set some kind of "not-empty" validation in a flux forms ?
15:54:46 <artisticMink> It might sound silly, but did you try 'true' as string value?
16:01:12 <artisticMink> batjony: I just checked AbstractFieldViewHelper, required is registered as a boolean, so 1 or true should work. Try clearing the cache after making changes or use uncache. If the problem persists, you probably have to debug it.
16:02:01 <pRiMUS> as soon as i add the configuration it break my backen
16:02:18 <batjony> actually not sure what should happens if something is set to required
16:02:27 <batjony> should some errror message appear ?
16:03:06 <artisticMink> batjony: At least, there should be a field prefix * by default.
16:03:21 <artisticMink> It would be a good thing to upload your flexform to pastebin and poste the link here.
16:05:04 <artisticMink> On another note, i've got a problem of myself: I need to pass some arguments down to an content element. Currently i'm using <v:content.render /> Do i have another option similair to <f:render arguments="{_all}" /> or do i need to create a view helper myself to handle this?
16:11:02 <NamelessCoder> artisticMink what is the purpose of the variables?
16:12:52 <pRiMUS> interessting. with the flux 7.1.0 everything works fine
16:13:03 <artisticMink> artisticMink: it's a flag. If set, i'll have to assemble some opengraph data inside the content element context. Currently digging trough your documentation, i should be able to register it as a variable.
16:15:50 <NamelessCoder> you could use v:variable.register.set / .get
16:16:40 <NamelessCoder> or if your child elements are always direct descendants of your parent, the child element can load the parent's details by {record.pid} + v:content.get / flux:form.values
16:18:20 <artisticMink> NamelessCoder: Yes, thanks. That should come in handy.
16:19:18 <jmverges> Claus, where is stored flux data?
16:20:36 <NamelessCoder> jmverges depends on the context, but always in a "flex" type field on the table you're editing
16:22:15 <batjony> another question guys, lets say i have a flux form where the first field is a select box and when the user choose something from this selectbox - some other logic in the flux form based on the selected value should appear
16:22:21 <batjony> for just an example I use this http://pastebin.com/JACeRbgE
16:22:49 <batjony> where the text field is populated with the selected value
16:23:07 <NamelessCoder> jmverges fluidcontent_core stores its settings in tt_content.content_options. Fluidcontent stores them in tt_content.pi_flexform. Fluidpages stores them in pages.tx_fed_page_flexform and custom plugin implementations usually store them in tt_content.pi_flexform.
16:23:14 <batjony> is it possibile to implement such "dynamic" flux logic ?
16:23:17 <NamelessCoder> this is flexform data still
16:52:41 <cbleicker> doing my first steps with flux
16:53:08 <cbleicker> what should i do with this one? AdditionalConfiguration.1414852807.php
16:53:40 <NamelessCoder> cbleicker nothing, ideally. It's a migration file used by the EM script of fluidcontent_core
16:54:53 <NamelessCoder> purpose is to allow fluidcontent_core to detect back in history all the versions of AdditionalConfiguration.php which it has written so that it can overwrite any version it wrote but leave any modified files intact (leaving it up to the admin to include any changes in that file)
16:55:32 <cbleicker> so on a totaly fresh installation nothing to do?
16:56:15 <NamelessCoder> except running the EM update script for fluidcontent_core or manually copying the current version of AdditionalConfiguration.php to typo3conf/ ? No, nothing required.
16:56:45 <NamelessCoder> all the EM script does is copy the file if it detects the file can safely be replaced or does not already exist
17:30:58 <qnic> NamelessCoder, hi, do you have a few minutes? I'd like to discuss your proposal for implementing page.resources.fal record sliding in vhs from issue #679.
18:48:54 <cbleicker> need initial help to understand page templating with fluidpages
18:49:22 <cbleicker> page record shows: Data Structure ERROR: No proper configuration!
18:49:44 <cbleicker> is this a fluidpage setting or is this some core stuff?
18:49:57 <cbleicker> i am totaly out of t3 ^^ did to much neos ^^
18:51:27 <cbleicker> frontend ends up in exception that typo3conf/ext/fluidpages/Resources/Private/Templates/Page/Default.html is not found. how to tell fluidpages that the templates are located in my personal site package?
18:54:03 <cbleicker> or do i still need backend layouts?
18:57:42 <qnic> cbleicker, you need to set the backend layout to fluidpages on your root page
18:59:06 <cbleicker> how to set it to fluidpages? where is the relation done?
19:00:25 <cbleicker> i am confused. is this still valid? http://docs.typo3.org/typo3cms/extensions/fluidpages/ because i see classnames without namespacing everywhere
19:03:57 <cbleicker> so for what is fluidpages in this case? just to deliver the abstracts?
19:04:09 <qnic> recent fluidpages versions also require you to set the 'backend-layout' field on the appearances tab of your root page properties to 'Fluidpages'
19:04:25 <qnic> it provides all required infrastructure
19:04:44 <qnic> you only have to provide the concrete site-specific templates in your own extension
19:07:31 <cbleicker> so simply disable the default fluidpage ts config in extmgn setup and copy this stuff to my own extension ts wich assigns then my own provider?
19:08:57 <qnic> you shouldn't need any ts for using fluidpages
19:09:37 <qnic> FluidTYPO3\Flux\Core::registerProviderExtensionKey($_EXTKEY, 'Page'); should take care of everything you need for basic pages
19:11:02 <NamelessCoder> qnic sorry, don't expect I'll have time today
19:11:34 <qnic> NamelessCoder, I'll bug you some other time then
19:12:01 <NamelessCoder> cbleicker if you still use 6.2 you might want to try installing the EXT:site distribution - it creates a basic setup that renders out of the box. We're still not quite ready for 7.x though
19:13:02 <cbleicker> using 6.2 but i want to understand and study it instead of autobuilding stuff ;)
19:13:26 <cbleicker> i will just give builder a try and will take a look what it generates for —pages
19:13:30 <qnic> cbleicker, then you should probably read the complete guide on fluidtypo3.org
19:14:21 <NamelessCoder> oh that's not autobuilding in the common sense of the word ;) it uses EXT:builder to generate the extension - we recommend you do that anyway. All EXT:site really does is load dependencies and insert a working setup (all the stuff you normally do in fresh sites - top page, three sub pages, a TS template, select which FE template to use, etc)
19:14:35 <NamelessCoder> but understanding is always a good thing, no doubt
19:18:08 <cbleicker> uuuuh. now i have the mistake i make :) this one tells the flux core to look for templates in my extension, right?
19:18:50 <NamelessCoder> yep, that tells any feature using Flux to enable the "Page" controller type that your extension has templates for it
19:19:37 <cbleicker> what i thought what it does ist: "register a new provider found in package 'foo' and is called class PageProvider{}"
19:19:52 <cbleicker> something similar like a plugin controller registration
19:20:38 <NamelessCoder> it's similar to registering a plugin - I see the confusion in the method name; the intention was to make it read "register provider-extension key"