09:47:02 <randomresult> @NamelessCoder after installing EXT:site i have a .git folder in all the extensions
10:02:27 <Akii> is there an estimate when the next flux version is released? (minor patchlevel)
10:08:24 <denis-fluid> bjo3rn: I've tried that now. For testing reasons I just setup a simple variable in my setup.txt - https://gist.github.com/DenisMir/d59d3c126caec1deef71 - I'm trying to render that one as items in the select field like so: <flux:field.select name="settings.switch" label="LLL:breakpoints.switchCols"
10:32:04 <denis-fluid> bjo3rn: I got the following setup now. Setup: https://gist.github.com/DenisMir/d59d3c126caec1deef71 Constants: https://gist.github.com/DenisMir/6ea74bfbf4947f5fdaca - I can see the correct settings in the constants editor of T3. When I'm trying to output one of the breakpoints in a p tag just for testing I'm getting an emtpy string. (<p>{settings.grid.breakpoints.b0}</p>) - I'm not quite sure if this should be possible :-)
10:41:34 <bjo3rn> denis-fluid I don't think so. you should be able to use the constant to populate argument items of your select field now though
10:42:00 <denis-fluid> I'm checking no the fluidbootstraptheme example.
10:42:16 <denis-fluid> It got some examples as well. I'm getting back in a minute.
10:45:25 <Kaimane> Hi at all. Yesterday I asked why the data-object is no present in my partial. I provide everything to the partial with arguments="{_all}" but if i debug {data} fluid returns "null". What to do to get data in my partial?
10:46:50 <bjo3rn> Kaimane is it part of a content or page template?
11:00:03 <Kaimane> bjo3rn: {_all -> f:debug()} is great! {page} provides the uid of the page ;) thank you very much for that hint!
11:01:57 <denis-fluid> What do I have to do that "ext_tables.php" gets executed again? (I added the seperate ts path like the one in fluidbootstraptheme)
11:06:38 <denis-fluid> Forget the question I got it :D
11:18:22 <denis-fluid> Hmpf I'm getting the following error now. What could that be: No value found for key "FluidTYPO3\Vhs\ViewHelpers\SwitchViewHelper->switchCaseValue", thus the key cannot be removed.
11:27:20 <jmverges> hey mates, does anybody know some extension for provide comments to NEWS extension?
11:44:59 <bjo3rn> denis-fluid this error happens when the switch value is NULL
11:46:19 <denis-fluid> bjo3rn: Yeah I added the settings in the ts config and the switch started to fail. I found the error. I named some fields "settings.xyz" and used the value in the switch. This started failing when I added the settings to the TS setup.
11:46:50 <denis-fluid> I assume that "settings." is not a good start for field names.
11:48:31 <denis-fluid> But in the end I still got the same problem with the rendering of TS values. :-) - I got the following simple constants.txt: https://gist.github.com/DenisMir/62959b62795371d49624
11:48:58 <denis-fluid> I can output the content simply with "{settings.grid}"
11:49:43 <denis-fluid> But as soon as I change the content of "grid" to something like: grid { 10 = test } and try to access it with {settings.grid.10} it fails.
11:57:57 <denis-fluid> bjo3rn: Ok when setting the grid to "grid = 10,20,30" I am able to render the 10,20,30 in the select field. But I'd like to have a key/value pair which does not seem possible I assume.
12:00:59 <bjo3rn> denis-fluid sure: settings.grid { 10 = foo 20 = bar 30 = baz } (formatted as single lines ofc)
13:19:12 <denis-fluid> bjo3rn: That is what I have tried. This makes it available in the object editor. But it doesn't work with the select field. :( The select field is populated with one option "{$plugin.tx_xyz.settings.grid}"
13:19:51 <bjo3rn> ok, then CSV maybe. sec, I need to try something.
13:19:59 <denis-fluid> Wenn I change grid to "grid = foo,bar,baz" I'm getting the select field populated with the correct items "foo,bar and baz"
13:20:52 <denis-fluid> It is weird that I even can't access the values like {settings.grid.10} in the normal rendering section.
13:26:00 <Guest|99209> Hi there and thx for the great documentation. I just want to mention that link https://fluidtypo3.org/community/support-chat.html leads to the fals page, maybe you want to fix this...
13:36:56 <denis-fluid> bjo3rn: could you paste me the whole template class. I'm totally confused why this doesn't work. (since everything else worked, I'm just wondering if the system is gettings confused with fields named "settings.<field name>")
14:00:07 <denis-fluid> bjo3rn: I'm getting crazy. :-) I will clean up everything from the "settings.<field>" name stuff and try it again.
14:01:26 <denis-fluid> bjo3rn: I will need some minutes and will get back to you. I hope the result is positive. :-) With the stuff you pastebined you get a select field with e.g. key: 10 value: foo. Correct?
14:51:20 <danilobuerger> well at least i think it was 5.3.9 when redeclaring interface was introduced
14:52:02 <denis-fluid> bjo3rn: Ok here we go. I got the following setup. Simple example template: https://gist.github.com/DenisMir/85f251c13d68c84b3543 - Simple setup.txt https://gist.github.com/DenisMir/4477f935e730fce8e770 and simple constants.txt - https://gist.github.com/DenisMir/42a3d287e272b1902313
14:52:48 <denis-fluid> When looking at the "Example" content element I'm still getting an empty select field. :( :(
14:53:33 <danilobuerger> denis-fluid what does <f:debug>{settings.foo}</f:debug> output
15:18:31 <bjo3rn> danilobuerger and how would you edit that in the be?
15:18:37 <danilobuerger> denis-fluid please see fcc as it does the same thing https://github.com/FluidTYPO3/fluidcontent_core/blob/development/Resources/Private/Partials/Properties/Header.html https://github.com/FluidTYPO3/fluidcontent_core/blob/development/Configuration/TypoScript/setup.txt https://github.com/FluidTYPO3/fluidcontent_core/blob/development/Configuration/TypoScript/constants.txt
15:21:03 <danilobuerger> i thought you did as you commited to that file ;-)
15:21:26 <bjo3rn> don't remember what I commited :S
15:21:35 <denis-fluid> danilobuerger: I will try that out.
15:23:45 <denis-fluid> danilobuerger: But it is not exactly what I want. I want to have multiple items by default. When I understand the header example correctly it sets type to "1" and you can select in the options from "1,2,3,4,5 or 6"
15:24:10 <denis-fluid> But I want options "1,2,3,4" and want to be able to change these selection of options.
15:24:24 <danilobuerger> try to get the select box working first through setup
15:31:59 <NIMIUS|johannes> sorry, templates. I want to have one basic element and extend it by one attribute for another element
15:33:14 <denis-fluid> bjo3rn, danilobuerger: Ok I got something weird. Here is the template: https://gist.github.com/DenisMir/6b972e594ff93dcd7301- breakpoint is empty and breakpointTwo is correctly populated.
15:33:21 <danilobuerger> NIMIUS|johannes use partials like fcc does
15:41:10 <NIMIUS|johannes> everything, that is not lowercase is dangerous in extkeys
15:46:38 <denis-fluid> Ok I got one question. Does the folder name of the folder that contains the extension matter or is it only the "\FluidTYPO3\Flux\Core::registerProviderExtensionKey('<key>', 'Page');" that matters?
15:54:50 <bjo3rn> denis-fluid if you made some mistake here the extension wouldn't work at all so this should be fine (besides it is builder generated).
16:01:54 <batjony> i want to use an image field in a custom CE, and i am wondering what should I use - flux:field.file or flux:field.inline.fal ?
16:02:18 <batjony> what is the big difference between both helpers
16:02:31 <batjony> as I see the second one could be used for unlimited files
16:03:03 <batjony> but if I need only 1 file/image - what is the difference when using both helpers
16:03:05 <denis-fluid> bjo3rn: Yeah. I changed the key now. It is without underscores now but the problem remains. :(
16:06:26 <denis-fluid> bjo3rn and danilobuerger: What makes me wonder is that fluidbootstraptheme does use the "{v:variable.typoscript(path: 'plugin.tx_xyz.settings.foo')}" as well for their access to settings stuff.
16:16:51 <jmverges> just for room consideration: there are a lot of extensions that don't work properly installed as global
16:31:50 <mhmli> Are you aware that https://fluidtypo3.org/viewhelpers/vhs/master/Page/Menu/DirectoryViewHelper.html (and other pages=) always show the f:security.ifAuthenticated content?
16:52:16 <denis-fluid> danilobuerger or bjo3rn: Is it required to set the extensionKey in the ts setup like here -> https://github.com/FluidTYPO3/fluidcontent_core/blob/development/Configuration/TypoScript/setup.txt
17:01:14 <denis-fluid> The Typoscript settings are only accessible with "{v:variable.typoscript(path: 'plugin.tx_xyz.settings.foo')}" when I try to use them in the <f:section name="Configuration"> e.g. as data source for a select field.
17:02:46 <denis-fluid> I have tried a lot. I looked in the examples of fluidcontent_core and fluidbootrstraptheme
17:02:59 <denis-fluid> But nothing fixed the issue. :(
17:03:50 <denis-fluid> And I got a absolutely basic setup. The extension generated by the normal fluidtypo3 builder
17:05:16 <Akii> I don't see the problem.. why not use v:variable.typoscript then
17:05:41 <denis-fluid> Well I just want to understand why the shortform does not work.
17:05:54 <denis-fluid> (danilobuerger and bjo3rn said that it should work fine)
17:07:09 <Akii> have you tried the module thing already?
17:07:12 <denis-fluid> And in addition when I try to set the value not in the setup.txt but in the constants.txt it doesn't work at all. "{v:variable.typoscript(path: 'plugin.tx_xyz.settings.foo')}" leads to {$plugin.tx_xyz.settings.foo} as value. (it seems that the constants don't get parsed correctly)
17:46:35 <rosieres> just for the record:<v:asset name="foo" external="TRUE" standalone="TRUE" allowMoveToFooter="FALSE"><!--[if gte IE 9]><style type="text/css">foo</style><![endif]--></v:asset>
20:11:34 <denis_droid> danilobuerger: I have updated my test environment here at home to flux 7.1.2 (I had been at 7.1.1) and now it is working. (having it setup in the setup.txt)
21:45:05 <denis_droid> What is the best way to create sections inside a flux form sheet?
22:07:58 <gbod> denis_droid: Take a look https://github.com/bootstraptheme-for-typo3/fluidbootstraptheme/blob/development/Resources/Private/Templates/Content/Accordion.html
22:51:51 <denis_droid> Does someone have an idea why I’m always getting a second „Fluid Content Area“ when creating a translation for a page and switching to the „Languages“ view. I got my column from the page layout and below there is always a Fluid Content Area
22:54:46 <xaver> this are elements on 18118 (or similiar id)
22:59:30 <denis_droid> xaver: Hmm. So it is normal to see the normal main column and below the same again in a fluid content area?