IRC logs

201604

Logs from channel #fedext on freenode - our official support channel.

IRC log range: 201604*

20160401

20160402

20160403

20160404

  • 03:22:38 <Guest|25034> Hi, how to render header field from FCC in ext:news plugin, searched logs but no help, and some 'I got it' - not very helpfull.
  • 03:24:07 <cweiske> what is FCC?
  • 03:24:47 <Guest|25034> fluidcontent_core
  • 11:28:30 <justcasoer> Hi, i could need some help.
  • 11:29:07 <justcasoer> i just updated vhs and after i updated all namespaces i get a new errormsg: Could not analyse class:FluidTYPO3\Vhs\ViewHelpers\Var\SetViewHelper maybe not loaded or no autoloader?
  • 11:29:17 <justcasoer> can someone help mich with this one?
  • 11:32:42 <NamelessCoder> replace v:var.set with v:variable.set (and check the change log, there are others!)
  • 11:43:23 <justcasoer> Thank you very much! You saved my day!
  • 11:48:53 <NamelessCoder> you're welcome :)
  • 11:51:47 <justcasoer> The Homepage is running, but now i have the problem that i get the error :
  • 11:51:47 <justcasoer> Fluid Content type not selected - edit this element in the TYPO3 backend to fix this!
  • 11:53:06 <justcasoer> If i try to choose a type, "there is just: fluid Content typ" and i cant choose anything.
  • 11:54:03 <Guest|65234> hey guys
  • 11:54:08 <Guest|65234> anyone still on?
  • 11:54:20 <Guest|65234> i got a problem with vhs
  • 11:54:37 <Guest|65234> and its rendering of links
  • 11:54:42 <Guest|65234> tried this
  • 11:54:44 <Guest|65234> <v:link.typolink configuration="{parameter: '{buttonListObject.item.link}',ATagParams: 'class=button','onClick=something()'}">
  • 11:55:30 <NamelessCoder> code contains syntax error in ATagParams. String escaping required.
  • 11:55:55 <Guest|65234> sorry?
  • 11:56:02 <Guest|65234> what woulod be the correct way?
  • 11:56:07 <Guest|65234> *would
  • 11:56:40 <Guest|65234> each param on its own works
  • 11:56:50 <Guest|65234> but it is not working with bot params
  • 11:57:23 <NamelessCoder> ATagParams: 'class=button','onClick=something()'
  • 11:57:59 <Guest|65234> but this is what i did?
  • 11:58:57 <NamelessCoder> but that's not what you should do. Check the typolink reference what it requires as type of the "ATagParams" configuration array member then make sure you pass that format
  • 11:59:21 <NamelessCoder> if it wants an array, you need to pass ATagParams: {class: 'button', onClick: 'something();'}
  • 11:59:48 <NamelessCoder> if it wants a string, that string likely needs a custom format for those properties, for example 'class=button onclick=something();'
  • 12:01:04 <Guest|65234> in doc it is said to do it like this:
  • 12:01:10 <Guest|65234> <v:link.typolink configuration="{parameter: '{buttonListObject.item.link}',additionalParams: 'class=button','onClick=something()'}">
  • 12:01:26 <Guest|65234> but this doesn't work too
  • 12:01:46 <NamelessCoder> that's probably not from our docs, if it is, someone made a pretty big mistake.
  • 12:02:25 <Guest|65234> https://fluidtypo3.org/viewhelpers/vhs/master/Link/TypolinkViewHelper.html
  • 12:02:26 <NamelessCoder> multiple things tell me it's not official docs, for one thing the formatting. We always put spaces between array keys and previous values
  • 12:02:53 <NamelessCoder> the code you gave does not appear on that page
  • 12:03:12 <Guest|65234> last example
  • 12:04:08 <Guest|65234> please could you just give me an example how to generate a vhs link with class and onclick
  • 12:04:11 <NamelessCoder> the docs really do not say to do it that way. They say that "configuration" is supposed to be an array, can be defined inline if you wish, or come from a variable. How that array must be structured is noted in the docs the main text links to, on the official TYPO3 docs site (since we do not document that array - it is entirely TYPO3 core and also applies many other places than Fluid)
  • 12:05:11 <NamelessCoder> that depends on how you defined that link - the TCA of buttonListObject.item.link.
  • 12:05:28 <NamelessCoder> if it contains an URL I would just use simple <a href=""> tags.
  • 12:06:21 <NamelessCoder> if it is a link wizard then you do need this v:link.typolink but may consider plain <a href=""> combined with the URI version https://fluidtypo3.org/viewhelpers/vhs/master/Uri/TypolinkViewHelper.html and put your onclick stuff in the a-tag properties as normal
  • 12:06:21 <Guest|65234> no it is coming form link wizard
  • 12:06:59 <NamelessCoder> use the URI version of the ViewHelper as value of the "href" attribute of your <a> tag
  • 12:09:40 <Guest|65234> you mean like this?
  • 12:09:41 <Guest|65234> <a href="<v:uri.typolink configuration='{buttonListObject.item.link}'" class="button" onclick="something()"> Link-Label </a>
  • 12:10:50 <NamelessCoder> you should take a closer look at the fluid syntax documentation (or you will have a pretty hard time in the future after I give you the facit on this one)
  • 12:11:17 <NamelessCoder> <a href="{v:uri.typolink(parameter: buttonListObject.item.link)}" class="button" onclick="something">Link label</a>
  • 12:12:03 <NamelessCoder> it'll be very hard to solve many use cases unless you know about such alternative versions of viewhelpers as well as how to use inline syntax
  • 12:14:31 <justcasoer> NamelessCoder: can i ask you one more questen, when you are finished?
  • 12:14:40 <Guest|65234> : Argument "parameter" was not registered.
  • 12:14:54 <Guest|65234> used the code you wrote in
  • 12:17:13 <NamelessCoder> <a href="{v:uri.typolink(configuration: {parameter: buttonListObject.item.link)}}" class="button" onclick="something">Link label</a>
  • 12:17:52 <NamelessCoder> I wouldn't expect you to catch that one - but it would have been more likely if you were comfortable with the inline syntax instead of just copy/pasting ;)
  • 12:18:13 <NamelessCoder> justcasoer don't ask to ask, just ask
  • 12:18:31 <Guest|65234> this generates this:
  • 12:18:31 <Guest|65234> <a href="{v:uri.typolink(configuration: {parameter: buttonListObject.item.link)}}" class="button" onclick="something">Link label</a>
  • 12:22:28 <justcasoer> sorry i already asked but then the guest joinded an i dont wanted to be impolite.
  • 12:22:37 <justcasoer> i geht this error on the page: Fluid Content type not selected - edit this element in the TYPO3 backend to fix this!
  • 12:22:45 <justcasoer> but i cant chose a type
  • 12:24:53 <NamelessCoder> justcasoer if your TCA or ACL doesn't allow tx_fed_fcefile you should fix that
  • 12:25:21 <NamelessCoder> if it does and the values don't include your template, you may have a parsing error
  • 12:25:55 <NamelessCoder> <a href="{v:uri.typolink(configuration: {parameter: buttonListObject.item.link}})" class="button" onclick="something">Link label</a> (gotta know that inline syntax)
  • 12:26:02 <justcasoer> i dont really understand what you mean. i just updated from 6.1.x to 6.2.x . before the update everything worked
  • 12:27:21 <NamelessCoder> justcasoer is the "Content type" set to "Fluidcontent" and do you see the field "Fluid content type" when editing the content and does the selector have any values?
  • 12:28:21 <justcasoer> "Fluid content type"
  • 12:28:34 <justcasoer> just this one
  • 12:29:53 <NamelessCoder> justcasoer you are looking for this field: http://i.imgur.com/ZEJNpAy.png
  • 12:30:39 <Guest|65234> thank you, you made my day. and yes you are right i have to know more about the correct syntax. i am still in learning process.
  • 12:30:45 <NamelessCoder> when "Type" (which is CType in database) is set to "fluidcontent_content" (the value behind the label "Fluid Content" in the left selector), then you should see the right selector listing all your templates
  • 12:31:10 <NamelessCoder> you're welcome Guest|65234
  • 12:31:52 <Guest|65234> you changed the ending brackets:
  • 12:31:54 <Guest|65234> <a href="{v:uri.typolink(configuration: {parameter: buttonListObject.item.link})}" class="button" onclick="something">Link label</a>
  • 12:32:01 <Guest|65234> this worked :)
  • 12:32:16 <NamelessCoder> yeah, 4K monitor + distance + hurry = typos :)=
  • 12:32:32 <Guest|65234> have a good day furthermore
  • 12:32:36 <NamelessCoder> you too!
  • 12:32:40 <justcasoer> http://s23.postimg.org/b4xjixj17/typo3.jpg
  • 12:33:36 <NamelessCoder> justcasoer if the selector has no values then my comment from 18:25 applies - you probably have a parsing error in the template
  • 12:33:47 <NamelessCoder> (which would cause it to be excluded from configuration)
  • 12:34:15 <NamelessCoder> that, or you have additional migrations to perform after updating one or more extensions (vhs, flux) - see changelogs of each to know what to migrate
  • 12:35:06 <justcasoer> i updated an activated everything like before. thank you for the hint. i will try to find the error tomorrow.
  • 12:35:19 <justcasoer> i hope i gonna find it
  • 12:36:23 <justcasoer> have a nice day!
  • 12:36:27 <NamelessCoder> you too :)

20160405

  • 04:47:16 <mddz> hi there
  • 04:47:34 <mddz> how can I set the upload folder for a flux:field.inline.fal viewhelper?
  • 04:52:38 <cweiske> I don't think this is possible
  • 04:58:16 <mddz> why not?
  • 04:59:30 <mddz> There is the flux:field.file viewhelper which can have a upload folder specified, but I can't get multiple file selection to work, despite it having attributes suggesting it should be possible.
  • 04:59:50 <cweiske> I cannot explain why I think something. I just do.
  • 05:06:16 <mddz> I don't want to know why you are thinking it, but why it is not possible ;)
  • 05:07:09 <mddz> I can't quite understand the reasoning for all these different File-related viewhelpers with vastly different capabilites, but I guess it is caused by TYPO3
  • 05:08:56 <cweiske> it is currently not possible because the view helper does not have an uploadfolder attribute, see https://fluidtypo3.org/viewhelpers/flux/master/Field/InlineViewHelper.html
  • 05:11:47 <mddz> yeah, I saw thad (and got a PHP error when trying if it was possible anyways)
  • 05:12:36 <mddz> so is there any 'best practive' for multiple file upload with defined upload folder?
  • 05:13:05 <mddz> I don't want to get the userupload folder get messed up by dozens of content elements which use images
  • 05:13:47 <cweiske> you could disable the upload button at the inline fal element
  • 05:13:53 <cweiske> so users are forced to upload through the file list
  • 05:16:29 <mddz> I am not quite sure which file list you mean?
  • 05:16:58 <cweiske> on the left side of your typo3 backend
  • 05:17:38 <mddz> ah I see, but I wanted to use a upload folder which is outside of the users reach
  • 05:17:53 <cweiske> typo3 would prevent that
  • 05:18:04 <cweiske> because the user has to have write permission to the folder
  • 05:18:09 <cweiske> via a file mount
  • 05:18:11 <cweiske> and thus he can see it
  • 05:18:14 <cweiske> in every case
  • 05:18:20 <cweiske> there is no out-of-reach
  • 05:18:58 <mddz> but it works with flux:field.file and uploads/tx_myext/...
  • 05:19:32 <cweiske> ah ok, so you don't mean fileadmin/
  • 05:43:43 <mikeMM> hey.. i use v:content.render with vhs 2.4.. when a page is not translated my content-elements are not rendered... i found this link... but it does not help me further.. is there allready a fix for this issue?
  • 05:44:01 <cweiske> which link?
  • 05:44:36 <mikeMM> oh.. can not paste link... Issue: FluidTYPO3/vhs/issues/761
  • 05:45:01 <cweiske> no, the issue represents the current state of affairs
  • 05:46:11 <mikeMM> ok.. the github issue says the problem is only there when the page is translated but not the content elements... in my case it's not working when there is no translation for the page at all
  • 05:46:40 <cweiske> then please add your observation as comment to the issue
  • 05:46:49 <cweiske> should be the same underlying problem
  • 05:48:50 <mikeMM> ok.. thank you
  • 06:37:34 <fka> hi there :)
  • 06:37:46 <fka> i have a custom ce with the following field in the configuration: <flux:field.relation name="settings.dummy" size="5" minItems="1" maxItems="99" table="mymodel" />. Now, in the main part, i want to display the selected records. transform="array" works as expected, but i still only got the uids. transform="ObjectStorage" and "mymodel" seem to do not
  • 06:37:46 <fka> hing in my case, i still get a string with comma-separated uids. any hint what i am doing wrong? :) thx
  • 06:48:38 <cweiske> there is a difference between storing the selected records in the database, which is done as CSV
  • 06:48:48 <cweiske> and the other side is actually reading those values
  • 06:49:53 <cweiske> in your main section, you need to "expand" the csv values to a list of objects
  • 06:53:29 <fka> thx for your answer. which viewhelper can do this for me? or must i use a userfunc/own vh for this?
  • 06:53:50 <cweiske> I thought that one could use one of the view helpers in https://fluidtypo3.org/viewhelpers/vhs/master/Resource/RecordViewHelper.html
  • 06:54:03 <cweiske> but there does not seem to be one that supports CSV values
  • 06:54:21 <cweiske> no idea actually
  • 06:54:29 <cweiske> maybe NamelessCoder or cedricziel can answer this
  • 06:55:17 <fka> just out of interest, for what can i use transform="mymodel" and transform="ObjectStorage"?
  • 06:55:36 <fka> thought ObjectStorage is exactly what i need.
  • 06:56:10 <cweiske> As far as I think, this determines the way it is stored in the database
  • 06:56:15 <cweiske> your selection
  • 06:56:25 <cweiske> how it is stored
  • 07:04:08 <fka> hmmm, v:resource.record is not the right vh i think...
  • 07:04:22 <cweiske> that's what I said
  • 07:04:34 <fka> missed that :)
  • 07:04:36 <cweiske> none of the v:resource.* view helpers have a csv field
  • 07:04:41 <cweiske> s/field/attribute
  • 07:06:44 <fka> no, i mean not in combination with csv values. when i set transform="array" i can iterate over the selected pids.
  • 07:07:37 <fka> but as i want the whole model object and not only a field associated to resources i think it is the wrong vh for my usecase
  • 07:30:59 <fka> ok i was using transform wrong, ObjectStorage needs the Modeltype as written in the docu and instead of mymodel i have to set the full namespace, ofc *facepalm*
  • 07:31:18 <fka> it is still not working tho, but i think im heading in the right direction
  • 07:50:09 <cweiske> fka, if you solve your problem
  • 07:50:14 <cweiske> please post the code
  • 07:59:25 <fka> sure
  • 08:01:12 <fka> the problem is, my classes don't get autoloaded (they are not listed by get_declared_classes())... i built my extension with the extension builder, so i thought all naming conventions should be fine...
  • 08:18:07 <fka> ok after fixing my extension everything works like a charm. sorry for wasting your time... the problem was i used the tablename as value for the transform attribute, not the classname
  • 08:18:15 <fka> this is the code: <flux:field.relation transform="ObjectStorage<Vendor\Extkey\Domain\Model\MyModel>" name="settings.dummy" size="5" minItems="1" maxItems="5" table="mymodel_table" />
  • 08:18:15 <fka> <flux:field.relation transform="Vendor\Extkey\Domain\Model\MyModel" name="settings.dummy" size="1" minItems="1" maxItems="1" table="mymodel_table" />
  • 08:18:46 <cweiske> that's in the configuration section, right?
  • 08:18:54 <fka> first one for multiselection, second for single
  • 08:18:55 <fka> yes
  • 08:22:34 <fka> thank you guys for this awesome set of extensions and have a nice day!
  • 12:36:29 <fka> hello!
  • 12:38:04 <fka> i've got a problem with custom content controller... the Actio-method for my contentelement is not called... however, the initialization methods (initializeProvider, initializeSettings...) are correctly called...
  • 12:38:15 <fka> any ideas what the problem might be?
  • 12:55:53 <fka> ok i changed the namespace of my ContentController from 'FluidTYPO3\Fluidcontent\Controller' to the namespace used in my extension. now the action methods are called, but the initialization methods no longer work :(

20160406

  • 03:26:57 <Guest|91866> Hi guys, is there any way to show in Backend all content elements in some custom defined order? Now I have 55 different panels and they are shown as follows: Panel 55, Panel 34, Panel 2, Panel 27 etc.
  • 03:31:11 <cweiske2> do you mean in the new content element wizard?
  • 03:32:42 <Guest|91866> yes, in the New content element wizard
  • 03:32:50 <cweiske> I'd like to know that, too :)
  • 03:32:57 <Guest|91866> :)
  • 03:37:10 <cweiske> typo3 8 contains a way to influence the order of the tabs; https://forge.typo3.org/issues/71876
  • 03:37:20 <cweiske> but I don't know of any for the order of the items themselves
  • 03:39:34 <cweiske> looking at NewContentElementController.php tells me it's not possible
  • 04:54:27 <Guest|91866> thank you cweiske
  • 09:18:02 <drlimbo> good afternoon
  • 09:18:39 <drlimbo> do i do something wrong with v:iterator.explode or why is "limbo" still Null?
  • 09:18:41 <drlimbo> <v:iterator.explode as="limbo" content="8,7,1" glue=",">{limbo -> f:debug()}</v:iterator.explode>
  • 09:25:03 <drlimbo> maybe cweiske has an idea?
  • 10:27:43 <drlimbo> someone else?
  • 12:05:39 <NamelessCoder_> you may have found a bug drlimbo - with that code the {limbo} variable should absolutely be filled. Maybe v:iterator.explode doesn't use the TemplateVaribleViewHelperTrait correctly

20160407

  • 04:58:43 <mddz> hi there
  • 04:59:22 <mddz> what to do if language labels of Page Layouts are not resolved in the backend page settings?
  • 05:07:32 <cweiske> are you using the extensions from TER?
  • 05:07:35 <cweiske> or from git?
  • 05:09:39 <mddz> git
  • 05:09:50 <cweiske> there is an open bug for this issue
  • 05:09:54 <cweiske> the TER version works
  • 05:10:39 <cweiske> https://github.com/FluidTYPO3/fluidpages/issues/313
  • 05:10:48 <mddz> ah I see
  • 05:10:53 <cweiske> oh, it's closed
  • 05:11:15 <cweiske> so it should be solved if you're running latest git
  • 05:11:19 <mddz> so is it fixed?
  • 05:11:38 <cweiske> so it should be solved if you're running latest git
  • 05:11:48 <mddz> I did not pull the newest version from git for some weeks
  • 05:11:57 <mddz> will try that out
  • 05:12:24 <mddz> btw, what is the recommended way of updating the extension?
  • 05:12:29 <cweiske> via TER
  • 05:12:42 <mddz> should I deactivate the extensions before I pull from git and then reactivate after?
  • 05:12:43 <cweiske> git master can always have problems and bugs
  • 05:12:57 <cweiske> that depends
  • 05:13:11 <cweiske> after updating, you should always clear class cache and compare database
  • 05:14:30 <mddz> compare the database manually? Or is there a TYPO3 function for that?
  • 05:14:38 <cweiske> install tool -> compare database
  • 05:18:55 <mddz> ok, thank you :)
  • 07:04:09 <moger> I have a multidomain TYPO3 instance with 4 trees (root levels) and 4 provider extensions. I'm trying to limit the availability of the page template sets to the respective trees.
  • 07:04:38 <cweiske> understandable
  • 07:04:43 <cweiske> but I have no idea how to do this
  • 07:05:08 <moger> by debugging through the code, i found out that plugin.tx_myprovider.view.enable = 0 works to archive that.
  • 07:05:42 <cweiske> cool
  • 07:06:06 <moger> so far so good - it works on all subpages of each tree.
  • 07:06:24 <moger> But not on the root pages. there, the "first" provider always "wins".
  • 07:06:45 <cweiske> what do you mean by "wins"?
  • 07:07:06 <moger> in the available layouts, i always have only the first provider.
  • 07:07:35 <cweiske> this is strange; it works fine with multiple providers here
  • 07:08:08 <moger> that's because of \FluidTYPO3\Flux\Service\FluxService::getViewConfigurationForExtensionName delivers wrong settings.
  • 07:08:15 <cweiske> http://fotos.cweiske.de/screenshots/2016-04-07%20typo3%20page%20layout%20selection.png
  • 07:09:58 <moger> yes, if i keep all providers enabled, of course i have all of them available everywhere.
  • 07:10:49 <moger> but once i disable some, but only in subtrees, the configuration which is read by flux differs from the typoscript configuration which can be seen in the backend (template analyzer / object manager)
  • 07:10:53 <moger> very strange.
  • 07:25:27 <moger> I debugged some more. the wrong pageId is determined by \TYPO3\CMS\Extbase\Configuration\BackendConfigurationManager::getTypoScriptSetup
  • 07:25:48 <moger> now I need to find out why.
  • 08:29:47 <mddz> Ho do I add css classes to the wrapping div of ContentCore elements?
  • 08:52:39 <mddz> ok, I think the easiest way is to just override the ContentCore Layout
  • 12:10:43 <drlimbo> hi there
  • 12:11:41 <drlimbo> does someone has an idea why image-croping works well in the install tool, but on my website f:image and v:uri.image doesn't resize my pictures?
  • 15:29:00 <Obiwan> Hi, somehow i can't render the output of an ext base-plugin (t3sheaderslider) with typoscriptObjectPath=... within fluid pages. But I see the output if i append it in e.g. page.10. Any suggestions?
  • 15:30:07 <Obiwan> *grabs a beer*

20160408

  • 02:21:09 <cweiske> is it possible to make a fluidcontent element aware of the container it is located in?
  • 02:21:32 <cweiske> I thought I could pass a variable in <v:content.render>, but that does not appear to be the case
  • 05:46:55 <haki> hi, since i updated from typo 6.1.x to 6.2.19 ( also the fluid extensions ) i dont get any content. i just get a yellow box with the text "Fluid Content type not selected - edit this element in the TYPO3 backend to fix this!
  • 05:46:56 <haki> Content uid: [135] " can you help me with this one?
  • 05:51:43 <cweiske> are the fluid extensions from TER or from git?
  • 05:52:18 <haki> i took over the project so i dont know. i updated them with the update manager in the backend.
  • 05:52:25 <cweiske> ok, so from TER
  • 05:52:37 <cweiske> which version has fluidcontent?
  • 05:53:10 <haki> 4.3.3
  • 05:55:57 <cweiske> haki, https://github.com/FluidTYPO3/fluidcontent/blob/development/CHANGELOG.md#433---2015-10-24
  • 05:56:15 <cweiske> did you actually check if this is the case with some of your content elements?
  • 05:58:51 <haki> No, it's my first real typo3 project.
  • 05:59:23 <cweiske> then check if there are content elements on your page which do not have a fluid content type set
  • 05:59:31 <haki> Disabled Fluid Content type drop-down for all CTypes, except fluidcontent_content .... i dont really get what this means
  • 05:59:41 <cweiske> #278 In case no Fluid Content type is selected for content with CType fluidcontent_content an error message is shown in FE and BE
  • 05:59:48 <cweiske> this is the one which is important for you
  • 06:03:23 <haki> http://s9.postimg.org/wqofwq49r/fluid.jpg it lookes like this
  • 06:03:49 <cweiske> in the top circled dropdown you actually have to SELECT A CONTENT ELEMENT
  • 06:04:29 <haki> oh the screenshot close the drop down. i cant select anything there. just "Fluid Content type"
  • 06:04:53 <cweiske> then this is your problem
  • 06:05:08 <cweiske> so this content element does not serve any purpose, does it?
  • 06:05:09 <cweiske> remove it
  • 06:05:46 <cweiske> do you actually have fluid content elements?
  • 06:05:51 <cweiske> in your extensions?
  • 06:06:45 <haki> you mean in the template?
  • 06:07:03 <haki> even if i want to create new content i get this error.
  • 06:07:05 <cweiske> do you know what the fluidcontent extension is for?
  • 06:08:19 <haki> it adds dynamic content
  • 06:08:25 <haki> in the template
  • 06:08:53 <cweiske> what dynamic content?
  • 06:09:07 <haki> i'm sorry if i frustrate you with my low knowlege base
  • 06:09:40 <haki> oh you mean what it does in my template?
  • 06:09:51 <cweiske> no
  • 06:10:04 <cweiske> I want to know if you know what fluidcontent does, and how to use it
  • 06:10:42 <haki> not really, i overtook the project and have to handle it now :/
  • 06:10:58 <cweiske> please come back after reading up what fluidcontent actually does
  • 06:12:32 <haki> https://fluidtypo3.org/documentation/templating-manual/introduction.html i just start reading this now.
  • 08:54:34 <haki> cweiske so the problem is that i didnt define a fluid contetn type right?
  • 08:58:51 <haki> or does anybody else have experience with the "Fluid Content type not selected - edit this element in the TYPO3 backend to fix this! " error?
  • 09:02:37 <drlimbo> is there a way to set the "lifetime" of _processed_ images with fluid?
  • 09:11:45 <cweiske> haki, exactly
  • 09:13:05 <haki> is it possible that there was no need to define it in older versions?
  • 09:16:52 <cweiske> see the changelog
  • 09:16:57 <cweiske> with the update, the error message came
  • 09:17:08 <cweiske> before maybe nobody noticed it
  • 09:17:24 <cweiske> haki, it's probably better to go back to the extension versions you had before
  • 09:17:32 <cweiske> and check how it looked then
  • 09:17:44 <cweiske> maybe fluidcontent now does not detect your content elements anymore
  • 09:18:56 <haki> i think it not that easy, because i had to update from typo3 6.1.x to 6.2.19.
  • 09:19:33 <haki> but im uploading the old version now and check again.
  • 10:04:52 <drlimbo> is there a way to show values from a typoscript array in an extbase Select Field (TCA)
  • 16:52:55 <Guest|28325> hi
  • 16:54:11 <Guest|28325> everytime i try to install fluidcontent 4.4.0 i get the error: Could not access remote resource http://repositories.typo3.org/mirrors.xml.gz.
  • 16:54:19 <Guest|28325> can anyone help me with this one?

20160409

20160410

  • 21:37:47 <NamelessCoder> veni, vidi, issue-closie

20160411

  • 02:56:20 <mdddz> hi guys
  • 02:56:36 <mdddz> I encountered a strange bug:
  • 02:57:57 <mdddz> from time to time, but only when I am logged out of the Backend, and only until I log in again TYPO3 forgets my TS config, which is included via \FluidTYPO3\Flux\Core::addStaticTypoScript(...);
  • 02:58:02 <mdddz> Is this a known problem?
  • 02:59:03 <cweiske> not to me, no
  • 02:59:08 <cweiske> did you look at the bug list?
  • 02:59:48 <mdddz> The open issues at github?
  • 02:59:55 <cweiske> yes
  • 03:00:52 <mdddz> I looked for some minutes, but not at every issue of every extension
  • 03:03:35 <cweiske> can you reproduce the problem again and again, or does it really only happen now and then?
  • 03:06:51 <de_macrocom> Hi there. I posted a question concerning controller arguments in FluidTYPO3 on http://stackoverflow.com/questions/36505001/how-to-pass-argument-to-controller-action-with-fluidtypo3
  • 03:07:17 <de_macrocom> Seems nobody can help there. Can you?
  • 03:43:37 <mdddz> cweiske: sorry, there was a meeting I had to attend to
  • 03:44:05 <mdddz> I can't repdoduce it reliable
  • 03:44:37 <mdddz> sometimes, it occures immediately when I log out
  • 03:44:55 <mdddz> but most of the times it just works fine for some time
  • 03:46:43 <mdddz> I notice it mostly in the morning, when I haven't work for some hours. Especially on Monday mornings, like today.
  • 03:46:52 <mdddz> Looks like a caching error of some kind
  • 03:47:40 <cweiske> what typoscript do you have in that file?
  • 03:49:11 <mdddz> It is a provider extensions which supllies all TS needed for the installation
  • 03:49:57 <mdddz> 'global' config / page setup mainly
  • 03:51:08 <mdddz> and then some fluid powered basics, like overriding ContentCore template paths
  • 03:51:22 <cweiske> does it work when you use typo3's default method to include static typoscript?
  • 03:52:44 <mdddz> I tried Option 1 and 2 ( https://fluidtypo3.org/documentation/templating-manual/templating/provider-extension/configuration-files.html ) but could'nt make it work
  • 03:53:16 <mdddz> the TS just did not produce any effect like it was not read afterall
  • 03:53:37 <cweiske> for option 1 you need a setup.txt in the folder you add via "addstaticfile"
  • 03:53:58 <cweiske> *and* you need to include it in you main typoscript template in the database
  • 03:53:58 <mdddz> yes, there is one named exactly that way
  • 03:54:08 <cweiske> did you do that?
  • 03:54:55 <mdddz> I added it in the "Include" tab in the template settings
  • 03:55:03 <cweiske> and that did not work?
  • 03:55:05 <cweiske> this is very strange
  • 03:55:06 <mdddz> "Includes"*
  • 03:55:18 <cweiske> http://fotos.cweiske.de/screenshots/2016-04-11%20typo3%20includes.png
  • 03:55:41 <cweiske> I guess you should try to get that to work correctly
  • 03:56:16 <mdddz> could this be like a TS parsing error?
  • 03:56:37 <mdddz> but there should be some error message if it was
  • 03:56:44 <cweiske> you can always check that in the typoscript object browser
  • 03:56:49 <cweiske> if your setup works
  • 03:56:59 <cweiske> and the template analyzer
  • 04:13:17 <mdddz> ok, this could be more of a TYPO3 issue than anything fluid-powered related, but maybe you can help me out nontheless:
  • 04:13:32 <mdddz> I included the TS with TYPO3's default method
  • 04:13:49 <mdddz> and I can see it in the TS object browser
  • 04:14:02 <mdddz> like the page setup with all my css / js ressources
  • 04:14:13 <mdddz> but it doesn't take any effect in the frontend
  • 04:15:03 <mdddz> but on the other hand, the meta tags I set via viewhelper in the page layout are displayed correctly
  • 06:44:14 <haki> Hello,
  • 06:44:48 <haki> everytime i try to install fluidcontent 4.4.0 i get the error: Could not access remote resource http://repositories.typo3.org/mirrors.xml.gz. can someone help me with this one?
  • 06:47:06 <cweiske> that's a general typo3 problem, not a fluid specific one
  • 06:47:19 <cweiske> fix your network connectivity problems on your server
  • 06:47:27 <cweiske> ssh into it and curl or wget this file
  • 06:47:34 <cweiske> you'll probably get more information that way
  • 06:47:47 <haki> its not the server. i can install the newer versions, but not the 4.4.0
  • 06:48:58 <haki> sorry i mean 4.0.0
  • 07:01:07 <haki> i found a solution. thank you
  • 07:02:51 <cweiske> what solution?
  • 07:05:24 <haki> i had to activate "[SYS][curlUse]" in the install tool
  • 07:05:39 <cweiske> why?
  • 07:07:08 <haki> i found the solution for error "Could not access remote resource http://repositories.typo3.org/mirrors.xml.gz." that i have to do it
  • 07:08:09 <cweiske> so you don't have any technical reasons for it
  • 07:08:54 <haki> no
  • 07:09:38 <cweiske> too bad :/
  • 07:15:21 <de_macrocom> Good afternoon. How do I pass arguments to a flux-enabled controller? It just doesn't work out for me as detailed here: http://stackoverflow.com/questions/36505001/how-to-pass-argument-to-controller-action-with-fluidtypo3 Any hints?
  • 07:39:03 <drlimbo> hi there
  • 07:39:39 <drlimbo> i just created an extbase extension - is there a way to use the current page as storagePid if there is nothing set in the plugin?
  • 07:42:56 <cweiske> current page is at $GLOBALS['TSFE']->id
  • 07:50:35 <grimmcreative> Hello @all, how can i get my data from a flux:field (from page template) inside my v:page.menu? just {name} does nothing {pageRecord.name} too :( (all newest TER Versions of extensions) — THANKS
  • 07:53:33 <bjo3rn> grimmcreative there's flux:form.data to extract a flexform's values.
  • 07:54:45 <grimmcreative> Ok - will try it :) thanks
  • 07:55:15 <bjo3rn> something like {section -> flux:form.data(table: 'pages', field: 'tx_fed_page_flexform') -> v:variable.set(name: 'sectionFormData')}
  • 07:57:51 <haki> one more question, any idea for: Fatal error: Call to undefined method FluidTYPO3\Fluidcontent\Service\ConfigurationService::getTypoScriptSubConfiguration() in ?
  • 08:03:26 <drlimbo> thanks cweiske, i just tried something like that:
  • 08:03:26 <drlimbo> $gridelements = $this->gridelementRepository->findAll();
  • 08:03:27 <drlimbo> $this->gridelementRepository->setRespectStoragePage(FALSE);
  • 08:03:27 <drlimbo> $this->gridelementRepository->setStoragePageIds($GLOBALS['TSFE']->id);
  • 08:03:27 <drlimbo> $this->view->assign('gridelements', $gridelements);
  • 08:14:19 <drlimbo> ah, i think i got it cweiske =)
  • 08:14:24 <drlimbo> thanks for your hlep
  • 08:14:26 <drlimbo> *help
  • 08:15:38 <grimmcreative> thanks @bjo3rn - works
  • 08:26:56 <drlimbo> v:uri.image replaces " " (Spaces) in Image-URLs with "%2520" instead of "%20" - is there a way to fix that?
  • 08:27:24 <cweiske> looks like double encoding
  • 08:27:32 <cweiske> %25 is "%" encoded
  • 08:28:55 <drlimbo> ah, loks like cweiske
  • 08:29:02 <drlimbo> but i have no idea where this gets double-encoded
  • 08:29:21 <cweiske> what arguments do you pass to v:uri.image?
  • 08:30:04 <drlimbo> {v:uri.image(src:gridelement.migratedimage, relative: 1, width: '{imgWidth}c', height: '{imgHeight}c')}
  • 08:30:21 <drlimbo> gridelement.migratedimage is a string with somes spaces
  • 08:30:46 <cweiske> where do you use that {v:uri.image}?
  • 08:30:49 <cweiske> the surrounding code?
  • 08:31:33 <drlimbo> <img src="..PLACEHOLDER.png" data-original="{v:uri.image(src:'gridelement.migratedimage', relative: 1, width: '{imgWidth}c', height: '{imgHeight}c')}" alt="{gridelement.title}" width="{imgWidth}" height="{imgHeight}"/>
  • 08:32:24 <cweiske> didn't fluid have some kind of auto-escaping?
  • 08:33:33 <drlimbo> i dont know
  • 08:33:45 <drlimbo> just tested that this works: <img src="{v:uri.image(src:gridelement.migratedimage, relative: 1, width: '{imgWidth}c', height: '{imgHeight}c') -> v:format.replace(substring:"%2520", replacement:"%20")}" />
  • 08:33:47 <drlimbo> but its ugly =P
  • 10:06:29 <drlimbo> crazy... i have an extbase extension and in the list view in fluid i debug v:page info {v:page.info() -> f:debug()} BUT this returns me an incorrect UID of the actual page, but the correct content
  • 10:06:45 <drlimbo> and i have only one list element on this page, but i get the debug two times
  • 10:11:54 <de_macrocom> I also see that multiple debug rather often. So would also be interested what causes it.
  • 10:13:39 <drlimbo> mhh, i think realurl messed something around, i just saw in the table that i have two pages with the same name
  • 10:17:02 <drlimbo> yes, it was realurl, so everything ok with debug, sorry de_macrocom

20160412

  • 04:50:32 <Fluidrules> Hi room. I have an f:image element, which gets its information from a flux:field.inline.fal field. The TYPO3 backend offers a "link" field for the editor, too. How do I get the entered information? I want the image to be wrapped with the link. No need for lengthy explanation, I think I can work with a working example I can copy off.
  • 08:46:17 <drlimbo> hi there
  • 08:46:27 <drlimbo> is there a way to use v:switch and v:case inline?
  • 09:15:21 <Fluidrules> drlimbo, there is inline syntax in the documentation, but I couldn't find a working example
  • 09:15:23 <Fluidrules> {f:switch(expression: [mixed])}
  • 09:25:33 <drlimbo> looks like =P
  • 09:36:13 <Fluidrules> here's case: {f:case(value: [mixed], default: 1)}
  • 09:37:22 <Fluidrules> so there's two problems - 1. What do you write instead of [mixed] and 2. how do you wrap the case around the switches if it's all inline?
  • 10:24:24 <Fluidrules> Are you still there, drlimbo?
  • 10:28:28 <drlimbo> yup sorry Fluidrules
  • 10:28:54 <drlimbo> i just jused a workaround with settings variables and use them inline
  • 10:29:27 <Fluidrules> sounds good.
  • 10:31:24 <drlimbo> its ok =P
  • 10:31:50 <drlimbo> but it would be interesting to find a solution for nested switch-case =)
  • 10:50:57 <Fluidrules> agreed, drlimbo. the examples database on fluidtypo3.org is extremely helpful, but non-devs like us need many more examples to grasp it. Maybe you have an idea how to solve my problem?
  • 10:51:16 <Fluidrules> I have an f:image element, which gets its information from a flux:field.inline.fal field. The TYPO3 backend offers a "link" field for the editor, too. How do I get the entered information? I want the image to be wrapped with the link.
  • 10:52:44 <drlimbo> where do u have the FAL field? in your extension Fluidrules?
  • 11:19:40 <Fluidrules> drlimbo: yes.
  • 11:19:57 <drlimbo> mh, so in your extbase extension?
  • 11:20:10 <drlimbo> or just in fluid?
  • 11:20:12 <Fluidrules> it's a content template (FCE) in a fluidcontent extension
  • 11:20:23 <Fluidrules> just a provider extension for the template
  • 11:20:37 <drlimbo> ah, so you need to get the FAL Files with v:resource.record.fal
  • 11:20:56 <Fluidrules> that sounds good
  • 11:20:58 <drlimbo> for example: {v:resource.record.fal(record: page, field: 'media', table: 'pages') -> v:variable.set(name: 'pageMedia')} to get the "Ressources" Images from Page
  • 11:21:33 <drlimbo> and dont forget the "treatIdAsReference: 1" setting in the image viewhelper
  • 11:21:34 <Fluidrules> I get the src, title and alt from {v:content.resources.fal(field: 'settings.image1') -> v:iterator.first() -> v:variable.set(name: 'image')}
  • 11:22:27 <Fluidrules> v:resource.record.fal vs v:content.resources.fal
  • 11:23:07 <drlimbo> ah, and dont use FAL-Images in a section - this wont work
  • 11:23:39 <Fluidrules> it works I just need the link
  • 11:25:02 <Fluidrules> I use e.g. <flux:field.inline.fal name="settings.image2" label="Image large" /> in the form and {v:content.resources.fal(field: 'settings.image2') -> v:iterator.first() -> v:variable.set(name: 'image')}
  • 11:25:02 <Fluidrules> <f:image src="{image.id}" title="{image.title}" alt="{image.alternative}" /> in the section.
  • 11:27:36 <Fluidrules> what would really help is an example of how to get a single FAL image with the link wrapped around.
  • 11:28:37 <drlimbo> there's a viewhelper to get the image url (resource.url something..)
  • 11:30:36 <Fluidrules> are you sure that's not just the path to the image?
  • 11:31:10 <Fluidrules> ... that would be the src...
  • 11:31:20 <drlimbo> https://fluidtypo3.org/viewhelpers/vhs/master/Uri/ImageViewHelper.html
  • 11:33:24 <Fluidrules> Maybe I'm explaining it badly. I know how to output the image.
  • 11:34:22 <Fluidrules> in the backend there is a field where you can assign a link to an image. That means, the image should be 'linked' with a URL, e.g. google.com.
  • 11:34:37 <Fluidrules> But I don't know how I can use this link in my frontend.
  • 11:44:03 <Fluidrules> it's not in <f:debug>{settings}</f:debug>
  • 12:02:53 <Fluidrules> can't find it in <f:debug>{all}</f:debug> either.
  • 12:05:04 <Fluidrules> found it... image.link
  • 12:05:37 <Fluidrules> works only when I debug just below the image tag in my Main section.
  • 12:10:28 <Fluidrules> now I need a conditional: if there's a link, wrap a link around the image, if not, don't wrap anything.
  • 12:13:06 <Fluidrules> solved, like this: {v:content.resources.fal(field: 'settings.image2') -> v:iterator.first() -> v:variable.set(name: 'image')}
  • 12:13:11 <Fluidrules> <f:if condition="{image.link}">
  • 12:13:15 <Fluidrules> <f:then>
  • 12:13:21 <Fluidrules> <a href="{image.link}"><f:image src="{image.id}" title="{image.title}" alt="{image.alternative}" /></a>
  • 12:14:05 <Fluidrules> and so on. Maybe this helps someone else. Take care, everybody.

20160413

  • 09:19:07 <de_macrocom> Hello. I still can't pass arguments to a flux-enabled controller action. And I can't see any reason why it doesn't work. Any help?
  • 09:19:20 <de_macrocom> http://stackoverflow.com/questions/36505001/how-to-pass-argument-to-controller-action-with-fluidtypo3
  • 09:20:15 <de_macrocom> There you find lots of information about my problem.
  • 11:08:25 <drlimbo> NamelessCoder: i think there is a bug with flux:field.input
  • 11:08:56 <drlimbo> this field, is always marked as "incorrect" until i type some characters, numbers only like 15 doesn't work
  • 11:08:58 <drlimbo> <flux:field.input name="time" label="Slide x Sekunden anzeigen" required="1" default="10" size="2"/>
  • 11:16:04 <drlimbo> damn, also <flux:field.input name="time" required="0" /> doesn't accept "10" as a value
  • 11:16:14 <drlimbo> it needs a char like "10x"
  • 11:20:40 <Fluidrules> Hi room, I'm building a HTML newsletter, and I want the CSS file to be rendered in the page header, if a certain page template is selected. With v:asset I can link to an external file, that works fine, but is there a viewhelper that can render the content of a file into my page header? Example: <style type="text/css">body {font-size:10px}</style>
  • 11:21:29 <Fluidrules> I know how to do it with TS, but I want the included CSS to be determined by the selected FLUID template.

20160414

  • 03:48:37 <mdddz> hi there, I am using option #2 from https://fluidtypo3.org/documentation/templating-manual/templating/provider-extension/configuration-files.html to include my TS Setup and page object config, but it only takes effect when I am logged in.
  • 03:56:24 <de_macrocom> http://stackoverflow.com/questions/36505001/how-to-pass-argument-to-controller-action-with-fluidtypo3
  • 03:56:47 <de_macrocom> Really no ideas?
  • 03:57:21 <de_macrocom> I can't pass arguments to a flux-enabled controller. Is that a bug? Or is it intended behaviour?
  • 04:15:53 <cweiske> de_macrocom, you're asking the same question for days now.
  • 04:16:19 <cweiske> I think it's time for you to dig into flux and follow the function stack, and find out yourself why it does not work
  • 04:21:03 <de_macrocom> Right. I'm asking for days. Because there was not even the slightest reaction on the question. A simple "should work, please inspect yourself" would have been enough.
  • 04:42:23 <cweiske> did you expect that reaction from all of the people in the room?
  • 04:42:39 <cweiske> in irc it's general that only people speak if they think they can contribute something
  • 04:43:05 <cweiske> if all 16 people in here said "I don't know" to every question, noise level would rise considerably
  • 04:43:35 <de_macrocom> I opened an issue on github now and will provide you with any information that I might raise on my way through the flux stack.
  • 04:43:53 <cweiske> ok
  • 04:49:26 <mdddz> hi cweiske, I investigated my problem from before some more.
  • 04:49:51 <mdddz> I am using option 2 from https://fluidtypo3.org/documentation/templating-manual/templating/provider-extension/configuration-files.html
  • 04:50:29 <mdddz> and now my TS included with that method reliably has no effect when I am not logged in
  • 04:51:35 <mdddz> Could it be that the ts is anyhow addes as UserTSConfig instead of 'general' SetupTS?
  • 04:57:54 <cweiske> if it's only when you're not logged in to the backend, it's because you put that in ext_tables.php
  • 04:58:12 <cweiske> ext_tables.php only gets loaded when a backend user is logged in, or rather only in the backend
  • 04:58:29 <cweiske> ext_localconf.php always gets loaded - for backend and frontend accesses
  • 04:59:01 <cweiske> but if you correctly followed option 2 instructions, this should not be the problem
  • 05:00:00 <mdddz> ah, I see. Thank you very much, that was the hint I needed.
  • 05:00:14 <mdddz> It is in fact in ext_tables.php
  • 05:02:52 <mdddz> I just now noted that there is even comments in the documentation telling the file names. Now I feel stupid for not seeing it. Sry to have bothered you with thtat.
  • 05:03:32 <cweiske> sometimes it's the small things that are easily overlooked and have big effects
  • 05:14:20 <Guest|3195> hi guys, I found an Issue: I'm using an FCE with an Input field: <flux:field.input ... when I enter an alpahanumeric string - evertything is fine, when I enter only a Number I get a validation error in the backedn in TYPO3-7.6.5 can someone confirm this behavior ?! TIA
  • 05:14:34 <Guest|3195> hi guys, I found an Issue: I'm using an FCE with an Input field: <flux:field.input ... when I enter an alpahanumeric string - evertything is fine, when I enter only a Number I get a validation error in the backend (in TYPO3-7.6.5) can someone confirm this behavior ?! TIA
  • 05:19:37 <cweiske> how does your flux field attributes look like?
  • 05:19:41 <cweiske> s/does/do/
  • 05:24:08 <Guest|3195> <flux:field.input name="price" label="Preis" />
  • 05:24:37 <Guest|3195> Inside of <flux:form id="stageTeaser" options="{group: 'FCE'}">
  • 05:24:45 <cweiske> that sounds completely fine
  • 05:25:18 <Guest|3195> yes. and it worl before. but since the typo3-update of this week ...
  • 05:30:30 <Guest|3195> its fluidcontent 4.4.0. BTW
  • 07:32:08 <drlimbo> hi there
  • 07:34:32 <drlimbo> is there a way to debug fluidtypo3 errors? i just get an "Oops, an error occurred! Code: 20160414132911e4c0d8ed" in the frontend
  • 07:34:46 <drlimbo> sure i enabled all debug-parameters i found
  • 07:35:00 <drlimbo> cweiske: i think we already talk once about debuging fluid errors, not?
  • 07:35:09 <cweiske> yes
  • 07:35:13 <cweiske> I gave you a link
  • 07:35:32 <cweiske> http://cweiske.de/tagebuch/typo3-cli_dispatch-debugging.htm#conclusion
  • 07:36:32 <drlimbo> yes cweiske i already set debug, displayErrors and devIPmask but i didn't get an error message
  • 07:36:43 <cweiske> no stack trace?
  • 07:36:53 <drlimbo> nope, only "Oops, an error occurred"
  • 07:38:10 <drlimbo> also the "application information" the info-thing on top in typo3-backend shows "Application Context: Production"
  • 07:38:50 <drlimbo> but in install tool under "debug" i enabled debug
  • 07:40:30 <drlimbo> also with same database and same version i can't reproduce the error local
  • 07:44:19 <drlimbo> cweiske: i think it was a different ext version of the fluidtypo3 family
  • 07:44:30 <drlimbo> ah nope, same error =)
  • 07:50:38 <drlimbo> looks like a problem with Typo3 - if i downgrade to 7.6.4 its working well, with 7.6.5 i get an error
  • 07:57:26 <drlimbo> does anyone has an idea?
  • 08:09:40 <NamelessCoder_> cweiske can't thank you enough for all the help you give other users!
  • 12:19:17 <mikemm> hey.. since I updated to 7.6.5 (from 7.6.2) Typo3 does not allow me to save flux:field.input fields with only numbers in (e.g. "123" does not work but "123a" works). anyone else had the same problem?

20160415

20160416

20160417

20160418

  • 04:02:30 <mdddz> hi there
  • 04:03:32 <mdddz> cweiske: the bug (extension TS not loaded when not logged in) is back D:
  • 04:06:52 <mdddz> I thought it was working when I moved the ts include commands to the ext_localconf.php, but this morning, when not logged in, the TS was not applied
  • 04:11:31 <mdddz> I think it has something to do with caching, because when I log out again it still works
  • 04:12:13 <mdddz> at least for some time
  • 09:39:59 <Guest|7781> hi all, after updating TYPO3 from 7.6.4 to 7.6.5 the flux:field.input for setting settings in my fluidpage-template doesn't accept any numerious values. This is a javascript validation-error. Seems that in ...class="form-control t3js-clearable hasDefaultValue"> the part 'type="text"' is missing. Is there any known workaround?
  • 09:41:50 <NamelessCoder> hi Guest|7781 - fix is pending, you can use Flux from github development branch until then
  • 09:47:09 <Guest|7781> Great news, thank's a lot. I love the fedext-stack.
  • 10:07:48 <NamelessCoder> thanks! :)
  • 10:55:10 <grimmcreative> Hello @all. Just forgot it. How can i use the Standard Header Field inside an FCE? just {header} will not work {data.header} too. THANKS
  • 10:56:19 <bjo3rn> grimmcreative {record.header}?
  • 10:58:26 <grimmcreative> YES. Thanks a lot @bjo3rn
  • 10:58:59 <bjo3rn> np. see also https://worksonmymachine.org/blog/custom-rendering-of-default-headlines-in-fluidtypo3
  • 11:00:03 <grimmcreative> thanks, very helpfull article
  • 11:00:23 <grimmcreative> but i like it without markup :D
  • 11:01:22 <bjo3rn> you like it RAW ^^
  • 11:02:18 <grimmcreative> yes :D
  • 11:07:21 <NamelessCoder> hehe hey Max, good to see you :)
  • 11:07:42 <grimmcreative> I think i missed something. All Icons are ok - but when i edit an FCE i get the default-not-found.svg icon. is this normal?
  • 11:08:26 <grimmcreative> Hello Claus :) nice to read you :D
  • 11:12:07 <grimmcreative> Lol funny. The FCE Icon overlaped the core icon
  • 13:49:10 <grimmcreative> This is annoying https://github.com/FluidTYPO3/flux/issues/1064 - ran into the same problem right now

20160419

  • 07:42:55 <drlimbo> good morning
  • 07:43:34 <drlimbo> can someone tell me, why the hell the "Edit Icons in top left corner" are hidden on all my Fluid FCE Elements? screenshot: https://goo.gl/3bw133
  • 07:45:30 <drlimbo> cweiske: maybe you have another good idea?
  • 07:56:03 <drlimbo> noone?
  • 08:04:18 <cweiske> sorry, no
  • 08:07:13 <drlimbo> it looks like, it takes the same icon as defined in flux:form options as icon, after clearing the cache multiple times
  • 08:07:46 <drlimbo> i can show the icon now with <flux:form options="{group: 'Infoscreen', icon:'{f:uri.resource(path:\'Icons/favicon-32x32.png\')}'}
  • 08:08:43 <drlimbo> it works locally, but on the remote hosts f:uri.resource display's a wrong path to the where the icon is stored, it doesn't show the path to the webroot, is there a way to set the web-root somewhere?
  • 09:48:30 <6JTAABJ03> [flux] NamelessCoder pushed 1 new commit to development: https://github.com/FluidTYPO3/flux/commit/fd8a9e955234318a17d8bf0d65f6859b79db577e
  • 09:48:30 <6JTAABJ03> flux/development fd8a9e9 tpinne: [FEATURE] Add showIconTable option to select component (#1121)...
  • 09:48:30 <7YUAASY42> [flux] NamelessCoder closed pull request #1121: [FEATURE] Add showIconTable option to select component (development...showIconTable) https://github.com/FluidTYPO3/flux/pull/1121
  • 14:40:34 <Guest|44952> http://prntscr.com/auadj4
  • 14:40:54 <Guest|44952> any one facing the issue of Nesting sections in container elements sections is not allowed ?

20160420

20160421

  • 02:49:06 <cweiske> What is the "Raw fluid template" page type used for?
  • 02:50:05 <jmverges> cweiske: you can select a fluid file
  • 02:50:16 <jmverges> and thats all I think
  • 02:50:41 <cweiske> ah, so I don't have to register a custom page type and all
  • 02:50:46 <cweiske> from my provider extension
  • 02:50:48 <cweiske> ok
  • 02:51:15 <jmverges> depends what you want
  • 11:35:58 <Lovefluid> Hi everyone, I'm using FSC and a grid widget and I am trying to hide / overwrite rendering of default headers in the frontend. When I set up "tt_content.fluidcontent_content.10 >" it does nothing - the headlines are still being rendered.
  • 11:36:43 <Lovefluid> Why does this work for everyone but me?
  • 11:37:04 <Lovefluid> Newest TER version plus TYPO3 7.6.5
  • 11:45:01 <Lovefluid> Got it. Apparently, this works with <f:layout name="Content"/> but not <f:layout name="ContentCore"/>
  • 11:45:08 <Lovefluid> Thanks / sorry

20160422

20160423

  • 12:07:17 <thierry2> Hi, is it possible to style a page backend layout with: 2 columns
  • 12:08:35 <thierry2> oups, to quick ... I wanted to say: 2 columns, the left one 75%, the right one 25% ? And in the right one, there must be 3 "colPols" under each other. I've tried what's explained on https://fluidtypo3.org/documentation/templating-manual/templating/creating-templates/page-template.html but ...
  • 12:09:23 <thierry2> When I say "column", I speak of it visually: in this case they are 4 "colPos": one on the left, and 3 on the right
  • 13:33:10 <RotesOHM> is anyone here who can help me with fluid pages and a multidomain setup?
  • 13:34:15 <RotesOHM> i created a template extension with builder for each domain
  • 13:36:29 <RotesOHM> but when i open the Page Layouts tab on one of the domain pages i always see all Layouts of all packages, and i cannot find a solution to assign a provider extension to a specific domain tree

20160424

20160425

  • 11:18:07 <fger> hi guys, my flux:form.object entries in a flux:form.section entry in configuration section inside a fluidcontent element dont show up anymore in TYPO3 7.6.5
  • 11:18:38 <fger> upgraded from 6.2 and changed syntaxes accordingly, also adding inherit=0 to all flux:form.object and child tags
  • 11:18:45 <fger> and in flux:form.section
  • 11:19:29 <fger> the debuggerUtility shows, that the child-objects described by flux:form.object are there in the delivered data-set and i can access them in frontend and preview setion
  • 11:19:44 <fger> is this a bug in flux ? no saving involved

20160426

  • 05:52:53 <fresskom1> Hi everyone. May I inquire about the state of fluidcontent in context of v8.0? Has anyone tried it out?
  • 06:49:08 <cweiske> yes, you may inquire
  • 09:38:54 <drlimbo> hi there
  • 09:39:11 <drlimbo> does anyone already used the FAL youtube element with v:media.youtube?
  • 09:41:24 <cweiske> I did nto
  • 09:41:26 <cweiske> not
  • 09:41:43 <drlimbo> oh bad
  • 09:42:30 <drlimbo> if i add a youtube video to FAL, there will the URL (https://www.youtube.com/watch?v=S5ep2vUMJt0) be saved, but the v:media.youtube viewhelper likes to get the Video-ID
  • 09:45:45 <cweiske> I don't think that v:media.youtube was made with the FAL remote source in mind
  • 09:45:51 <drlimbo> looks like =P
  • 09:45:56 <cweiske> or was in vhs before typo3 got youtube link support
  • 09:49:49 <drlimbo> looks like =P and using v:format.replace isn't that nice too =P
  • 13:10:51 <haki> Hi,
  • 13:12:45 <haki> after updating my typo3 from 6.1.7 to 6.2.19 and my fluidcontent from 3.1.0 to 4.0.0 i have some bugs on my page. where can i get a changelog for this versions?
  • 13:21:19 <haki> ter

20160427

  • 03:15:09 <drlimbo> good morning
  • 03:16:38 <drlimbo> is there a way to add some new fields to the flux:field.inline.fal in an FCE? I'd really like to use FAL instead of Sections with Input-File-Fields, but i need another setting for each file =(
  • 04:26:38 <Marc2016> Hi. I'm running into trouble with a flux-FAL-construct, which should allow 999 files, but only allows 100 files (no matter if they are chosen at once or not). Is there any known restriction and how may I allow more than 100 files in a flux-FAL-field?
  • 04:29:34 <cweiske> did you try if you can select more files in e.g. page -> media?
  • 04:39:11 <Marc2016> yes, x-checked this right now. In "Images" I can choose 104 images...
  • 04:39:37 <cweiske> not more?
  • 04:39:48 <cweiske> or did you simply test more than 100?
  • 04:40:00 <Marc2016> I have tested > 100
  • 04:40:24 <cweiske> hm
  • 04:41:59 <Marc2016> in CE "images" I can choose more (tested 5 more right now without problems)
  • 04:42:22 <Marc2016> in the flux CE which is defined as
  • 04:42:23 <Marc2016> <flux:field.inline.fal name="galleryimages" multiple="true" collapseAll="true" maxItems="1000" />
  • 04:42:32 <Marc2016> not more than 100 files are possible,
  • 04:43:03 <cweiske> can you select more, and only 100 are saved, or does the "select" button disappear after the 100st?
  • 04:43:21 <Marc2016> I can select more than 100, but only 100 are saved.
  • 04:43:39 <Marc2016> Also, when I choose 99 and than 5 more -> 100 files are saved.
  • 04:43:47 <cweiske> ah
  • 04:44:45 <Marc2016> any idea how to debug this?
  • 04:46:37 <cweiske> i'd look into flux' FalViewHelper.php and check which configuration is actually used in getComponent
  • 04:47:34 <Marc2016> ok, thanks. I'll go digging... :-)
  • 04:52:04 <cweiske> maybe the 100 limit is in there somehow
  • 04:53:13 <Marc2016> there is no maxItems-configuration at all. I'll try to add it, waiting for a proper dev system to test this out...
  • 04:55:38 <cweiske> in falviewhelper::getComponent(), just before the return $component, add a var_dump($component). do you see a maxItems in the output?
  • 04:57:27 <Marc2016> I'll try this as soon I have a dev system to play with. :)
  • 04:57:47 <cweiske> the maxitems configuration comes from a parent class
  • 05:14:51 <drlimbo> is there a way to add some new fields to the flux:field.inline.fal in an FCE? I'd really like to use FAL instead of Sections with Input-File-Fields, but i need another setting for each file like "show Title on left or right" =(
  • 05:15:42 <cweiske> I doubt that
  • 07:26:19 <cweiske> how can I make a page selection field in flux?
  • 07:31:21 <drlimbo> page selection cweiske?
  • 07:31:32 <drlimbo> input field with link wizzard and page tab choosen?
  • 07:33:12 <cweiske> no, not an input field
  • 07:33:27 <cweiske> more https://docs.typo3.org/typo3cms/TCAReference/Reference/Columns/Group/Index.html#type-group
  • 07:34:22 <drlimbo> ah, i dont know.. i just used the method i just mentioned, but im also interested in a solution =)
  • 07:47:23 <cweiske> flux:field.relation http://fotos.cweiske.de/screenshots/2016-04-27%20flux%20field.relation.png
  • 07:47:34 <cweiske> that displays all pages in a dropdown, which is not usable for large pages
  • 08:01:51 <fresskoma_> Hi everyone. Does fluidcontent/fluidpages influence the copying/pasting behaviour of TYPO3 in any way? I’m having a weird problem where the content elements I’m trying to copy are indeed copied, but _also_ moved to the location where the element is copied to ~.~
  • 08:01:51 <cweiske> what I want is this: http://fotos.cweiske.de/screenshots/2016-04-27%20typo3%20select%20page.png
  • 08:03:07 <cweiske> which is a group type
  • 08:03:10 <cweiske> which flux does not have
  • 08:18:12 <BjoernP> hey
  • 09:35:51 <drlimbo> hi there
  • 09:37:07 <drlimbo> i'd like to position some bullets on an image in an FCE, is there a way to display an Image in Backend AND visually select some points (coordinates) to display the Bullets?
  • 15:32:07 <haki> Hi, i really could need the changelog from 3.1.0 to 4.0.0. Can someone help me?
  • 15:50:48 <haki> is it possible that {data.header} does not work with 4.0.0?
  • 16:21:11 <haki> no one?

20160428

  • 07:59:51 <s-andersen> Hi, I have made a theme with flux,fluidpages and vhs. In the "Page Configuration" the editor can choose a logo for the website, and a background image, field.file viewhelpers. The images inherited from the frontpage, but for some reason the inheritance doesn't work right, which leads to broken images in the frontend. Does anyone have an idea what's
  • 07:59:51 <s-andersen> wrong here?
  • 08:12:59 <cweiske> you cannot use fal fields in page configuration; that's broken typo3-wise
  • 08:14:18 <cweiske> see https://github.com/FluidTYPO3/fluidpages/issues/228
  • 08:20:32 <s-andersen> cweiske: I'm not using flux:field.inline.fal, I'm using flux:field.file, is that affected by the same bug?
  • 10:16:28 <cweiske> i have no idea s-andersen

20160429

  • 05:14:00 <fresskom1_> Hmm, does css_styled_content still have to be installed when using fluidcontent? When uninstalling it, I can’t get any content elements to render.
  • 05:30:37 <x3ro> Hmm, never mind me. This seems to have been caused by the wrong TypoScript includes being set in the root template /o\
  • 05:37:12 <x3ro> NamelessCoder: Regarding https://github.com/FluidTYPO3/flux/pull/1126 – I’m doing some work with fluidcontent at the moment, and it seems like we’ll be switching to it for future projects. So I definitely have an interest in contributing :D I find that its documentation is much better than for most other TYPO3 related projects (kudos).
  • 07:21:02 <Guest55270> Hello, I try to use <flux:form.option.translation> in a page layout. I added a field <flux:field.input name="settings.subtitle" label="Seiten-Untertitel" enabled="1" inherit="1" inheritEmpty="1" />, which works in standard page settings. There I can enter values in tab "Page configuration". But in language specific page settings, this tab is comple
  • 07:21:02 <Guest55270> tely missing. Any hints?
  • 07:21:21 <Guest55270> Btw: I use 7.6.6 with actual extension versions from TER
  • 07:30:34 <Guest55270> Ufff... https://fluidtypo3.org/blog/news/flux-option-translation-and-typo3-76-lts.html
  • 07:33:54 <Guest55270> I installed compatibility6, but I still get the same behaviour.
  • 09:07:24 <NamelessCoder> sounds good x3ro - looking forward to it, and thanks for the contributions so far!
  • 09:37:35 <x3ro> NamelessCoder: I’d still like to start a discussion of how to best document flux in context of fluidcontent, though :D wouldn’t this best be done in a github issue?
  • 09:38:28 <x3ro> Because I feel that right now it is somewhat lacking, I suppose due to the issue of keeping the Flux documentation clean of references to fluidcontent
  • 09:41:45 <NamelessCoder> we can discuss it briefly here then follow up with a github issue - just to avoid having to cover more than necessary in the github issue
  • 09:42:13 <NamelessCoder> it is indeed lacking and speaking of viewhelper docs it is lacking for the reason you describe
  • 09:44:05 <NamelessCoder> I've been thinking about how to solve that one and the only sensible solution I can think of (until this point) is some sort of pingback tracking where we are able to link internal doc resources that link *TO* docs. So we can track that for example fluidcontent's docs about icons links to flux's icon viewhelper docs, but without having to include that information in flux itself (because there it will inevitably become outdated or wrong at some
  • 09:44:05 <NamelessCoder> point, or we risk documenting dozens of extensions via flux)
  • 09:45:01 <NamelessCoder> (that pattern would apply quite well to other viewhelpers too, if I'm not mistaken - tracking all doc places that link to a VH doc)
  • 09:45:17 <x3ro> Sounds sensible
  • 09:45:29 <NamelessCoder> challenges in that regard would be that we document every version and won't necessarily know if/how something applies to previous versions
  • 09:45:33 <x3ro> That would be done in the typo3 that powers fluidtypo3.org?
  • 09:46:09 <NamelessCoder> yes that would be part of the docs rendering, likely achieved with a custom template + VH for schemaker's FE plugin
  • 09:46:50 <NamelessCoder> we could design a rule that says, for example, "VH links in docs are ALWAYS to 'master' version of any VH"
  • 09:47:46 <NamelessCoder> so our docs only link to master VH refs but VH refs link back to that resource from every version of VH refs
  • 09:49:36 <NamelessCoder> few things would need to happen for that to be a good approach... most importantly we'd need to add the VH doc links in various documentation that gets rendered on fluidtypo3.org. A plain "these viewhelpers are used in this example: <markdown-list>" would suffice, imho.
  • 09:51:26 <NamelessCoder> there's more, actually... we could parse out example blocks when displayed in docs and parse as Fluid (not render, just parse) where possible, extracting viewhelpers that are used (see live fluid example on site for how that works) and listing those. But that doesn't have to be there for it to work initially
  • 09:52:15 <x3ro> So, lets say I’m looking at the Flux\Form\Option\GroupViewHelper. That page would contain the list you’re speaking of, linking to where the GroupViewHelper is used in the fluidcontent docs?
  • 09:52:24 <x3ro> Just to make sure I understand you correctly :D
  • 09:52:33 <NamelessCoder> this makes the relationships between VH docs and other docs more human friendly, I think. But it doesn't really solve the other problem, that our current structure is a bit hard on the brain
  • 09:53:08 <NamelessCoder> yep, exactly - when looking at any VH you would also get a list of all places in other docs where that VH is used (read: where there is a link to that VH)
  • 09:53:28 <NamelessCoder> basic pingback/trackback logic
  • 09:53:40 <NamelessCoder> but filtering so it only shows "official" resources
  • 09:53:46 <x3ro> What about allowing to actually provide documentation for Flux in Fluidcontent?
  • 09:54:05 <x3ro> I.e. having a docs/ folder or something, that allows me to document Form / Option / GroupViewHelper
  • 09:54:13 <NamelessCoder> should be solved by linking to docs in Flux or Flux VH refs
  • 09:54:16 <x3ro> from within fluidcontent, w/ a simple markdown file
  • 09:54:31 <x3ro> hmm
  • 09:54:50 <x3ro> I’m just trying to figure out where I would put those docs that link to Flux
  • 09:55:09 <NamelessCoder> it's fine to document how Flux components work in each other extension, but the main docs should be in Flux. E.g. you can explain how "group" renders this and that type of field, but don't begin to list supported arguments and perspectives about how it renders as TCA - that's a job for Flux docs
  • 09:56:41 <x3ro> Yeah, I think I get that. But lets take https://github.com/FluidTYPO3/flux/pull/1126 as an example. Lets say the mechanism that links references in the Flux docs is in place, and I would put the documentation from the PR in fluidcontent instead. Where would that be?
  • 09:56:48 <NamelessCoder> my vision is a set of docs that explain exactly how Flux works in details - without using fluidcontent etc. as examples. It does make sense as a general library for integration even when you don't use any of the other exts and I think that fact tends to get missed.
  • 09:56:51 <x3ro> that is, where in fluidcontent would I put the stuff I’ve written there? :D
  • 09:57:25 <NamelessCoder> if that existed it would be pretty easy to write the fluidcontent/fluidpages docs because it would mostly be about explaining how those patterns apply in that extension
  • 09:58:20 <NamelessCoder> re: your question, currently fluidcontent etc. has no viewhelpers which means you can't put it in viewhelper docs. The only place it can be put currently is in the "documentation" repository that gets rendered as a page tree on the site
  • 09:59:25 <NamelessCoder> but that's not optimal and that's my point... this central documentation seems to be a pretty bad idea unless it's to write guides about how to use the framework as a whole. Individual guides should be in each extension's docs, probably. With relationships to Flux docs when there is a relation.
  • 09:59:55 <NamelessCoder> we've had some efforts in that direction but it's a seriously tough job
  • 10:00:36 <NamelessCoder> (gotta go in around 10 minutes, pre-warning :))
  • 10:01:54 <x3ro> yeah, I guess its nothing that’ll be done in a day. I’ll give it some thought as well. one more question. you’ve mentioned schemaker, and I did get it running locally after some trouble w/ vhs versions. Is the stuff rendered at https://fluidtypo3.org/viewhelpers.html done by schemaker, or is that something else?
  • 10:02:20 <NamelessCoder> that's all schemaker
  • 10:02:38 <NamelessCoder> for your own projects I'm guessing enabling the BE module is a lot easier
  • 10:02:50 <NamelessCoder> FE output is based on XSD files, BE will read from installed classes
  • 10:03:09 <NamelessCoder> (that's the only way we can render multiple versions in FE - not consulting the classes)
  • 10:03:20 <x3ro> Ah, that explains it :D
  • 10:03:47 <NamelessCoder> we're only limited by PHP in this regard :)
  • 10:05:26 <x3ro> I think I’ll take another look at schemaker and maybe play around a bit. I’ll also try to summarize this discussion in a GitHub issue. Would that go in Flux?
  • 10:05:31 <x3ro> or elsewhere
  • 10:05:42 <NamelessCoder> to sum things up from my end, I'd aim for the following:
  • 10:06:18 <NamelessCoder> 1 - independent Flux docs that can be read as a beginner (without requisite TCA knowledge) but with links to official resources to make it clear that Flux *IS* primarily a shell for TCA/TCEForms
  • 10:06:56 <NamelessCoder> 2 - independent tutorial-style docs for each extension (fluidpages, fluidcontent etc.) to show how those work, without explaining Flux in detail - but linking to the Flux docs from step one
  • 10:07:16 <NamelessCoder> 3 - manual or automatic extraction of "trackback" links from docs to VH refs
  • 10:07:48 <NamelessCoder> 4 - refitting fluidtypo3.org docs section to reflect the divided docs - where now it's more of one big pile
  • 10:08:14 <x3ro> Is the thing that renders the templating manual also in schemaker?
  • 10:08:22 <NamelessCoder> I guess that's several weeks of work, depending on how fast one can type and how much one has ready in memory
  • 10:08:37 <NamelessCoder> no, that's part of the fluidtypo3org extension (github repo)
  • 10:08:40 <x3ro> yeah, but it doesn’t have to be one big “whoop"
  • 10:08:51 <x3ro> step by step is also an option, I suppose
  • 10:08:56 <NamelessCoder> definitely not and that's a good thing - each step can be done by its own
  • 10:09:12 <NamelessCoder> but it won't be the golden solution until all is in place
  • 10:09:25 <x3ro> :D
  • 10:10:05 <NamelessCoder> if that's something you want to tackle we'll support you every way we can. We've no budget this year :/
  • 10:10:58 <x3ro> Yeah, I’ll check w/ my employer as well. I certainly wont get time to work on this full time, but lets see what can be done :)
  • 10:11:24 <NamelessCoder> we also had InvisibleKind writing something (higher level tutorial style) that might be good as a replacement for the current big pile and then complemented by the individual ext tutorials
  • 10:11:36 <NamelessCoder> it's along the lines of "how to use the framework, for beginners"
  • 10:12:08 <x3ro> Well, the current templating manual is not bad, even though it could benefit from a little work
  • 10:12:26 <NamelessCoder> fingers crossed you can get some time for this ;) if you do we can invite you into the team and you/co can use that as reference
  • 10:12:45 <NamelessCoder> not much else we can offer except of course the knowledge ;)
  • 10:12:49 <x3ro> :D
  • 10:13:03 <x3ro> Well, that’s pretty valuable as well ;)
  • 10:13:26 <x3ro> I’ll see what I can do. Talk to you soon, I guess :D
  • 10:13:33 <NamelessCoder> hehe indeed it is, with a bag full of fluidtypo3 knowledge you can prototype like a madman
  • 10:13:51 <NamelessCoder> spewing out new sites left and right
  • 10:14:13 <NamelessCoder> alrighty, it's weekend time! Got people coming over so there's a bit of prep. Have a nice one!
  • 10:14:25 <x3ro> likewise :) have a nice weekend
  • 10:30:59 <Guest|19175> hi, i get the error "
  • 10:31:00 <Guest|19175> Fatal error: Call to a member function resolvePrimaryConfigurationProvider() on a non-object in /kunden/123103_73765/rp-hosting/5007132/6007132/typo3cms/cm4all_live/public_html/typo3conf/ext/flux/Classes/Service/FluxService.php on line 363" with the newsest fluidcontent for 6.2.
  • 15:58:20 <Guest|3161> hi, after updating fluid content i get a problem with this line: class Tx_CmagWebsite_Controller_ContentController extends Tx_Fluidcontent_Controller_AbstractContentController {
  • 15:58:26 <Guest|3161> was replaced?

20160430