09:48:03 <batjony> guys does someone know why multiple checkboxes like <flux:field.select name="pageType" renderMode="checkbox" items="{197 : 'news', 198 : 'events'}" /> does not work ?
09:48:33 <batjony> how can I render multiple checkboxes with flux ?
10:10:00 <batjony> i found the issue, you should always set the argument maxItems > 1
10:43:08 <Akii> I just added a CE on a non default language and a new CE magically appeared on the default language and is now no longer removable nor can be seen in the BE
11:13:25 <bjo3rn> mahlzeit. can I override the button label of inline FAL fields 'Add new relation'?
11:15:54 <drlimbo> what are you guys using to create a website search with fluidtypo3?
11:16:11 <drlimbo> i thought about indexed_search or ke_search - but both need an own indexer
11:55:32 <batjony> guys is there a way to access the flux configuration variables from a ContentController ?
11:56:28 <batjony> most likely with a custom Flux Provider
12:03:38 <batjony> i mean that if i have a custom content element "Test" and a flux field "name", how can I access the variable "name" in the ContentController:testAction() ?
13:57:16 <mrboe> hey guys - i have a additional col in the translation view "fluid content area"
16:27:01 <jmverges> hey mates, I need some help with Page Configuration and subpages. In my root page I have configured some behaviour for itselft and other for subpages, but subpages are not getting it... what am I doing wrong?
16:29:42 <batjony> Guys if i have a custom content element "Test" and a flux field "name", how can I access the variable "name" in the ContentController:testAction() ?
16:31:11 <bjo3rn> batjony $this->data is an array of all fields
16:36:09 <batjony> bjo3rn: 10x, I remember that someone said also something about custom providers, but most likely is some other case
16:52:22 <NamelessCoder> use the settings. prefix so it merges with typoscript and can be accessed in the standard $this->settings array - https://fluidtypo3.org/documentation/templating-manual/templating/using-variables/typoscript-variables.html
17:19:56 <jmverges> NamelessCoder, what about subpages configuration?
17:25:37 <NamelessCoder> on sub-pages, $this->settings is filled with whatever values were inserted in the subpages configuration. It's all described in the documentation.
17:33:42 <cbleicker> hey guys, the first snippet is a layout example? if so why there is a layout in a layout
17:40:36 <NamelessCoder> f:layout inside Layouts is not required, but it helps to put it there for clarity
17:44:14 <jmverges> but NamelessCoder, I don't understand something. If I configure in root pid something for the page configuration and other thing for the subpages, when I go to edit a subpages, shouldn't I see in subpage configuration the one setted in root subpage configuration? I'm just using flux, no php
17:46:20 <jmverges> I mean, subpages inherits the configuration of the parent page, no the configuration setted in subpages of parent page configuration... what a mess I think that I'm getting a headheache
17:50:12 <NamelessCoder> jmverges only for fields which support actually displaying a default value as determined by the "default" property in the TCEforms array. Internally, inheritance works by detecting and removing any values which are either empty, have the same value as the parent or have been explicitly told not to inherit values.
17:50:48 <NamelessCoder> we absolutely only deliver TCEforms arrays. We do not override the JS that preselects, nor do we control the HTML that constitutes fields.
17:51:47 <NamelessCoder> basically: it it works in a flexform context using TCEforms logic, it works in Flux (or can be brought to work - there are exceptions in some very rarely used properties that we don't currently transfer, see fx most recent flux pull request). Nothing more, nothing less.
17:52:12 <NamelessCoder> Flux is not a substitute for TCEforms, it's an API for it.
17:58:13 <jmverges> there is some way to hide the page layout selection and set someone by default? or, to not show all page layouts and show only some of thems?
17:58:53 <NamelessCoder> an initial value has to be filled but after that you can exclude the field from access by user group or override the TCA showitems definition for your types
18:01:11 <jmverges> I tried this an is interesting
20:17:47 <cbleicker> NamelessCoder: found it here https://fluidtypo3.org/documentation/templating-manual/templating/creating-templates/content-element.html
20:21:06 <cbleicker> also here: typo3conf/ext/fluidcontent/Resources/Private/Layouts/Content.html
21:24:41 <cbleicker> need to build up a flux form wich allows to select multiple content elements. maybe by suggest. but i have no idea how to do this
21:34:13 <NamelessCoder> you could perhaps use flux:field.relation size>1 maxItems>1 table=tt_content and optionally have a child of that field, flux:wizard.suggest table=tt_content BUT, I would not recommend using "suggest" on tt_content since it searches only in headers and uid
21:37:09 <cbleicker> searching in headers would be totaly okay for me
21:37:35 <cbleicker> but i dont get any search result :(
21:38:48 <NamelessCoder> cbleicker have you tried setting the various properties of the suggest wizard? I believe by default it is optimized to search in pages so it might need a bit of tweaking to find content
21:41:46 <cbleicker> NamelessCoder: but it also does not work for table="pages"
21:42:24 <NamelessCoder> cbleicker try with <flux:wizard.suggest table="tt_content" storagePageUids="{0: 1}" storagePageRecursiveDepth="999" />, optionally override the pid restriction using searchCondition="1=1" (last one is an educated guess because I don't remember it specifically)
21:44:56 <NamelessCoder> - don't even remember how to configure a suggest wizard in tceforms...
21:51:57 <NamelessCoder> okay, check. This was also a content element.
21:53:26 <NamelessCoder> in the XHR request my search dispatches I am seeing these values: value=32&table=tt_content&field=pi_flexform|data|progressBar|lDEF|contentrelationtest|vDEF&uid=4&pid=1&newRecordRow=
21:53:37 <NamelessCoder> (content element name is "contentrelationtest")
21:54:42 <NamelessCoder> is your element already saved when you attempt searching?
21:58:06 <NamelessCoder> "multiple" property denotes whether or not the field accepts duplicate values (as per TCA naming which yes, kinda sucks in this case)
22:03:43 <cbleicker> a "group" type is not availble, right?
22:04:03 <NamelessCoder> it's replaced by .relation and .file to separate those two responsibilities
22:04:59 <cbleicker> i mean thsi type: https://www.dropbox.com/s/9ikjfkhm0kmnr6p/Bildschirmfoto%202014-12-04%20um%2022.03.53.png?dl=0
22:05:28 <cbleicker> damn, i did only flow the last time and forget nearly anything about cms :(
22:05:47 <cbleicker> even dont know tca type names anymore ^^
22:13:13 <NamelessCoder> autocompletion will definitely help out
22:13:40 <NamelessCoder> looks like we're missing a field that renders like the above. flux:field.multiRelation was the intention but I think it never got built...
22:13:53 <NamelessCoder> which is certainly a shame, but fixable in a matter of seconds
22:22:01 <NamelessCoder> there's the XSD in case you're using the autocomplete. Btw, tip is to map the xmlns URL to the typo3conf/ext/flux/Resources/Private/Schema/Flux.xsd file so it updates along with Flux
22:22:03 <cbleicker> so multiRelation is my friend now?
22:22:25 <NamelessCoder> yep, multiRelation is internally a group/internal_type=db
22:28:09 <cbleicker> i mean, storing the whole record
22:28:12 <NamelessCoder> the "name" is what gets used as fluid variable name - only requirement is it has to be a valid lowerCamelCase name with or without dots
22:28:30 <NamelessCoder> was just thinking out loud while debugging ;)
22:28:37 <NamelessCoder> I can reproduce the problem
22:29:47 <NamelessCoder> the hidden input field gets updated correctly... freaky
22:36:41 <cbleicker> think this is ready for master ^^
22:37:27 <NamelessCoder> we're building up to a flux 7.2 release soon but there's a bit of a problem; seems the legacy templateRootPath name was completely dropped in favor of array templateRootPaths so we have to be smart and adapt
22:37:52 <NamelessCoder> I'm investigating now how bad it is
22:41:08 <cbleicker> so there will be no v6.2 release including the new formelement?
22:42:48 <cbleicker> there is a missing use statement in the the viewhelper
22:43:06 <cbleicker> annotaton @return is relative interface
22:44:59 <NamelessCoder> sure sure, there will be a 6.2 compatible release with this component included
22:45:09 <NamelessCoder> we will keep supporting 6.2 until we have a new LTS
22:53:47 <NamelessCoder> and that's how you support CMS 7 ^^
22:58:02 <xaver> yeah i fixed the dam opcacheGUI and i think the developer of that tool need to be reassigned as garbage collector in real-life
22:58:19 <cbleicker> i dont have a chance to port this vh to my own package because of this? $className = $this->createComponentClassName($type, 'FluidTYPO3\Flux\Form\Field');
23:00:00 <xaver> its true, take a look how the config works -_-
23:00:06 <NamelessCoder> cbleicker we check if the generated class exists and if not, we try to use the FQN you specify
23:00:13 <xaver> also the logging stuff is nearly finished
23:00:15 <NamelessCoder> our checks maybe could be smarter there
23:01:58 <cbleicker> wich i specify? this is the SCOPE constant?
23:04:03 <NamelessCoder> cbleicker just the full class name passed as $type should do it - this is the line that resolves the class: $className = TRUE === class_exists($prefix . '\\' . $className) ? $prefix . '\\' . $className : $className; and we supply $prefix.
23:04:27 <cbleicker> year, okay. passed as argument i see
23:04:34 <NamelessCoder> currently the prefix is hard, but FQN class name support should work :)
23:04:57 <NamelessCoder> one of those features one uses once maybe per year
23:05:44 <NamelessCoder> if you want to pimp that approach, there's the option to create forms as pure PHP
23:06:06 <NamelessCoder> that way you can be as creative as you want with precomposed Forms and Form Components
23:07:49 <NamelessCoder> there's a tiny bit of that in this gist: https://fluidtypo3.org/library/code-examples.html?tx_fluidshare_display%5Bgist%5D=1&tx_fluidshare_display%5Baction%5D=display&tx_fluidshare_display%5Bcontroller%5D=Gist&cHash=0aad324cc78ca0e8a913a6fefe195e4c
23:10:58 <NamelessCoder> out of curiosity cbleicker can you reveal what you are working on?
23:13:53 <cbleicker> no i cant because of stupid aggrement with the client
23:15:44 <NamelessCoder> sadly, that analogy is not entirely wrong :)
23:16:25 <cbleicker> so, if i would do all of this in ts i could build the menu by the pid list i have now. it there a vh wich simply fetches a content record by a given uid?
23:31:23 <NamelessCoder> if you only ever require the content UIDs as an array, set transform="array" on the flux:field
23:31:36 <NamelessCoder> that'll explode it good before assigning it to template
23:41:40 <NamelessCoder> for anyone reading: drag-n-drop is broken in CMS 7 if you use the master branch of the typo3 core. But it's not our fault: seems a JS library is a bit broken.