05:13:06 <fmo> Hello. What is the best way to add/change/remove fields from the Configuration section of an existing template ?
05:13:16 <fmo> For example, in the extension fluidcontent_youtube, how to add new fields related to the video ?
05:13:33 <fmo> For the moment, I changed the template path and use my own template, but I guess it's not a good solution.
05:14:13 <fmo> I'd like to know if there is some kind of inheritance and solutions to add new fields and keep the existing ones
10:11:29 <jost> In EXT:vhs why does the "v:iterator.sort"-ViewHelper sort by *key*, not by value?
10:12:33 <SvenDeKa> hi folks, I have a little pain with v:render template when using a f:form inside of the included template.
10:13:35 <SvenDeKa> it is that the _refferer-Parameters stay empty and therefore run into an error in 6.2
10:14:12 <SvenDeKa> (Could not analyse class:TYPO3\\Controller\StandardController)
10:14:47 <SvenDeKa> is there a way to make the included template aware who/what called it?
10:17:19 <SvenDeKa> I use v:render inside of an extension like this: <v:render.template file="fileadmin/furtherPath/template.html" variables="{_all}"/>
10:22:00 <NamelessCoder> SvenDeKa f:form requires a proper controller context and request - you may want to try https://fluidtypo3.org/viewhelpers/vhs/master/Render/RequestViewHelper.html if you are trying to call an Extbase controller
10:26:09 <SvenDeKa> @NamelessCoder, that sound very much like it. ill try. THX!
10:41:48 <SvenDeKa> sweet! thanks to all developers of that nice flux- and vhs-stuff! Rock on!
11:11:09 <wagner51|32389> hi all. Do you know how to chain a VHS uri.request with a VHS format.url.encode ?
02:31:37 <pRiMU5> can any1 help me with a multilanguage issue? i have created a fce with an inline.fal element. everything works fine so far in default language. but when i translate a page and copy the default elements to the new created language, fedext is not saving the sys_language_uid to the fal in the sys_file_reference table. so i am not able to get the meta information of the translated relation.
05:19:16 <JohPie> I use TYPO3 6.2.10, flux 7.1.2, fluidpages 3.1.2 and fluidcontent 4.1.1
06:16:55 <s-andersen> I have a single page in a pagetree, where the backend layout will simply not render, FE is fine. List module works fine. Even if I disable all content elements, there's no success. What can be the cause of this behavior?
06:33:48 <tv_sebastian> Hi guys. Is there an approx date for the 7.2 release because of the support of 7.x ?
07:00:38 <deffcon_> hey guys. i migrated FCEs from FED to fluidcontent DCEs. backend preview shows me that it got the new definitions. but if i try to edit or look in frontend i get "INVALID VALUE("fed_fce") and "Content Element type "fed_fce" has no rendering definition!".
07:00:55 <deffcon_> the tt_content entries have still "CType" "fed_fce"
07:01:40 <NamelessCoder> run the EM upgrade script for fluidcontent, that should correct your CType entries
07:03:18 <deffcon_> sadly it gave following output "0 rows have been updated"
07:05:01 <NamelessCoder> should work - https://github.com/FluidTYPO3/fluidcontent/blob/development/class.ext_update.php#L21
07:05:26 <NamelessCoder> last changed some six months ago (to also clear caches)
07:09:36 <Idleworks> i have several provider extension within a typo3 installation. each extension serves one page tree. is it possible to set content and page elements from flux to one page tree? at the moment I have one tab (group) for each extension. but that means an editor can select element of another page tree
07:10:00 <deffcon_> was the same script. tough it showed 0 rows affected the fed_fce CTypes are replaced by fluidcontent_content
07:14:05 <NamelessCoder> Idleworks see https://github.com/FluidTYPO3/flux/issues/747 - work in progress
07:19:59 <NamelessCoder> deffcon_ yep, was the order of SQL queries. This commit just now fixes that. It still worked, just reported wrong.
07:20:57 <NamelessCoder> thanks for finding the bug ;)
07:22:45 <Idleworks> NamelessCoder thanks for the hint
07:23:14 <NamelessCoder> Idleworks e.t.a probably some time during the weekend - need to get this week over first.
07:24:08 <NamelessCoder> and after the change you'll be able to override anything, not just enabled/disabled state, through TS.
07:24:47 <flyingfish> I have added extentions: fluidpages,fluidcontent,vhs,flux
07:24:47 <flyingfish> after that i have created an extension with extension builder
07:24:47 <flyingfish> after that i have added: \TYPO3\CMS\Core\Utility\ExtensionManagementUtility::addStaticFile($_EXTKEY, 'Configuration/TypoScript', 'myextension_ext'); in ext_tables.php
07:24:47 <flyingfish> in ext_localconf.php i've added:
07:24:47 <flyingfish> After that i have set templateRoot, layoutRoot, partialRoot in setup.txt which is set up in template setup.
07:24:48 <flyingfish> After that I have added Foo.html in template and the other foo.html in layouts )like suggested on this sites tutorial)
07:24:48 <flyingfish> In page->edit->Page Layouts i got one option which i have selected.
07:24:49 <flyingfish> now i get an error: Could not analyse class:flux\ViewHelpers\FormViewHelper maybe not loaded or no autoloader?
07:24:49 <flyingfish> What did I miss/do wrong/forgot?
07:25:53 <NamelessCoder> flyingfish you probably forgot to add the "flux" namespace in one or more of your templates
07:26:30 <NamelessCoder> or you set it to a legacy value of Tx_Flux_ViewHelpers which should be FluidTYPO3\Flux\ViewHelpers now
07:27:55 <NamelessCoder> if you use xmlns:flux, the correct namespace is http://typo3.org/ns/FluidTYPO3/Flux/ViewHelpers
07:31:24 <flyingfish> hmm..i have changed now from: xmlns:flux="http://typo3.org/ns/flux/ViewHelpers" to xmlns:flux="http://typo3.org/ns/FluidTYPO3" and its still the same
07:52:28 <NamelessCoder> AlexN if it's about vhs, flux, fluidcontent, fluidpages, fluidcontent_core... then you've come to the right place
07:55:31 <AlexN> Glad to hear that :) Well, I assign domain models in my controller to fluid but I cannot access the functions. I currently have a workaround using magical getter. Is it a mistake by myself or simply not possible to access model functions in fluid?
07:57:21 <NamelessCoder> that's maybe a bit of a broad question. First of all: Fluid uses the ObjectAccess object to access values and this method supports all recognised getters on model instances
07:57:47 <NamelessCoder> so the problem in this case sounds more like you're going outside the pattern of recognised getters - you shouldn't do that.
07:58:24 <NamelessCoder> that being said: there are ways to achieve the result you want also with custom getters but without magic methods which you definitely should consider avoiding.
07:58:46 <NamelessCoder> 1) let your domain objects implement ArrayAccess. ObjectAccess will recognise this and attempt access as array.
07:59:12 <NamelessCoder> 2) Use v:call on your model instance to call unrecognised methods - but consider 1) first and foremost.
08:02:00 <AlexN> Yeah, I agree with you. Magical getters aren't the best way to do. I will research the points you mentioned and come back if I have further questions regarding fluid :) For now you did me good tips. Thanks ! :)
08:55:36 <Guest|78812> Hey! can someone help me exploting a string with fluid?
08:56:21 <Guest|78812> Here is what i tried: <v:iterator.explode content="test,test2,test3" glue="," as="var" /> ... debug return NULL :/
08:59:27 <Akii> try using the inline annotation if available
09:00:04 <Akii> otherwise make sure to use the scope properly: <v:iterator.explode ...>{var -> f:debug()}</v:iterator.explode>
09:00:41 <Akii> *inline + v:var.set (or whatever the new VH is called)
09:03:31 <AlexN> NamelessCoder? Do you have link where "domain objects implement ArrayAccess" is explained.
09:06:02 <Guest|78812> inline isnt available i've tried this syntax: <v:iterator.explode content="test,test3,test5" glue="," as="var">{var -> f:debug()}</v:iterator.explode> but its still returning NULL
09:10:13 <AlexN> Okay, I've found out... one has to write the function name without "get" as prefix.
10:07:57 <Idleworks> @NamelessCoder I have a weird problem with flux and typo3 >= 6.2.9
10:08:33 <Idleworks> somehow caching is completely turned off
10:09:30 <Idleworks> when I deinstall provider ext and fluidpages, caching is ok
11:18:38 <NamelessCoder> go right ahead guys - give that one a try on 7.1 ;)
12:13:43 <Guest|48683> Hey guys, I use fluidcontent 4.1.1 with vhs 2.2.0 and got a strange problem. If I use the v:uri.typolink viewhelper the new content element rendering for this FCE breaks
12:15:49 <Guest|48683> There is a broken image for the icon visible and no text from the language files are visible
12:16:06 <Guest|48683> If I remove the viewhelper everything works fine...
12:16:51 <NamelessCoder> Guest|48683 maybe you forgot to include the "v" namespace in the template
12:17:14 <Guest|48683> I include this {namespace v=Tx_Vhs_ViewHelpers}
12:17:30 <Guest|48683> Shouldn't that be sufficient?
12:17:57 <NamelessCoder> you'll need {namespace v=FluidTYPO3\Vhs\ViewHelpers} for VHS 2.2+
14:51:11 <s-andersen> Hi, I load jQuery with vhs assets handling, loaded in the footer. Now I need to add some inline javascript from an extension below the file generated by vhs. But how do I accomplish this?
14:55:15 <NamelessCoder> s-andersen give your jQuery inclusion a name property and add that in "dependencies" in the asset block you put your inline JS into
14:55:48 <NamelessCoder> that will make the rendering order irrelevant so you can make sure it comes in the right order always
15:06:59 <s-andersen> NamelessCoder: That works great! Now I have three different places I need to add code to the same file. Can I just chain three createFromContent() right after each other and call finalize just before the end of the extension?
15:10:11 <NamelessCoder> not really - if you mean chaining as in fluid syntax (that doesn't make much sense with assets). But yes, you can have three assets depend on each other in a sequence
15:13:35 <s-andersen> NamelessCoder: I do this: $this->asset->createFromContent($this->productDeleted($uid))->setType('js')->setDependencies('jquery')->setStandalone(FALSE)->finalize();
15:14:04 <s-andersen> I need to do it three times. Should I make three separate instances instead of setting $this->asset
15:15:14 <NamelessCoder> you need to have three of those statements then
15:15:30 <NamelessCoder> chaining returns the same instance over and over; you need three seperate instances here.
15:20:56 <s-andersen> NamelessCoder: This is just great. I'm converting an old pibase extension which I didn't make. I feared it would be a pain to stick to conventions of having JS in the footer, but VHS really makes it a breeze
15:21:43 <NamelessCoder> you can also add them as TS if you like - same property names etc.
15:22:02 <NamelessCoder> direct php is the most efficient of course
15:22:59 <s-andersen> NamelessCoder: We already do most of the scripts via TS, but this inline JS required some dynamically inserted productnames and properties from PHP.
15:23:44 <NamelessCoder> hehe yep, this is the whole point of having all three APIs supported :)
15:24:36 <s-andersen> And this is where you deserve a lot of credit. I needed to solve a specific problem, and decided to browse the code to see what you had done, and because it was so well documented I figured that what I already did in TS was possible to do in PHP, even from a non-extbase extension.
15:26:16 <NamelessCoder> the hard part is usually finding out which tool you need, because there are so many small use cases
15:28:15 <s-andersen> Exactly, and I guess that is an issue for everyone, not only for people using FluidTYPO3, but even someone starting with TYPO3 will ask "What do I do to create a template", and there will be several possibilities, most of them outdated.
09:49:55 <Kaimane> Using {v:iterator.filter(subject: '{Vehicle.Equipments}', filter: '3', propertyName: 'CategoryId')} but output is still "Array". My goal is to get all items of {Vehicle.Equipments} where CategoryId is 3: {Vehicle.Equipments.x.CategoryId}. But why do I get "Array"?`
09:56:36 <NamelessCoder> Kaimane what would you expect f:iterator.filter to return, if not a filtered version of the input array? If you try to output an array directly in Fluid, it will just write "Array"
09:58:42 <Kaimane> NamelessCoder: I expect a filtered version ;-) But how to work with that output "Array"?
09:58:43 <NamelessCoder> you have to use that expression somewhere that an array is expected, like in <f:for each="{array -> v:iterator.filter(...)}">
10:00:13 <NamelessCoder> and you can of course <f:debug> it. But outputting it as a string will not work.
10:00:46 <Kaimane> Namelesscoder: <f:debug> does not work. It also outputs "array".
10:01:27 <NamelessCoder> then you have some spaces around the value
10:02:17 <NamelessCoder> <f:debug>{variable}</f:debug> debugs {variable. <f:debug>{variable} </f:debug> debugs {variable} as cast to a TextNode inside f:debug because it has text.
10:02:48 <Kaimane> Okay. My fault. That does the trick: {v:iterator.filter(subject: '{Vehicle.Equipments}', filter: '3', propertyName: 'CategoryId') -> f:debug()}
10:03:25 <NamelessCoder> your ideal expression, following all rules, might look like: {vehicle.equipments -> v:iterator.filter(filter: '3', propertyName: 'CategoryId') -> f:debug()}. Your variables are a bit oddly named
10:03:47 <NamelessCoder> and by the way you never need to do '{variable}' *especially* when the variable is not a string.
10:04:17 <NamelessCoder> {v:iterator(subject: vehicle.equipments)} is the same but does not try to create an additional TextNode
10:31:49 <Kaimane> NamelessCoder: Thank you very much for your support. Now it works as expected!
10:33:57 <Kaimane> But there is another question: I use <f:alias map="{categories: {1: 'Kategorie 1', 2: 'Kategorie 2', 3: 'Kategorie 3'}}"></f:alias> and would like to output {categories.{i.cycle}} within the <f:alias> tag but fluid does not render the string. How to use an interator within a variable?
10:35:46 <NamelessCoder> check the "Dynamic variable access" example on https://fluidtypo3.org/library/try-fluid-now.html
11:03:39 <Kaimane> NamelessCoder: Okay, I have to use <v:variable.get/>. Works like a charm ;-)
11:07:13 <Kaimane> Third and last question for today ... Is there a possibility to check if an array is empty? <f:if> does not the trick if the condition is {array} == ''. <f:debug> prints array(empty).
11:10:39 <NamelessCoder> that's the most efficient way you can check any array/iterator ;)
11:23:46 <Denyerec> NamelessCoder, if I want to checkout an extension based on its tag it's "git checkout 3.0.0" right ?
11:24:05 <Denyerec> This gives the me "You are in detatched HEAD" state, but that's OK if I'm just consuming the extension and not developing it, right ?
11:26:38 <NamelessCoder> if you have all the tags locally then yep. However, it should create a new branch for you - so I think you may not have all the tags
03:37:13 <drlimbo> is there a know issue with <v:page.menu> an multiple languages? <v:page.menu> doesn't care about the language until im looping manually thour every element and add additionalParams="{L: '{v:page.language()}'}"
04:12:37 <ndee> hey guys, I pulled the newest "development" version of vhs and I'm getting following syntax error: syntax error, unexpected T_USE, expecting T_FUNCTION in typo3conf/ext/vhs/Classes/ViewHelpers/Resource/Record/AbstractRecordResourceViewHelper.php on line 24 . Looks like it's related to this commit: https://github.com/FluidTYPO3/vhs/commit/0630c1a685b36b3bf799220a8e06b9c57ccadefe Anyone encountered that problem as well? I'm running ubuntu 12.04
04:24:01 <ndee> just saw the "Raise PHP requirement to 5.4" commit
04:35:53 <FraSpe> I have a problem with the rte in my fluidcontent elements. The links are inserted in the format <a href="http://xxxx.yz/?id=21" class="internal-link">link</a>, so realurl isn't working. Using the standard text-element, all the links are fine. Any ideas?
05:11:30 <drlimbo> is there a know issue with <v:page.menu> an multiple languages? <v:page.menu> doesn't care about the language until im looping manually thour every element and add additionalParams="{L: '{v:page.language()}'}" ?
08:26:13 <drlimbo> is there a way to use multiple "plugin.tx_ogbase.view.templateRootPath"?
08:47:33 <sik> hi everybody. if i use f:image with the latest fluid version and add "c" to width AND height the image is not being processed. if i only use on "c" it is handled. how can i achieve cropping on both - width and height?
08:58:25 <sik> it was buggy with GraphicsMagick. i now switched to im6 and it works with both c's
09:46:26 <drlimbo> IS ist possible to use <flux:grid.column> and ALLOW/DISALLOW Fluidcontent-Elements based on the GROUP? Not every single File like yourextensionkey:HeaderSlideshow.html?
09:46:52 <drlimbo> NamelessCoder:i think we already talked about the "allowedContentTypes" once
15:38:15 <Outdoorsman> I'm just curious if anyone knows what the status is on fluidbootstraptheme? There hasn't been any activity on it since pretty much last year.
17:17:36 <Outdoorsman> xaver do you know what the status is with fluidbootstraptheme?
17:18:21 <Outdoorsman> Here's the history... https://github.com/bootstraptheme-for-typo3/fluidbootstraptheme/graphs/contributors
18:06:40 <NamelessCoder> Outdoorsman anything in particular you miss? I tested, and the package still works with Flux 7.2 etc. so an update is not required as such ;)
09:25:56 <ndee> @cedricziel: do you know a way on how to override a locallang file from an extension? e.g.: add an additional locallang path
09:26:19 <cedricziel> typoscript maybe, but that's just a guess
09:59:37 <benjamin_654> @ndee i used this: $GLOBALS['TYPO3_CONF_VARS']['SYS']['locallangXMLOverride']['EXT:news/Resources/Private/Language/locallang.xml'][] = 'EXT:myext/Resources/Private/Language/locallang.xml';
10:02:43 <benjamin_654> @ndee or you pass the extension name directely to the v:l view helper: <v:l extensionName="MyExtension" id="page.edit.button.label.show" default="Show" />
11:54:12 <Guest|97463> Hi! TYPO3 CMS 7.1 and newest development branches of fluidtypo3-Extensions ... the page layout is not working correctly; it works if I choose the layout for subpages, but not the "this page"-template. Anyone having this issue, too?
10:53:19 <bronco> i have a problem that a variable in my own created fluid content element isn'nt replaced - it's inside a javascript code with a pair of brackets around and i guess the brackets are the problem, how can i escape them? anyone an idea?
15:00:24 <apiening> I use the fluidbootstraptheme extension but none of the content templates gets rendered, only the h1 headings… no matter what content element I pick.
15:06:01 <apiening> The extension uses flux, vhs and fluidconteent to render the content. I don't get any error messages or warnings in the apache log.
15:06:15 <apiening> Can someone give me a hint how I could track this down?
17:51:22 <apiening> Has someone successfully used the fluidbootstraptheme extension? I'm especially interested in the bootstrap content elements but I get no content rendered in my frontend other than the heading.
07:50:19 <LuJakob> Hello. I have a question regarding Fluidcontent Elements rendering in backend module with $this->contentObject->RECORDS. I can render fluidcontent fce's in frontend like this, but not in backend. i get a typo3 exception: The default controller for extension "Fluidcontent" and plugin "Content" can not be determined. Please check for TYPO3\CMS\Extbas
07:50:19 <LuJakob> e\Utility\ExtensionUtility::configurePlugin() in your ext_localconf.php
07:50:54 <LuJakob> does anybody in here know a solution to this ? and maybe explain why this is not working. THNKS
07:51:52 <LuJakob> i can render normal content elements like this in frontend and backend, but not fluidcontent elements ...
09:08:22 <pedda> this does not work ExtensionManagementUtility::addToAllTCAtypes('tx_news_domain_model_news', 'field1,field2,field,field4', 'after:tx_roqnewsevent_location');
09:14:15 <pedda> i was playing around with this a few weeks ago already, while trying to place a field right after a pallette which wasn't working either
09:15:57 <pedda> it seems as if i need to proceed with some hacky preg_replace approach on the showitem string
09:21:01 <drlimbo> im try'n to debug with <f:debug> - but only the debug-styles (CSS) in head will be loaded and <body> is empty
09:34:17 <pedda> @LuJakob FYI: i solved my issue via setting dependencies in ext_emconf.php of my extension to depend on news and roq_newsevent, as loading order still matters
09:34:54 <LuJakob> excellent. thanks for telling me :-)
11:49:06 <NamelessCoder> if someone doesn't stop me before ~21:00 I'll release VHS 2.3.0 - I assume most of you are already using branch:development and have fixed/reported any problems with it, but if you want to get a last test in on branch:staging, now is the time
12:21:55 <Guest|41590> Hi Everyone. I am having a go a fluidcontent_core. I would like to use the overlays function to just replace one template. I cant seem to to get this to work. I have a new Text.html template stored in EXT:my_ext/Resources/Private/Templates/ContentCore How can i use this template?
12:32:37 <NamelessCoder> Guest|41590 if you're using Flux from development branch: https://fluidtypo3.org/blog/news/coming-changes-in-flux-72.html second section, also works for fluidcontent_core. If you're using Flux from TER, the answer is in https://github.com/FluidTYPO3/fluidcontent_core#concept-variants (but in this case you may want to wait for Flux 7.2 or switch to development now, because your use case is not exactly suited for variants which is the only current
12:32:37 <NamelessCoder> option). Very last option: copy all template files and change templateRootPath like you know from legacy.
12:34:24 <Guest|41590> i think ill go with copying all the templates. Seems more straight forward. I can revisit this again when 7.2 is released
13:10:21 <Guest|96096> Hi NamelessCoder. You helped me out a few minutes ago with setting up fluidcontent_core I have copied all the templates into my extension in the same place as in fludicontent_core. I now only see the headers and no content?? any ideas would be most appreciated. Thanks
13:12:13 <Guest|96096> it doesnt seem to render section Main
13:16:39 <NamelessCoder> Guest|96096 if you changed layoutRootPath, also copy those.
13:20:50 <Guest|96096> NamelessCoder - I copied everything into the same place. I am just trying disabling layoutRootPath to see if anything chnages
13:24:55 <Guest|96096> NamelessCoder - if I just add plugin.tx_fluidcontentcore.view.templateRootPath = EXT:my_ext/Resources/Private/Templates/ i only get the header and no content
13:31:45 <Guest|96096> NamelessCoder templates are stored in Resources/Private/Templates/CoreContent/
13:32:23 <Guest|96096> I just have latest versions from TER installed
13:38:41 <Guest|96096> NamelessCoder. School boy error on my part. I names the folder ContentCore rather than CoreContent
14:19:02 <Outdoorsman> Guest|96096 also don't forget that you can use this:
17:12:54 <NamelessCoder> incoming - run for cover!
17:58:44 <Opk> Hi all. I'm trying to use l10nmgr with fluid content based. Latest l10nmgr won't export any data for tt_content element build with fluid. Can you give me any pointers?
18:30:27 <benjamin_654> Opk: I looked into this some days ago. l10nmgr expects xml tags in the flexform structure which fluidcontent does not provide ($dataStructArray['meta']['langDatabaseOverlay’]). So those two extensions are not compatible.
19:06:43 <Opk> @benjamin_654, thanks for the info. It seems that localization is serious deal breaker for using fluidcontent and fluidpages in multi-language projects for now.
19:08:39 <Opk> @NamelessCoder, I've noticed you started playing with l10nmgr (https://github.com/NamelessCoder/l10nmgr). Do you have any planes for it?
19:12:35 <NamelessCoder> Opk it's a fork of xavers repository so you should ask him about the status
19:13:51 <Opk> @NamelessCoder, I will thank you :)
04:09:10 <benjamin_654> Opk: nice! I did not know about this fork. Will have a look at it.
11:18:03 <drlimbo> HI NamelessCoder, i just updated to VHS 2.3.0 (from 2.2.0) but now the "v:page.header.meta" fails and the documentation wasn't updated
11:18:10 <drlimbo> PHP Warning: Missing argument 2 for FluidTYPO3\Vhs\ViewHelpers\Page\Header\MetaViewHelper::renderTag()
11:23:19 <NamelessCoder> please check out development and try again
11:24:16 <NamelessCoder> and as far as possible please don't forget to give the development branch a try - every error like this you catch before we release is an error we don't end up releasing ;)
11:24:43 <NamelessCoder> (as in: give it a try *regularly*) ;)
11:28:39 <NamelessCoder> oh yeah - and we ask for a lot of patience in the docs updating. It's not yet automated so there are some manual actions involved, plus very long cache life.
11:28:55 <NamelessCoder> it *will* get better, trust me ;)
11:29:06 <drlimbo> oh, with your latest commit it works well NamelessCoder
14:04:07 <Outdoorsman> NamelessCoder, should I submit a new bug for what we found yesterday? Which extension should the typoscript order of precedence issue be reported in?
14:15:30 <NamelessCoder> no need, I'll be fixing that momentarily ;)
17:39:37 <Outdoorsman> NamelessCoder: Currently the first typoscript line is the one that is written last regardless of the 10 or 20... shouldn't it be the last line that overwrite the first one?
17:46:35 <NamelessCoder> it should be using the one with lowest priority last
18:19:56 <Outdoorsman> NamelessCoder: Not arguing, but it seems it should be the other way around. For example in typoscript if I enter page.includeCSS.file1=fileadmin/local.css and then on the next line enter page.includeCSS.file1=fileadmin/local2.css, local2.css is the one that's used.
18:21:25 <Outdoorsman> The last one overwrites the first one.
18:25:44 <NamelessCoder> yes, that's true for standard typoscript. There, the order of lines is all important. But when you configure objects that use those numeric indices, the rules change. Most (but not all!) of those objects will internally sort the sub-objects/values according to that numeric index
18:25:57 <NamelessCoder> page.includeCSS is *not* among those that sort
18:28:48 <Outdoorsman> Okay... I'll take your word for that one then.
18:29:15 <Outdoorsman> More feedback... ss for the templateRootPaths.10, the numbers at the end don't make any difference yet, just the line item order in.
18:29:38 <NamelessCoder> rule of thumb is: if the indices are truly numeric and only numeric is supported, the array is sorted. That goes for most COA, USER etc. objects you see in TS
18:30:47 <NamelessCoder> for templateRootPaths etc. in a Flux context those arrays should now be sorted, assuming all the caches are nuked and you pulled Flux very recently
18:31:34 <Outdoorsman> I *just* pulled it and cleared cache. I didn't do a full rm -rf typo3temp/* though... I'll try that in case something is hanging on.
18:35:27 <Outdoorsman> I just hard flushed cache and the numbers are not being sorted yet.
18:38:46 <NamelessCoder> yeah I think you're right... it does sort, but in the wrong order
18:45:42 <NamelessCoder> now this should match how the core's View classes expect to receive the paths
18:46:14 <NamelessCoder> it internally just uses the order it is given - and Flux is now giving it the right order. I actually thought the core reversed it internally but it seems it doesn't.
06:29:25 <Guest|76666> Hello, I'm trying to implement a vertical menu with subitems. Is it possible, in this case, to set an active Class to the links? Also I wanna show the name of the parent item as headline above the menu. https://gist.github.com/anonymous/85bcf4f3f2b893d08571 can someone help me?
06:37:25 <NamelessCoder> Guest|76666 for CSS class, use class="{item.class}". To read a property from a page by passing the UID, use https://fluidtypo3.org/viewhelpers/vhs/master/Page/InfoViewHelper.html and feed it the "pid" from the item which parent's title you want displayed.
06:44:32 <Guest|76666> @NamelessCoder thanks, it works!
06:59:07 <drlimbo> NamelessCoder: im wondering about the inheritance of flux:field.inline.fal
06:59:34 <drlimbo> im using this on a page, but "page AND subpage" are displayed and both are synced? https://www.evernote.com/shard/s8/sh/46b57edc-4e19-4ec4-9957-d197b4a1a3bd/5b5e8a7a1bfc5236018d26faeb49b27d/deep/0/hbz.png
06:59:46 <drlimbo> and on the subpage i dont have access to those pictures
07:04:57 <NamelessCoder> drlimbo inheritance of FAL resources doesn't work because they are tied to the page record itself and are m:n.
07:06:17 <NamelessCoder> you can manually traverse the page rootline and use the first page that has any relations (you'd be selecting relations inside a loop) but there are no mechanisms to let you do that automatically
07:06:58 <drlimbo> allright, so i need to check on the subpage "if no media -> check parent-page for media"
07:07:17 <drlimbo> but why there are two "file-lists" in page settings? (Page AND Subpage?)
07:11:00 <NamelessCoder> not sure what you mean by that
07:12:43 <drlimbo> here are two "configurations" NamelessCoder -> https://www.evernote.com/shard/s8/sh/46b57edc-4e19-4ec4-9957-d197b4a1a3bd/5b5e8a7a1bfc5236018d26faeb49b27d/deep/0/hbz.png
07:14:28 <NamelessCoder> same problem, unfortunately.
07:15:01 <NamelessCoder> the m:n is created using the Flux field name + page UID which means that if both templates use the same FAL IRRE field name, values are duplicated after you save them.
07:15:39 <NamelessCoder> this is a core issue and has been right from the start - the situation is slightly better now with flexforms because the flexform field name, not the record's field name that contains the flexform, is used for the relation.
07:47:01 <Guest|50850> Hi Everyone. Is is possible to use tkcroptumbs to render cropped images in custom content elements using fluidcontent?
07:58:24 <benjamin_654> Hi Guest|50850, i dont know that extension. But i would guess if you create a fluidcontent-element with a content-area where you then place such a image it should be rendered fine. But i expect problems if you also use fluidcontent_core.
08:02:50 <Guest|50850> benjamin_654 I am using flux:field.inline.fal to add the image rather than adding an image content element.
08:04:58 <Guest|50850> Thanks for you help, I'll keep digging
08:05:12 <benjamin_654> Guest|50850: Then i dont see a way to use the rendering of tkcroptumbs. But you can easyly crop the images yourself with the image view-helpers https://fluidtypo3.org/viewhelpers/vhs/master/Media/ImageViewHelper.html
08:14:09 <drlimbo> thanks NamelessCoder, but now im wondering what inherit="1" means in flux:field.inline.fal
08:39:18 <drlimbo> NamelessCoder: is v:page.resources.fal gone? can't find that in the documentation and it doesnt work, but v:content.resources.fal works well
08:48:11 <twistedNerv> i dont get lang translations from locallang file to flux and thats why i would like to check where is the problem. I have turned on debug mode in flux extension. Where cani see the errors?
08:56:43 <benjamin_654> drlimbo: The documentation for inherit=“1” is here: https://fluidtypo3.org/viewhelpers/flux/development/Field/Inline/FalViewHelper.html#argument-inherit - but as N.C pointed out, inheritance of FAL does not work. This may be a bug - if it does not work for you, please create a issue on github that this argument isnt used/working in this viewhelper and it should be removed
09:00:36 <benjamin_654> drlimbo: your welcome btw. v:page.resource.fal doc is here: https://fluidtypo3.org/viewhelpers/vhs/master/Page/Resources/FalViewHelper.html
09:02:05 <benjamin_654> twistedNerv: which view helper are you using?
09:02:30 <drlimbo> thx benjamin_654 - but the "shortmode" {v:page.resources.fal(field: 'media') isn't working for me -> found it here: https://fluidtypo3.org/viewhelpers/flux/master/Field/Inline/FalViewHelper.html
09:04:23 <benjamin_654> twistedNerv: did you try do add the ‘extensionName’ argument? This helped me if the template belonged to a other extension than locallang.xlf.
09:05:38 <benjamin_654> drlimbo: and the tag version does work?
09:09:06 <twistedNerv> benjamin_654: im using 2.2.0 (VHS: Fluid ViewHelpers )
09:09:47 <twistedNerv> locallang file is in the same extension
09:15:05 <drlimbo> benjamin_654 - it works if i add table etc, maybe this isn't default?
09:17:46 <benjamin_654> twistedNerv: There are a few possible causes for problems with the translation files. One of the is for example a wrong language key ( config.language = de ) in the typoscript configuration or the locallang filename or xml-attributes. I dont think this is a problem with vhs or flux.
09:24:51 <twistedNerv> oh, ill check that ... tnx!
09:28:27 <benjamin_654> drlimbo: there are defaults for table and field. Required is only ‘uid’ or ‘record’.
09:30:19 <drlimbo> so benjamin_654 {v:page.resources.fal(field: 'media')} should work, not?
09:35:06 <benjamin_654> drlimbo: no, either uid or record is a required argument. So it sould be: {v:page.resources.fal(record: record)} // but check if record is really available and its the page-record
09:44:46 <drlimbo> is there a way to automatically add the LanguageParam to every Link? so i dont have to add additionalParams? <f:link.page pageUid="{subitem.uid}" additionalParams="{L: '{v:variable.typoscript(path: \'config.sys_language_uid\')}'}"
09:47:35 <benjamin_654> drlimbo: i think you are searching for typoscript: config.linkVars = L
09:47:35 <benjamin_654> but for general typo3 or typoscript questions you shold visit room #typo3
09:50:53 <drlimbo> oh, thanks benjamin_654! i tried nearly everything =P
12:24:31 <drlimbo> im stuck again with .record.fal =P
12:24:47 <drlimbo> {v:resource.record.fal(record: page, field: 'media', table: 'pages', uid: 1) <- why does this only work on Page with uid:1 an not on other pages?
12:25:06 <drlimbo> is it not possible to get fal-media from parent page?
12:25:19 <drlimbo> benjamin_654 maybe u can help me here too?
12:30:56 <benjamin_654> drlimbo: You should only use one argument: record OR uid. Does this work?: {v:resource.record.fal(record: page, field: 'media', table: 'pages')}
12:30:57 <benjamin_654> Or to get the parent : {v:resource.record.fal(uid: page.pid, field: 'media', table: 'pages')}
12:42:30 <drlimbo> ah, tahts works benjamin_654 - thanks
12:42:50 <drlimbo> so i have to check - if no media - check if parent has media - if not - check parent-parent for media
12:52:27 <benjamin_654> drlimbo: I actually made a viewhelper for this problem: https://gist.github.com/BenjaminBeck/b77720d57718579b8c08
12:52:27 <benjamin_654> Performance is improveable but it gets the job done..
12:54:33 <drlimbo> i just did it the ugly way with multiple if then else =(
12:55:02 <drlimbo> but i'll switch to your viewhelper tomorrow morning and try if I can do it like that
12:55:30 <drlimbo> you also have a solution for inheritance of flux:grid.column benjamin_654?
12:58:51 <benjamin_654> drlimbo: <v:content.render column="12" slideCollect="1" slide="1" slideCollectReverse="true"/> does work for me, but i am not sure if this is what you want ..
12:59:07 <drlimbo> oh, i have to check that too =)
13:00:23 <drlimbo> sorry benjamin_654, but where i have to put your viewhelper?
13:04:58 <benjamin_654> drlimbo: sorry, i haven´t got the time to walk you through creating a viewhelper - but there are plenty tutorials available: https://stmllr.net/blog/writing-a-basic-fluid-viewhelper-for-typo3/ ; http://t3-developer.com/1/extbase-fluid/cheats-fluid/viewhelpers/view-helpers-selbst-erstellen-eine-anleitung/ ..
13:05:34 <drlimbo> allright, thank you benjamin_654
13:17:44 <drlimbo> benjamin_654: i can try to extend your viewhelper tomorrow, to add type (now "media") as parameter, so i can also get FAL-Images from my FlexForms
13:20:49 <drlimbo> not? i thought if i switch fileRepository->findByRelation('pages', 'media', $page['uid']); to ('pages', 'mySpecialField', $page['uid']); <- as a param, this should work?
08:21:49 <vizArt> hi: ISSUE: BackendConfigurationManager on CLI Scripts (https://github.com/FluidTYPO3/flux/issues/668) is still broken in version 7.1.2
08:22:30 <vizArt> the fork from akii (https://github.com/Akii/flux/commit/391c02093f0aafa5e919d729429e010b4acba76c#diff-27bf5883578afaf149e9b26735ad57df) works.
08:32:05 <vizArt> I noticed this first time nov.2014 ... https://fluidtypo3.org/community/irc-logs.html?tx_fluidtypo3org_content[date]=20141119&cHash=1addc7ada531144b667e5745b9be95be#09:56:30
08:32:31 <vizArt> but today i remebered after my sheduler wont work after update
08:39:10 <Akii> NamelessCoder: somehow a change that was merged is unmerged
08:39:20 <Akii> that one https://github.com/FluidTYPO3/flux/pull/706
08:39:24 <NamelessCoder> Akii recently I removed some methods from Flux's ConfigurationManager because they were behaving exactly like the inherited methods would behave
08:39:51 <Akii> vizArt reports something is broken :D
08:42:23 <vizArt> still present ... and a big problem
08:43:39 <NamelessCoder> vizArt 7.2 is right around the corner but if you can, please confirm whether that happens with the development branch. We wouldn't want to release a new version with that one still hanging around.
08:48:53 <vizArt> ok, thanks for the info ... i have modded the v.7.1.2, so it works for now
10:29:10 <fger> hi guys, im experimenting with TYPO3 6.2.10 and composer-based install of core/extensions...
10:30:05 <fger> installing typo3-ter/news works like expected - copy of the extension files in typo3conf/ext/news and the composer librarie under Packages/Libraries...
10:30:46 <fger> but when installing / requiring e.g. fluidtypo3/fluidpages the Extension Manage shows 2 installed extensions
10:31:05 <fger> one fluidpages and the other named LibrariesFluidtypo3Fluidpages
10:32:00 <fger> looks like the new composer-autoload-mechanism hooks in and both extension file locations get registered in the PackageStates.php ... can anyone confirm ?
11:10:37 <fger> small other question: Does anyone know, if the copy/paste bug of inline-fal-related images, that lets also flux:field.inline.fal (latest flux dev) relations fail, is solved in TYPO3 6.2.10 ?
11:12:58 <NamelessCoder> fger haven't tested that one - if you do, please report here ;)
11:49:14 <Arrluk> Hi. I want to create an anchor menu (fluid content object) of all content elements of the current page. How can this be done? How can i access the content of other fluid based content objects of the current page…its all stored as XML inside the record.
11:54:44 <NamelessCoder> Arrluk see v:content.get/flux:content.get + flux:form.data
11:55:02 <NamelessCoder> flux:content.get if the content you want to list is child content of another element
11:55:11 <NamelessCoder> v:content.get if it is page-level content
11:55:47 <NamelessCoder> flux:form.data to extract the content's Flux options if you need them. The standard record attributes are available as plain array.
12:05:56 <Arrluk> But i cannot loop with v:content.get?!
12:06:48 <pedda> Arrluk you know about the sitemap ce which is capable of anchor list ?
12:07:55 <pedda> a fluid content element is always wrapped by a div.csc-default div by default and prepended by an anchor
12:08:42 <pedda> it shouldn'T make any difference if those ce's are fce's or default ce's anyway, so in my opinion you could use the sitemap ce
12:09:48 <pedda> if the menu you want, is not planned to reside somewhere fixed in your page layout
12:22:21 <Arrluk> The section index output was empty so i tried to build another fluid based CE..almost all content elements are based on fluid in this case.
12:25:04 <pedda> as this is a core feature, it doesn't matter how your content elements are implemented (DCE, fluidcontent, templavoila, whatever)
12:25:20 <Arrluk> But i can try to use another viewhelper to get all elements of the page where i can loop through…then try flux:form.data. basically i didn´t know how to access the xml
12:25:36 <pedda> each content element is wrapped by a div and prepended with an anchor as long as you didn't move some TypoScript around to avoid this
12:26:33 <pedda> if i would have been requested with your task i would kne, that each content element has it's own marker like c123 where 123 is the content element's uid
12:26:49 <pedda> i would have placed a sitemap ce in my "sidebar" or whatever
12:28:50 <Arrluk> In this case it was requested to do this with fluid….i know about the section index but its more like "optional" way
12:29:11 <pedda> nearly anything is optional in typo3
12:29:20 <pedda> there are a lot ways to achieve a goal
12:30:07 <Arrluk> I know…It´s an alternative way im looking for…Thanks anyway!
12:30:29 <pedda> okay if i get you right, the task now is: create a fluid content element which renders a list/list-group (bs3) which contains links to all content elements
12:31:08 <pedda> i would use the page.uid and select all content elements whose pid is = page.uid
12:31:51 <pedda> and render links to #c<ce.uid> as many times as i have matches returned in my fce file
12:31:54 <Arrluk> I did this…just didnt know how to acess the flexform data as i wrote earlier
12:32:43 <pedda> aaah .. now i get it.. you need to access the flexform, because you use your own title field instead of the content element's default Header field
12:33:06 <Arrluk> I used v:content.render before as this provides a way to iterate through the elements
13:32:29 <benjamin_654> hi, i can remember that there was a change for default icon filenames & location the last few days - but i dont find the commit.. has someone a link at hand?
14:54:09 <JustAPoring> Ugh... I'm dealing with an issue where a an element with a flux grid column can be cut & pasted into itself, which leads to happy little errors.
14:54:21 <JustAPoring> I'm running an older version in this project, does anyone know if this was ever fixed? :(
15:03:25 <benjamin_654> JustAPoring: i just tried it with current development branch -> This bug is still there (->Fatal error: Maximum function nesting level of '5000' reached, aborting!)
15:04:01 <JustAPoring> benjamin_654: Thanks for testing! That sucks. I'll open an Issue in that case. Would this be related to flux or fluidcontent?
15:06:00 <benjamin_654> Now my backend is gone ): …..
15:06:46 <JustAPoring> benjamin_654: You can edit the 'content area of parent' of that element through the list view... But I haven't found a way to get rid of this element without direct DB acces yet
15:07:42 <benjamin_654> JustAPoring: thx, but i have a script that pulls the live db into dev .. so its not a big deal ..
15:09:22 <JustAPoring> benjamin_654: I wish I had a way to have a beuser get rid of tho.... the customer of this project managed to kill ~5 pages already.
15:17:09 <benjamin_654> JustAPoring: you can try the blacklist feature (if its already available in your version)
15:18:23 <JustAPoring> benjamin_654: Any idea roughly when that was implemented? We're using 3.1.2 in this project - according to emconf.
15:18:57 <JustAPoring> Hm.. it looks like we're quite up to date for fluidcontent actually.
15:19:29 <JustAPoring> benjamin_654: This sounds great! I'll check it out.
15:39:36 <JustAPoring> benjamin_654: It didn't work, sadly. That one only hooks into the wizard, and doesn't do anything about copy/pasting blacklisted objects.
15:42:26 <benjamin_654> Outdoorsman: looks good to me
15:42:39 <Outdoorsman> I'm not really sure what Tx_Fluid_ViewHelpers_Widget_PaginateViewHelper.templateRootPath does or where to find documentation???
15:43:46 <Outdoorsman> The full thing is... plugin.tx_fluidbootstraptheme.view.widget.Tx_Fluid_ViewHelpers_Widget_PaginateViewHelper.templateRootPath
15:44:15 <benjamin_654> Outdoorsman: it overrides the templateRootPath for the Paginate Widget - if you dont use it, you dont need it..
15:44:58 <Outdoorsman> Okay, so it could accept templateRootPaths.10, templateRootPaths.20. Thanks... that's what I needed to know.
15:45:50 <JustAPoring> Outdoorsman: Correct me if I'm wrong, but you don't really need to use templateRootPaths unless you actually require for there to be that fallback mechanism that comes with it...
15:46:05 <JustAPoring> Since that widget is a single template file I don't see how you would ever need to use the fallback mechanism for that one.
15:46:41 <JustAPoring> Are people actively suggesting to never use templateRootPath and always use templateRootPaths?
15:47:01 <Outdoorsman> Maybe that's true. But by nature fluidbootstraptheme will have a provider extension overriding it 99% of the time.
15:47:12 <NamelessCoder> yes we are JustAPoring, because the singular naming is deprecated
15:47:29 <JustAPoring> NamelessCoder: Oh, when was that deprecated? Some 7.x version?
15:47:58 <JustAPoring> So they immediately deprecated the singular? :O I didn't know that.
15:48:03 <NamelessCoder> currently gets used as fallback but support won't be eternal
15:49:29 <JustAPoring> This might cause even more confusion for look-alikes which don't support the plural variant... But I suppose that's gonna work out eventually.
15:51:21 <Outdoorsman> Thanks for the comment NamelessCoder. JustAPoring, to override the fluidbootstrap theme in my provider extension I have to do "plugin.tx_fluidbootstraptheme.view >" and then recreate it from scratch with the templateRootPaths.10 and .20 to override it properly.
15:52:06 <Outdoorsman> That another reason it seems nice to have it overlay ready.
15:52:26 <Outdoorsman> Or whatever terminolgy I should be using.
15:53:29 <JustAPoring> Yeah... but I've seen some extensions which sometimes used view.templateRootPath for standalone templates ... that is what I assumed would cause confusion once the acutual view.templateRootPath is removed.
15:54:31 <NamelessCoder> I initially submitted a patch for the core which suggested the use of the "overlays." array to define *additional* template paths that would be checked before the fallback path
15:54:53 <NamelessCoder> this patch was rejected and replaced later by the one that is used now, that introduced templateRootPaths (plurals)
15:55:32 <NamelessCoder> the reason for doing that is that apparently, that methodology fits better with the configuration pragma of Flow, which is to grab Yaml files from packages and each package completely replaces any others it overrides
15:55:51 <NamelessCoder> now, the problem came "how to support the legacy path name and the plurals at the same time".
15:56:05 <NamelessCoder> (which wouldn't have been a problem at all, had they chosen my patch, but I digress)
15:56:16 <JustAPoring> Do you know if there is an easy way to replicate the functionality of templateRootPaths for StandaloneViews?
15:56:23 <NamelessCoder> the decision was made initially that if defined, templateRootPath would be the ONLY path checked
15:56:48 <NamelessCoder> so in 6.2 you couldn't properly use these for overlays without first removing the existing view configuration
15:56:56 <Outdoorsman> I like the templateRootPaths.x option much better, it was a good move!
15:57:11 <NamelessCoder> and this is where the whole problem began - so, Anja made efforts to fix this, letting templateRootPath work as *fallback* rather than *override*
15:57:48 <NamelessCoder> anywho: now, the templateRootPath works as fallback but is still considered just as much legacy as it was in 6.2
15:57:59 <NamelessCoder> it's probably going away in 7.2 LTS, mind you!
15:58:12 <NamelessCoder> alright, so, now the situation STILL is that we're using arrays to define these paths
15:58:27 <NamelessCoder> and those arrays are, because of the very similar naming, bound to be confused.
15:58:36 <NamelessCoder> one value is an array, the other is a string.
15:58:37 <benjamin_654> Ah .. i begin to understand a problem i had with that overriding templateRootPath ..
15:58:54 <NamelessCoder> this is why https://github.com/FluidTYPO3/flux/blob/development/Classes/View/TemplatePaths.php exists
15:59:36 <NamelessCoder> it *forces* every path usage in Flux (but not the core itself) to go through a proper object that sorts all this crap out and hides away the underlying configuration, replacing it with methods that *always* and *only* return path arrays.
15:59:53 <NamelessCoder> this class supports ALL the current naming conventions: singular, plural, overlays.
16:00:18 <NamelessCoder> but the core hasn't adopted anything like this and it still passes the arrays in raw to the template views (including the standaloneview, JustAPoring)
16:00:39 <NamelessCoder> internally the core's view STILL has methods to getTemplateRootPath which are no longer used by the core.
16:00:50 <NamelessCoder> they may however still be used by extensions that implement custom views
16:01:13 <NamelessCoder> and that's the problem: the core's views' methods that return a templateRootPath will return a reset($this->templateRootPaths)
16:01:40 <NamelessCoder> because the singular method is deprecated and no longer used, that is safe for almost all cases - but not all
16:02:11 <NamelessCoder> you can immediately see how that causes severe issues if someone were to configure a plugin to use the plurals but the developer only implemented the singular
16:02:58 <NamelessCoder> initially Flux only supported the singular naming + overlays (internally added, same as in EXT:view). It did this because 4.x and 6.2 both had to be supported (and there was no TemplatePaths object back then)
16:03:18 <NamelessCoder> this is still true about the TER version. It simply doesn't support the plural paths - they're ignored.
16:03:48 <NamelessCoder> however, in the development branch, all paths handling is pushed through TemplatePaths and homogenised. There's no more Q if some naming is supported - they all are.
16:04:31 <NamelessCoder> but even so, there is no way to guard against people using the deprecated methods on the view they instantiate manually. And if they do, back comes the problem that only a single path is supported
16:05:00 <NamelessCoder> plenty extensions have been adapting to this new naming in recent months; Flux is just a bit behind because of the LTS support requirement
16:05:25 <NamelessCoder> so that's the story and the full story behind paths in fluid
16:05:50 <NamelessCoder> and how that relates to Flux, what works and doesn't and why, and when you can expect it to change
16:07:17 <JustAPoring> NamelessCoder this sounds like a huge headache.
16:07:32 <NamelessCoder> JustAPoring tell me about it. A lesser man would have cried.
16:08:18 <NamelessCoder> JustAPoring so to answer your Q about the plural paths support for standalone views: Use FluidTYPO3\Flux\View\TemplatePaths, feed it your existing paths array in the constructor and use the getters afterwards to get paths and resolve templates.
16:09:21 <JustAPoring> NamelessCoder: thanks for your work. ;) I will do the next time I'm in that situation.
16:10:42 <benjamin_654> i often feel like the core has the “not invented here”-syndrom .. i still thing extbase could have used symfony/doctrine components ..
16:10:58 <NamelessCoder> ah, there's my old hobby horse
16:14:36 <NamelessCoder> to people coming from for example Drupal I can tell you TS is crazy flexible
16:15:10 <NamelessCoder> it also has its strong points vs. fluid (but mostly because TYPO3 invented the "integrator" job)
16:15:30 <Outdoorsman> Thanks for the history NamelessCoder... I almost feel like I just got to watch a movie, my emotions going up and down, agreeing then disagreeing, you have a bright future ahead :)
16:15:46 <JustAPoring> Flexibility isn't everything if basic templating tasks are a chore
16:16:47 <JustAPoring> I should read this channel more often. :D
16:16:51 <NamelessCoder> heh yeah Outdoorsman you win some, lose some - and you *definitely* have to pick your battles. To me, that paths thing wasn't one I wanted to fight
16:17:43 <Outdoorsman> Understood. Some people have real work to do once in a while too :)
16:19:54 <Outdoorsman> JustAPoring... I am really enjoying the templating options that the whole FluidTYPO3 ecosystem has opened up but at the same time, I'm findinig that it still takes me quite a bit longer to go from design to production than it did with Templavoila (don't throw anything at me).
16:21:02 <Outdoorsman> For a small web developer like myself, it comes down to how long does it take. If it takes longer, I have to charge more and it makes it harder to complete with my competition.
16:21:27 <NamelessCoder> Outdoorsman it's just a matter of training like everything else. In time you figure out the solutions that solve your exact problems - and they do tend to be the same problems over and over
16:21:27 <JustAPoring> I'm in the luxurious situation that I've never had to develop with templavoila from scratch, only maintain some, so I can't really comment on that
16:23:03 <Outdoorsman> No matter what someone says, there was power in that point and click method that Templavoila used. I created a custom template, point/click, and bam it worked. I wish there was a dummy way to do the same thing in FluidTYPO3 that would also allow for customization.
16:23:35 <NamelessCoder> the things I could do if my only job was FluidTYPO3...
16:23:58 <NamelessCoder> it's been two years now since I thought out the way to do that, Outdoorsman - but it's a 3-4 month job, minimum.
16:24:03 <Outdoorsman> It's my pie in the sky, I know. But turnaround time is huge.
16:24:12 <JustAPoring> Hell, in still quite new with TYPO3 considering all, with roughly 3 years under my belt now
16:25:33 <Outdoorsman> well NamelessCoder, if you really really think that it's a good solution that would help reduce the barrier to entry, it just may be worth talking to some big investers like AOE or whoever and it could become the new gold standard.
16:27:01 <Outdoorsman> Not trying to convince you to do something that may not fully be adopted though. It might be something to make a public project from the beginning with a clear goal, milestone, teamwork and everything.
16:27:47 <Outdoorsman> Many minds working toward a common goal should give it much bigger adoption as well as a potentially better solution.
16:28:56 <NamelessCoder> currently there's no agency support (money-wise) behind. It's been, what, 5 years or so without any mention of putting serious money in it.
16:29:36 <NamelessCoder> not that I complain, I'd still be doing this without it. But that's the main reason why some of the features don't go beyond thinking stage.
16:31:23 <Outdoorsman> Seems I get laughed out of town whenever I bring up this topic so thanks for at least entertaining it. I really don't think I'm imagining when I say this could bring TYPO3 to a much broader audience and would also benefit the programmers as well so there's less chance for error and faster time to market.
16:31:34 <NamelessCoder> also, FT3 doesn't want to become gridelements. No offence to their strategy, I just don't agree with it.
16:32:01 <NamelessCoder> Outdoorsman have you tried EXT:site, the pseudo-distribution for FT3?
16:32:32 <NamelessCoder> it's not point-and-click templating but it does all the heavy lifting and makes a folder mount in file list where you can edit your first two templates
16:32:57 <Outdoorsman> Hmmmm... thanks for the tip.
16:33:04 <NamelessCoder> that's the best compromise so far in regards to entry barrier
16:35:32 <JustAPoring> No offense, but IMHO the state of the documentation is the largest entry barrier ( in case nothing much changed the last couple of months )
16:35:42 <Outdoorsman> site... very interesting... that's a unique way of handling things.
16:36:27 <JustAPoring> I know all too well that writing documentation is a time consuming task
16:36:43 <NamelessCoder> JustAPoring we get almost zero contributions for documentation
16:37:04 <Outdoorsman> JustAPoring: This has been a good section for me to get acquainted with, https://fluidtypo3.org/viewhelpers/flux/development.html
16:37:13 <NamelessCoder> trying to arrange updates for Flux 7.2 launch currently
16:39:51 <JustAPoring> I know the ref but often - especially for flux which IMHO is not very self explanatory - knowing a viewhelper and its attributes are one step of the way.
16:40:27 <NamelessCoder> it's based on TCA - 'nuff said ;)
16:41:58 <JustAPoring> When I stated with FT3 the doc had huge holes. Is that still the case? (On phone right now or I'd check)
16:42:30 <NamelessCoder> 10-15% of the pages are still missing (the more advanced parts)
16:43:00 <JustAPoring> Sadly those are probably very important parts...
16:43:58 <JustAPoring> But is sad to hear there are so few doc contributions
16:44:21 <JustAPoring> Not that I've made any myself to be frank
16:44:54 <JustAPoring> I am very much part of the problem
16:46:53 <NamelessCoder> well, if you know some magic trick that solves this problem don't wait to tell me ;)
16:47:22 <NamelessCoder> at this point, contributing is as easy as clicking a button and writing Markdown which everyone can learn in a few minutes
16:47:37 <NamelessCoder> not sure how to improve that, short of paying people to write
16:55:37 <Outdoorsman> JustAPoring... I'm sure NamelessCoder wouldn't mind you sending a donation to help out with his time if you can't do it. I've done that a little becuase i know it takes a lot of free time. I try to give back when I can.
16:56:20 <Outdoorsman> There are also some quite active folk on the vhs team too
17:04:35 <NamelessCoder> donations are of course appreciated :)
17:15:05 <JustAPoring> Well I can't really offer any donations - but contributions might be possible ;-)
18:15:24 <Arrluk> i read that its currently not possible to use FAL elements inside flux.objects…is there any workaround for that. maybe to create a fluid container element where the single elements are stored….i need multiple elements for a slideshow (not a fixed number of row)
18:17:00 <Arrluk> I get the error "Wrong configuration in table a7c727320c"
07:04:17 <Kaimane> Hey guys. After upgrading all fluidtypo3 extensions from git (dev branch) I got this error message in backend when opening a page in page module: Fatal error: Call to a member function resolvePrimaryConfigurationProvider() on a non-object in /var/www/clients/client20/web410/web/typo3conf/ext/flux/Classes/Service/FluxService.php on line 373
07:04:35 <Kaimane> Do you know whats wrong or what i missed?
07:14:57 <Kaimane> Do I need to migrate something?
07:40:28 <Kaimane> Okay, I got it. The "s" was missing in TS: plugin.my_ext_view.templateRootPaths .partialRootPaths and .layoutRootPaths
07:41:15 <Kaimane> Sry: plugin.my_ext_view.templateRootPaths.0 .partialRootPaths.0 and .layoutRootPaths.0 ;-)
07:56:02 <Torsten85> hey, I've added flux / fluid content to my typo3 v7 instance and all is working as expected except drag & drop in the page module. I guess flux is not yet fully compatible or is it a bug?
08:36:47 <jmverges> I'm taking a look to: should I do a PR and change: https://github.com/FluidTYPO3/flux/blob/development/Classes/Hooks/WizardItemsHookSubscriber.php#L265 ?
08:36:52 <Torsten85> yeah, but that part is working right noch as it should
11:18:23 <jmverges> xaver, what do you mean when you say additional containers ?
12:27:03 <jmverges> NamelessCoder, what do you think about https://github.com/FluidTYPO3/fluidcontent/issues/222 ?
12:37:59 <NamelessCoder> jmverges I think you need a bit of discipline with your git commands my friend ;)
12:40:07 <jmverges> I'm still trying to understand the approach 0_
12:40:08 <NamelessCoder> I don't mean to preach, but the formal stuff is as important as the functional stuff. They don't work well separately but together they make clarity and consistency.
12:40:59 <jmverges> you are right, then, if I open an issue, and then I want to do a PR that resolve it, what should I do?
12:43:33 <NamelessCoder> almost exactly what you did, but the commit message should be something like this: https://fluidtypo3.org/documentation/contributing/contribution-guide.html#creating-a-pull-request
12:44:48 <jmverges> [FEATURE] Made VHS more awesome
12:44:48 <jmverges> This change makes VHS more awesome by increasing the
12:45:04 <NamelessCoder> basically, the commit message must explain what's being changed so you know without reading the diff. It's great to create issues first - but to reference it, use "Fixes: #123" or "Close: #123" or whatever. GitHub detects pretty much all of them.
12:46:10 <jmverges> okey, maybe the next time I get it. At least this time I didn't get the robot saying things like "all is wrong" it is because is turning off or because I did it partially fine?
12:46:13 <NamelessCoder> in this case though I had to take this opportunity to really clean up the affected class
12:46:35 <NamelessCoder> and I don't expect you as a contributor to have to do that first, then apply your change - so I hijacked it ;)
12:47:00 <NamelessCoder> yeah it's temporarily disabled because of noise
12:47:36 <NamelessCoder> the very best recommendation is to clone the repository, run composer install from the extension root and then use ./vendor/bin/make to install git hooks that validate everything *before* the commit is created
12:47:57 <NamelessCoder> as described in https://fluidtypo3.org/documentation/contributing/contribution-guide.html#initialising-the-repository
12:48:34 <NamelessCoder> if you do that, you'll make 100% sure you don't commit anything that breaks code and violates the rules we've included so far (it is not 100% complete regarding CGL check, but it is close)
12:49:16 <NamelessCoder> last note for IRC - you really should create separate branches when you create new features, less of a headache if something has to be changed
12:49:35 <NamelessCoder> the guide describes every single step and consideration - but it is a bit long ;)
12:50:49 <NamelessCoder> we'll be just as happy as you if your next contributions just race directly through that review step - win/win ;)
12:51:54 <jmverges> your code is much cleaner, I just try to do little changes by now, once that I get the approach correct I will try to suggest crazier things. At least I'm happy because the task are included so I just need to practice and practice, just please, have patience with me in the meantime. I started to feel that I'm going to be fired from my current job so I will have a lot of time to contribute :)
12:54:02 <NamelessCoder> Practice and more practice is precisely what it takes :)
15:54:56 <jmverges> I'm following the contribution guide step by step, let's see if I'm able to do a PR for https://github.com/FluidTYPO3/fluidcontent_core/issues/135 without any problems
15:55:57 <NamelessCoder> I'm here if you need feedback
16:27:48 <jmverges> it is taking a while doing composer install almost 10 minutes with - Installing typo3/cms (6.2.10) Downloading: 100%
16:28:06 <NamelessCoder> is is craaaaazy slow, yes :(
16:28:34 <NamelessCoder> first time. Next time, also if you do it for other ft3 exts, it will get it from cache and should be much faster.
16:33:06 <jmverges> Great, let's see if it finish. I was reading https://github.com/FluidTYPO3/fluidcontent_core/issues/35 all the thread is interesting I'm thinking about if it is really necesary to use FCC, I mean, FCC is much more better than CSC however, if we are able to have as many fluidcontents as we like, what is the point of FCC? could be posible just to remove all default CTypes and just work with Fluidcontent? I was thinking about it for some time and this is th
16:33:06 <jmverges> e reason because today I was looking about allowedContentTypes information
16:34:21 <NamelessCoder> the point is to preserve those core types - text, image, media etc.
16:34:42 <NamelessCoder> many third-party extensions will for example index these differently, will restrict allowed content types and much more
16:35:45 <NamelessCoder> the other aspect is that the native CTypes are all able to be protected/granted via user group permissions - that is not true for fluidcontent elements unless such restrictions are manually made possible in (just as example) page TS config for each user group.
16:36:28 <NamelessCoder> but you are correct that they are extremely similar (on purpose hehe) except for the CType/tx_fed_fcefile situation
16:37:26 <jmverges> what about extend the group permissions to include the different Fluidcontent in the list of group permissions? too mad?
16:37:38 <NamelessCoder> from what I hear, TYPO3 7.2 will be rendering content using FLUIDTEMPLATE cObject which is a huge improvement already. When/if that happens, the only remaining reason to use FCC is the ability to use a custom controller - the rest will be possible in core.
16:37:48 <NamelessCoder> I don't think that's possible
16:38:13 <NamelessCoder> afaik no hooks exist at that point and it is unfeasible to generate the (fake) TCA it would require
16:38:57 <NamelessCoder> pageTSconfig can still remove/add elements if you set it on a user, a usergroup or at system level - it's not super user friendly, but it works
16:39:37 <NamelessCoder> there's a lot of that going around in the core btw. Some incredibly powerful features hidden away like royal gems :)
16:41:39 <jmverges> good to know, however versions and variations are part of FCC and that is nice
16:42:35 <NamelessCoder> that part is true of course
16:43:12 <NamelessCoder> arguably, one could get the same result in plain core (when it starts using extbase/fluid to render core elements) by way of an added TCA field and TS conditions
16:45:02 <NamelessCoder> but even when the core switches FCC will still have a place. We'll simply make it transparently use or at least be able to switch to the same configurations the core uses
16:45:10 <jmverges> Today I was taking a look to some WP Page Builder ( https://siteorigin.com/page-builder/ ) I don't like WP I think that it is a insult for the profession but I have to recognize that it has a lot of themes and this page builders are getting a lot of popularity so it is hard for me to defend TYPO3 when I talk with non developers
16:45:20 <NamelessCoder> so you get the whole provider, flux forms etc. without having to add it manually in TCA etc.
16:47:47 <jmverges> do you plan or do you know if anyone is doing something as visual as that WP Page Builder? I really feel sick talking about WP but the UX of that video is great
16:49:07 <NamelessCoder> it's a very, very deep topic...
16:49:25 <NamelessCoder> yes, it would be nice to have something like that to build pages or just structure page templates' grids etc.
16:49:37 <NamelessCoder> but it is an extremely big task
16:50:24 <NamelessCoder> afaik nobody is working on that (it pretty much amounts to completely recreating the TYPO3 page module - excluding the record editing module)
16:51:42 <NamelessCoder> mention the words FormEngine and ContentObjectRenderer and people usually flee
16:52:33 <jmverges> if you want to preserve all the TYPO3 functionality could be huge, but I think that mapping with Extbase pages and tt_content and some angular stuff could do the trick (at least, something to show to the community, a "mockup")
16:53:22 <NamelessCoder> it's the iceberg beneath the surface that's the problem
16:54:32 <NamelessCoder> there are SO many things you can manipulate with settings about how those interfaces behave. It's good to be brave but in this case, you'd probably end up with something that supports 10% of the original features and to add the remaining 90% would be close to impossible
16:55:25 <NamelessCoder> part of the problem here is that the original, underlying code in typo3 isn't written with modern design patterns in mind - and it is that code that everyone depends on (even Extbase depends on it)
16:56:18 <NamelessCoder> btw it was a discussion like this one that caused Neos to be invented in the first place ;)
16:57:00 <jmverges> yes, you probably are right, but there are beast developers (like you) that maybe could be amazed seeing a drag and drop page builder in admin and some real FE editing and then who knows
16:57:17 <jmverges> but Neos it is completely different to TYPO3, I love TYPO3
16:57:35 <NamelessCoder> the problem is not inspiration, it is time
16:58:14 <NamelessCoder> pay any one of those developers and they'd gladly create it - take Flow for example
16:58:47 <NamelessCoder> but it wouldn't have been created if there wasn't any money in it. The people with the skills to create it have no need to use it - they just grab the internals.
17:00:01 <jmverges> time and money :) all is related with it
17:01:24 <jmverges> no problem it is good to have someone putting my feet on the ground
17:02:30 <NamelessCoder> even so: we might not be able to change the whole thing, but we can make the smaller parts much better
17:03:20 <jmverges> I think that I'm going to be fired from my job, I have never been getting money from the state, but, if I got fired, I want to spend my time with TYPO3 and FluidTYPO3
17:04:33 <NamelessCoder> I've been sacked three times
17:04:57 <NamelessCoder> you get back up and next time, kick more ass ;)
17:05:41 <jmverges> but, you know, small company ugly code without templates just php html and js in .php, no phpstorm, no vagrant, no xdebug, no nginx, no scrum, ... I'm introducing all this and TYPO3
17:06:21 <jmverges> and it is too hard, because the developers don't want to learn anything and are just trying to arguee and complain
17:08:04 <jmverges> and as you know, I don't know as much as other developers arround but at least I'm on the right way (I think)
17:10:48 <jmverges> NamelessCoder, why were you fired? you are the fucking boss arround ;)
17:14:06 <NamelessCoder> once when I was 21 because I didn't want to work the way they wanted, then when I was 28 because they couldn't afford me any longer and then in 2013 because there wasn't enough work and money.
17:14:27 <NamelessCoder> no popcorn drama, sorry :p
17:15:04 <NamelessCoder> if you want to grow btw, you need to find a place where people are already better than you
17:15:24 <NamelessCoder> otherwise you'll be growing them and you probably shouldn't be taking that responsibility so soon
17:26:13 <jmverges> yes, I know it, but they "sell me" the job and the company as fantastic and is not that. The last two years I was working in a bigger company an I learned about PSR-2, git, jira, jenkins, etc the bad point was that we were using private code so, all was in the mind of the architect and, for sure is a good developer, but is not a team player and he doesn't know about a lot of things related with javascript or FE in genral, he stole part of my code and he
17:26:13 <jmverges> said that it was his code and then I started to feel more and more burn out and then I left the company. I could get a better payed job in a casino online company (they needed a TYPO3 guy for do all the integration) and I refused it because I don't like the casino stuff, I meet some people that lost all their things with poker and other games. So, I finished here and workmates don't want to learn anything, this is the worse part, 0 ilusion 0 iniciative.
17:27:05 <jmverges> My 30th birthday was the last sunday
17:32:00 <jmverges> well, dinner time, my fiance started to be angry with me. See you later or tomorrow.
18:05:19 <NamelessCoder> that PR is *perfect* jmverges - but I think we might be able to nip this problem deeper at the source so it never even reaches the list of content one can insert
18:05:36 <NamelessCoder> that however is a matter of ancient TS :/
18:08:50 <jmverges> lol, at least the PR is well done. The contribution guide is good, I saw one issue, I will try to do a PR tomorrow to the contribution guide and I will do it right. ;) now, its time, my fiance is more and more angry XD See you latter
18:09:53 <NamelessCoder> formals of that PR is absolutely perfect
03:55:58 <jmverges> do you know which repository is on charge of documentation of https://fluidtypo3.org/viewhelpers/flux/development/Grid/ColumnViewHelper.html#arguments
04:01:05 <jmverges> I think that could be great to have this in somewhere: <flux:form.variable name="allowedContentTypes" value="fluidcontent_content" />
04:02:23 <bjo3rn> ...or am I missing the point here?
04:03:30 <bjo3rn> what are you trying to achieve? those variable viewhelpers do exist.
04:03:56 <jmverges> I don't know, I'm creating like a workflow for creating elements: First you need to choose between FCE A and FCE B and the once that one of them is added you can create C,D,E,F and then you can create G,H, etc
04:05:41 <jmverges> so in Page doktype Layout, you can only introduce FCC Container. Into FCC Container you only can Introduce Row, Nav, ect, and in those elements then you can insert Text,Image or Menu (for example)
04:15:48 <bjo3rn> meh, yes. just found it. https://github.com/FluidTYPO3/documentation/blob/rewrite/3.Templating/3.2.CreatingTemplateFiles/3.2.5.Grid.md
04:47:35 <jmverges> I was taking a look to: https://github.com/FluidTYPO3/documentation/issues/40 what does it do options="{preview: {mode: 'append')}"> with modes being either append, prepend or none. ?
05:52:40 <FT3BOT> Issue 40: Chapters about previews must be updated https://github.com/fluidtypo3/documentation/issues/40
05:53:02 <bjo3rn> do you want to work on that? otherwise I'd take it.
05:57:38 <jmverges> bjo3rn, I don't know about previews
05:58:20 <jmverges> bjo3rn, could you explain me what should I do with the PR? other commit appliying the changes that you said or fix my first commit? (I don't know how to do the second)
05:59:04 <bjo3rn> I'd prefer amending: update your commit, amend the changes and force push.
06:00:03 <bjo3rn> yes. simple to the changes locally. commit again with --amend (https://www.atlassian.com/git/tutorials/rewriting-history/git-commit--amend/) and force push git push --force
15:18:30 <Akii> NamelessCoder: are you coming to t3dd?
19:00:31 <Outdoorsman> fluidbootstraptheme has a content element called ImageGallery. Currently it forces every image to be square in development version :(
19:09:10 <NamelessCoder> Outdoorsman I think the boostrap gallery component thingie expects that, but I'm not sure...
19:14:20 <NamelessCoder> as usual, the best experience with ft3 extensions is on the latest stable core
19:16:34 <Outdoorsman> Sigh... true. But I run into issues and then end up going back to the dev branch. In the end it seems that I'm spending more time debugging than getting work done. If that's what I did for a living that would be fine ha ha.
19:18:51 <Outdoorsman> Right now I'm making a website mobile friendly. I create a four column row in fluidbootstrap theme and try to drag the content elements into it and they disappear. So I've spent much of today recreating each element in the columns and then deleting the old ones... quite time consuming for the amount of content on this website.
19:19:03 <NamelessCoder> for what it's worth, your input also helps both us and other users - and we very much appreciate that!
19:19:36 <NamelessCoder> branch:development involves a bit of "caveat emptor" but the feedback we get is really invaluable
19:20:41 <Outdoorsman> I'm slowly getting better at submitting pull requests too I guess. I'm just not familiar with workflow there yet.
19:20:57 <NamelessCoder> if you did not know already: any elements that, for whichever reason, lose their relationships, you can find in list view and in the tab "Relations" you *should* be able to select the right content area name if that's the relation that was lost.
19:21:58 <Outdoorsman> When that happens, I go to list view click cut and then paste back into somewhere that it will show... the column it came from, etc.
19:22:35 <NamelessCoder> ah yes that too should solve the problem
19:23:18 <Outdoorsman> Sounded like there were still issues with 7.x that were not worked out yet so am holding off a bit longer.
19:23:41 <NamelessCoder> most of my attention on the drag-n-drop stuff was focused on 7.1 but I didn't expect the changes to affect 6.2
19:23:43 <Outdoorsman> ...issues with fluidbootstraptheme, and a few of the FluidTYPO3 extensions.
19:25:06 <Outdoorsman> I saw this issue so haven't said anything thinking it was just being worked on: https://github.com/FluidTYPO3/flux/issues/573
19:25:32 <Outdoorsman> Is that the one that's likely the culprit?
19:27:17 <NamelessCoder> honestly I'm not sure what the state is. The issue there was an attempt to make sense of the remaining cases, but how much of it has been solved by other efforts is unknown (at least to me)
19:28:01 <NamelessCoder> what I do know is that the drag-n-drop works on this 7.1 testing setup including some of the cases that didn't when I last looked at the issue in the link
19:28:43 <NamelessCoder> I haven't gone into translation behavior on 7.1 yet
19:32:18 <Outdoorsman> So is this the ImageGallery they were trying to imitate?
19:36:45 <NamelessCoder> again not sure, but I *think* the aim is to only include the bootstrap code components (and only those that actually make sense as content)
19:37:16 <NamelessCoder> so I don't think it's that gallery they emulate - I'd expect it to be a core bootstrap component that's basically just markup and very simple
19:37:46 <Outdoorsman> I just didn't see it in the core... I'll look some more, you don't need to do that.
19:39:30 <NamelessCoder> there's the media list component - that one I know expects square imgs
19:39:51 <Outdoorsman> Different name... maybe that's it... I'll look
19:39:54 <NamelessCoder> there's also some sort of image grouping containers, but not a gallery as such
19:40:20 <NamelessCoder> and if it's those image things then I am pretty sure that any aspect ratio is supported by bootstrap itself
19:40:37 <NamelessCoder> at least, I used those in a project where the image size couldn't be trusted
05:26:27 <martin587> hello together, i use the viewhelper v:asset.style to include a css file, how can i add the attribute media, for example media="print" to the output. Thanks for your help!
06:18:41 <Torsten85> hey, I've added flux / fluid content to my typo3 v7 instance and all is working as expected except drag & drop in the page module. I guess flux is not yet fully compatible or is it a bug?
07:34:43 <Denyerec> Anyone in here much good with tt_news and realURL ?
07:35:04 <Denyerec> I've about €75 here as a bounty for anyone who can help fix up some insane URL duplication crap on a site of mine :(
08:18:12 <featdd> I'm clicking through news and see no duplications
08:20:10 <featdd> theres item and article which is kind of redundant, you meant that?
08:22:48 <featdd> when its about item is think you used postVarSets, which sets this annoying type title "item", you can avoid that by using fixedPostVars
08:23:07 <featdd> but then you have to set the pageUid in the realurl config
09:05:37 <featdd> Denyerec: item is the name of the page, you have to rename it in article or something the article in path is the type title from postVarsets
09:06:50 <featdd> if you use fixedPostVars you can avoid the "article" and make 2015/march bypass, archive has to be vconfigured as a seperate page too
09:20:21 <Torsten85> Could someone explain to me why the Flux ContentProvider only triggers on "list" CTypes? That seems wrong to me because it won't trigger on drag & drop.
05:46:59 <k4mi> Hey there :). I am trying to build a proper onepage design with fluidtypo based on bjo3rn's tutorial. The problem is c:content.render doesn't render any of my subpages content. Not even if I directly pass directly a pagUid, any ideas ?
07:11:44 <Guest|5028> Hello, I have a gallery content element and I want that each time the site is reloaded the order of the array is randomly generated. I tried it with a ViewHelper on my own, but the array will be cached after the first load of the page. Only if I clear the cache and reload the order is different.
07:35:12 <Guest|98763> Morning everyone. It is possible to store the data from a flux field in one of the default fields of tt_content i.e in bodytext?
08:01:50 <Torsten85> Hey.. what's the current status concerning compatibility with TYPO3v7?
09:12:04 <Guest|5028> Is it possible to turn off caching for certain content elements created with fluidcontent?
09:14:53 <NamelessCoder> yes and no, Guest|5028. You can make the template or parts of the template not cache by using v:render.uncache, but the controller action itself cannot be switched from USER to USER_INT. If you must have the controller included as uncached, I suggest creating a small Extbase plugin to do that.
09:16:55 <NamelessCoder> the other, more crude way, is to force the entire page to not cache via a custom content/page controller
10:20:43 <NamelessCoder> if you can, check that your DB was updated - tt_content needs indexes on tx_flux_column and tx_flux_parent, it's possible those weren't added
10:21:21 <NamelessCoder> other than that, yes, flux 7.1.2 is quite a lot slower than flux 7.2 will be - several factors
10:22:05 <NamelessCoder> we are so close to release that you may want to risk the development versions and do the migration now - we don't expect any more API changes before release.
10:22:51 <Rabe69|43669> can i update to this version without updating fluidpages/fluidcontent?
10:23:08 <NamelessCoder> no, - and you'd also need fluidcontent_core updated
10:23:16 <NamelessCoder> are you using custom templates or fluidbootstraptheme?
10:24:34 <NamelessCoder> there is very little migration to be done for flux 7.1.2 -> flux 7.2. If you used fluidbootstraptheme there's a branch compatible with flux 7.2 - but since you use custom elements you may need to change a few things, depending on the amount of deprecated viewhelpers you used.
10:25:06 <NamelessCoder> main thing: use a provider extension, make sure you register it with a Vendor.ExtensionKey format if you use controllers - and use namespaces.
10:25:32 <NamelessCoder> most important change: templateRootPath etc are deprecated - use templateRootPaths (plural) instead
10:25:55 <NamelessCoder> (still supported for now, but you should take this opportunity to change it if you upgrade)
10:26:38 <NamelessCoder> unfortunately the release notes aren't drafted yet or I'd send them to you. Hopefully those hints plus this link are enough: https://fluidtypo3.org/blog/news/coming-changes-in-flux-72.html
10:26:47 <Rabe69|43669> tt_content has the indexes
10:27:03 <NamelessCoder> okay - I suspect the main problem here is the template parsing/compiling
10:27:26 <Rabe69|43669> named index_fluxcolumn, index_fluxparent and index_fluxparentcolumn
10:27:27 <NamelessCoder> depending on your cpu+hdd speeds, that particular operation may slow things down a lot
10:27:53 <NamelessCoder> yep - sounds like your DB has the optimisations needed. We added those a while back.
10:28:14 <Rabe69|43669> i have the problems on two different maschines
10:28:37 <Rabe69|43669> lokal in my docker container
10:28:41 <NamelessCoder> the optimisations in flux 7.2 include actual enabled support for compiling templates and has removed several hundreds to thousands of dependency injections per page load (in BE particular)
10:29:08 <Rabe69|43669> and on my server, which should have the power
10:29:15 <NamelessCoder> are you using NFS mapping or something for your typo3temp? I have it from xaver that using a tmpfs for this *greatly* speeds things up, also with new flux
10:31:06 <NamelessCoder> as are a lot of other core caches
10:32:16 <NamelessCoder> there could be a lot of reasons why it bottlenecks - but I'm sure flux@development is going to speed things up to at least triple speed after first hit
10:32:32 <NamelessCoder> the more complex your templates, the greater the boost
10:33:11 <Rabe69|43669> is it not possible to configure this to another (e.g. redisBackend)?
10:33:27 <NamelessCoder> absolutely, it just has to support FS based inclusions
10:33:44 <NamelessCoder> the internals of TYPO3 caches that assume file caching will simply include() the file
10:34:15 <NamelessCoder> in other words, it writes PHP as files and the backend must support this
10:35:09 <Rabe69|43669> so, i will first update to flux 7.2
10:35:11 <NamelessCoder> btw I have a testing setup here (fluidbootstraptheme) on typo3 7.1 with flux@development. 16 FCEs on page, 600ms load time in BE.
14:15:31 <jonasjo> i'm very new to flux, but i really like it :-)
14:16:25 <jonasjo> is there some kind of tutorial around for how to create custom content elements and their backend forms?
14:19:55 <jonasjo> i can not manage to get a contentelement show up in the frontent. not even the example element provided in the example ext (builded with "site") does show
14:20:48 <jonasjo> i mean, it should get rendered "I am a content element! My template file is EXT:mysite/Resources/Private/Content/Example.html." right?
14:22:22 <jonasjo> it just renders the headline in case i give it one
14:33:27 <Rabe69|43669> @NamelessCoder: The new flux version (7.2.0) renders backend view in half time :-)
14:37:44 <jonasjo> i just installed fluidbootstraptheme but the same problem. it just renders headers from fluid content elements. no body. i seem to miss somthing hard :-(
17:39:39 <jonasjo> no one? i'm kinda desperate here :-/
18:55:45 <jonasjo> oooook, i got the error i guees
18:56:45 <jonasjo> you need to copy or add AdditionalConfiguration.php
18:57:25 <jonasjo> oh man, this wans't clear to me. took me a few hours. well whatever thx anyway for those great extensions
09:51:40 <NamelessCoder> benefit: each section is cached separately which means you touch much less code when rendering, compared to the switch. Worst of all f:switch isn't compilable on 6.2
09:51:45 <drlimbo> i didnt know section="Content{ContentLayout}" will work
09:52:25 <NamelessCoder> also works for Layout but there, you won't be able to use any ViewHelpers to generate the dynamic parts of the Layout name - it is parsed quite differently.
09:55:16 <drlimbo> i created a flexible element, and added some Text in the Backend in the default Title-Field
09:55:42 <drlimbo> is there a way to hide the title and render this in my FCE as a h2 or to render it default as H2 instead of H1?
09:56:07 <drlimbo> i saw the type:hidden select, but the users will always forget to set this
10:51:31 <k4mi> Hey, I have question about v:content.resources.fal and the record argument. If I for example use record="{uid: '8'}", I get a perfect result. But if I want to get all the records with pid 10 ( I thought the argument should be record="{pid: '10'}"), I dont get any results.
10:52:02 <k4mi> (bear with me if I totally miss the point, just started yesterday with typofluid extensions)
10:56:57 <NamelessCoder> k4mi the "record" argument expects the database record that has the relations to FAL objects
11:04:20 <k4mi> Ah okay,thank you. Kinda makes sense :)
11:15:06 <Guest|39353> Hey guys. Ive been here some time ago with the following problem:
11:15:10 <Guest|39353> "Once i add the enabledControls param the error appears. If i leave it empty ("{}") or dont add it it works fine (i need the delete option as the hide option actually doesnt work)"
11:15:37 <Guest|39353> just fixed it by writing a new viewhelper extending the inline viewhelper
11:15:43 <Guest|39353> setting the enabledControls in php
11:26:23 <mrboe> @NamelessCoder here are teh files
13:38:40 <Outdoorsman> I want to commit more things on Github but need some help to understand the process.
13:40:26 <Outdoorsman> If I fork for instance fluidbootstraptheme on Github and time goes by, how do I merge my fork just locally so it is caught up to the most recent changes on the upstream?
16:37:41 <Outdoorsman> jonasjo check out some code examples here. Many of them are fancy ways of doing thing but it could give you some ideas if not what you're looking for. https://fluidtypo3.org/library/code-examples.html
16:40:30 <jonasjo> i saw those, but if you are really new to flux (and fluid) the fancy part kinda is the problem ;)
16:41:40 <jonasjo> in the mean time i found https://worksonmymachine.org/blog/a-guide-to-menu-rendering-with-fluidtypo3 which kinda looks like what i was searching for :)
16:42:34 <Outdoorsman> Actually I know about that. That's what I learned my first menu from too.
16:43:49 <Outdoorsman> He did a nice job. What I didn't realize when I read that right away is that you can have an automatically generated menu with just a few lines. <v:page.menu useShortcutData="TRUE" />
16:46:14 <Outdoorsman> Notice that <v:page.menu ... /> is a self closing tag. If you use it to wrap manual rendering you get the joy of doing a lot of things manually... very manually in some cases. <v:page.menu> ... </v:page.menu>
16:51:30 <jonasjo> i guess i just play around with it a little
16:51:55 <Outdoorsman> Once you go through the pain of writing a manually, you can use and reuse the code and it's not quite as bad as I first thought. Nevertheless, I'm still convinced that there a LOT that could be done to make things easier in auto mode.
16:52:51 <Outdoorsman> I'd love to see quite a few more parameters so we don't have to write custom stuff so often just to get a simple bootstrap or foundation menu working (a common case).
16:53:27 <jonasjo> i think i know what you mean now with "manual"
18:40:13 <jonasjo> i got a question regarding v:page.menu anyone around?
18:58:20 <jonasjo> shouldn't v.page.menu render a whole menu, like with all subpages and all? (without shortcuts, ok)
19:24:02 <NamelessCoder> if you can at all make do with automatic rendering, it is preferrable. It's faster and will render all the levels you designate
19:24:31 <jonasjo> that may be the problem i had the whole time. i thought i could render the whloe pagetree with v.page.menu
19:39:28 <NamelessCoder> if you used <v:page.menu ... /> as tag, you should expect to see N levels of menus if all menus in the tree are visible in menu
19:40:05 <NamelessCoder> there's a diff between <v:page.menu>...</v:page.menu> and <v:page.menu /> if you have whitespace inside the tag
19:40:40 <jonasjo> so just to be clear here. in manual mode i just have one level. but this level should include all pages on this level, right?
19:57:34 <NamelessCoder> last chapter of https://worksonmymachine.org/blog/a-guide-to-menu-rendering-with-fluidtypo3 is relevant here.
19:58:36 <NamelessCoder> to make things clear: when you use manual rendering, expandAll and levels has no meaning (you'll be controlling that by how many times you call v:page.menu/v:page.menu.sub inside
19:59:55 <NamelessCoder> you would now expect that if you remove expandAll, levels and entryLevel parameters from the menu, that it will render all your pages below page UID zero but only the first level of pages
19:59:58 <jonasjo> but, the snippet from above, shouldn't it render ale the three pages ?
20:00:13 <NamelessCoder> I suspect it only renders the current page because of entrylevel 1
20:01:53 <NamelessCoder> yes - and to make the viewhelper absolutely aware what you want, add the as="menu"
20:02:53 <NamelessCoder> this will avoid unexpected behavior if your menu output is completely empty (e.g. no items exist). Because you have no custom HTML inside v:page.menu, the content could be detected as empty. With the "as" argument that cannot happen; it always assigns the template variable and renders tag content, never falling back to auto rendering.
20:09:27 <NamelessCoder> little bit creepy, honestly. I haven't seen the viewhelper do stuff like that unless there was something horribly wrong with the loop used in the template - and yours is fine
20:09:46 <NamelessCoder> I wish I could reproduce the problem :/
20:09:57 <NamelessCoder> hate it with things don't make sense
20:11:15 <jonasjo> yeah, mtt, too. that is why i was so unyielding :-/
20:11:23 <jonasjo> doens't want to bother at all ;9
20:11:43 <jonasjo> i'll set up a new instance and let you know
20:12:33 <NamelessCoder> thx - and if that one also fails I think it's time to send me a dump of the instance with all files included, plus some added info about your php version.
20:12:47 <jonasjo> thank you very much. a least i know i'm not crasy :-)
20:12:49 <NamelessCoder> in the faint hope that lets me reproduce it
20:13:10 <NamelessCoder> I'm hoping this was some crazy fluke - like I said, I've never, ever seen this happen and I've seen pretty much everything in Fluid ^^
20:29:17 <NamelessCoder> if you're not constrained by project dependencies, and if you have time, please try the exact same thing you're doing, but with a 7.1.0 core. Mean while I'm trying on 6.2.9 (was on 7.1.0 and 6.2.10 before)
20:35:26 <NamelessCoder> something is definitely wrong here on 6.2
20:37:50 <jonasjo> i will. but shouldn't i test on 6.2.11 ?
20:37:59 <jonasjo> i have some time on my hand :-)
20:40:46 <NamelessCoder> ah yes that was released today right?
20:44:06 <jonasjo> it renders nothing with <v:page.menu />
20:44:20 <NamelessCoder> I'm beginning to feel your pain here
20:44:45 <NamelessCoder> my attempts have no output whatsoever. Internally, the v:page.menu uses PageSelect and this class consistently returns an empty value
20:44:58 <NamelessCoder> now, to track down the reason for this crappola
20:45:06 <jonasjo> i kind of feel relieved, sorry ;)
20:45:12 <NamelessCoder> I bet it's some undoc'ed SQL change...
20:45:20 <NamelessCoder> hehe I've been here before ;)
20:47:06 <jonasjo> i'm more the FE person though ;)
20:50:51 <NamelessCoder> this is the generated query here - it returns zero results but no errors: SELECT * FROM pages WHERE
20:50:51 <NamelessCoder> pid=2 AND pages.deleted=0 AND (fe_group = '-1' OR fe_group LIKE '-1,%' OR fe_group LIKE '%,-1' OR fe_group LIKE '%,-1,%' OR fe_group = '0' OR fe_group LIKE '0,%' OR fe_group LIKE '%,0' OR fe_group LIKE '%,0,%' OR fe_group = '' OR fe_group = '0') AND pages.deleted=0 AND pages.t3ver_state<=0 AND pages.pid<>-1 AND pages.hidden=0 AND pages.starttime<=1426726140 AND (pages.endtime=0 OR pages.endtime>1426726140) AND (pages.fe_group='' OR pages.fe_group
20:50:51 <NamelessCoder> IS NULL OR pages.fe_group='0' OR FIND_IN_SET('0',pages.fe_group) OR FIND_IN_SET('-1',pages.fe_group)) AND doktype IN (1,3,4,7) AND nav_hide=0
20:54:48 <NamelessCoder> and prepare to kick my ass mentally :/
20:55:24 <NamelessCoder> EXT:site does indeed write the pages like it must, but does it save them with doktype=0 and is this doktype not recognised? I do believe so, yes.
20:55:45 <NamelessCoder> saving the pages once sets doktype=1 and the pages pop up
20:56:00 <NamelessCoder> basically, it solves everything here...
21:01:40 <NamelessCoder> give it an hour, tops, then refresh EM's list of extensions. EXT:site should pop up in 1.3.3 which creates pages with doktype=1
21:01:53 <NamelessCoder> thanks for not giving up btw ;)
21:01:58 <jonasjo> oh cool,which band? i belevie you'r into metal, right? me, too ;)
21:07:04 <NamelessCoder> sleep tight, try the site thing tomorrow and all will be well :) I'll think about putting a page menu into the templates that are created, plus some other basic stuff
21:07:06 <jonasjo> had to give it a few spins, but now i'm really diggin it
21:07:34 <NamelessCoder> learning curve can be a bit steep but once you remember, should make most of your FE work a lot faster ;)
04:31:24 <TYPO3ua> I have code: {items.1.item.image) .. {items.2.item.image) .. {items.3.item.image)
04:31:35 <TYPO3ua> I need this ... {items.{itemIteration.cycle}.item.image) but this is not work ...?
04:31:42 <Guest|37930> MyNameContentController seems to be ignored. ContentController leeds to the error... Cannot redeclare class FluidTYPO3\\Fluidcontent\\Controller\\ContentController. I'm confused. ;)
04:33:21 <Guest|37930> ContentController with own namespace seems to be ignored too.
04:49:57 <Guest|33596> Hello! I've just update all of my FLUID TYPO3 Ext. After changing some code. everything works ... unfortunately not all. my flux elements are totally confused. I add the new "FCE1" and after save and close, the element change to "FCE2" f.e. I think there's a problem with fluidpages, because my Backend Layout didn't show their names like "left colum
04:49:57 <Guest|33596> n" `<flux:grid.column colPos="0" name="Slider" colspan="2" />` or is it a problem with flux?
04:53:33 <mrboe> @Guest|33596 the dev-branch is fixed
04:53:56 <Guest|33596> I try it with a new Installation TYPO3 7.1 and the new FLUID TYPO3 Package. The same. I don't see the names of the backend layout columns like 'main' or 'right' `<flux:grid.column colPos="0" colspan="3" name="main" />`
04:55:18 <Guest|38326> The dropdown values for content type and column only show me an INVALID VALUE
04:55:40 <Guest|38326> the column select shows also the number 18181
04:56:29 <Guest|38326> well, if I add content to the fluidcontent grid, everthing works fine, but when I want to change the content type, there's just this Invalid Value
04:58:04 <Guest|33596> hey mrboe, so I'll pull the development branch from fluidcontent. I will try it .. and hope the problem is also fixed at my instance
05:01:13 <Guest|37930> Hi. I have a question about an own Flux ContentController.
05:01:17 <Guest|37930> in the documentation it's written the Class should named ContentController. Do I have to adjust this?
05:01:24 <Guest|37930> MyNameContentController seems to be ignored. ContentController leeds to the error... Cannot redeclare class FluidTYPO3\\Fluidcontent\\Controller\\ContentController. I'm confused. ;)
05:01:29 <Guest|37930> ContentController with own namespace seems to be ignored too.
05:06:10 <Guest|33596> Hi <mrboe> . yes. my problem is also solved. the name of the backend layout columns still not there, but here i can wait for a new update of fluidpages ... the problem with the FCEs is done. thanks a lot
05:15:14 <Guest|38326> Well that was not the problem. I still have the INVALID VALUE options in content-type and content-column dropdown. The flux object is <flux:form.content name="foo" label="bar" />. do I have to use another element instead?
05:23:10 <pedda> i'm facing a behaviour, i thought it was already fixed, where assets via ts and assets via fluid are not merged correctly
05:23:28 <pedda> i pulled the latest version of vhs in my project
05:25:20 <pedda> when i debug $assetSettings in AbstractAssetViewhelper in Line 301 i get a debug output for each asset i included via fluid
05:25:53 <pedda> those 2 which were included via ts are listed within each debug output as if they were properties of each asset included via fluid
05:26:22 <pedda> as if the asset merging of ts based and fluid based assets would miss the right level of array items
05:30:02 <pedda> anyone facing the same behaviour ?
05:30:59 <pedda> i realized there are the ts based assets guys and the fluid based assets guys, i belong to the second group, as i want to unclude assets only if a certain fce is used for instance
05:31:11 <pedda> but then if i use extensions with ts based assets things get strange
05:45:50 <patricktzzz> hi.. are there any notes for updating to fluidcontent 4.2 ?
05:46:00 <patricktzzz> because after updating, i can't choose the Fluid Content type any more
05:52:41 <pedda> patricktzzz did you upgrade flux also ?
06:04:05 <patricktzzz> yes, i updated all extensions in extension manager (flux, fluidpages/fluidcontent)
06:04:06 <braguzz> ext manager and language gives me 'Version number in composer manifest of package "fluidcontent_bootstrap" is missing or invalid'
06:24:20 <braguzz> I've lauched the 'update extension list' and ... boom!
06:25:21 <pedda> braguzz: I have not access to ext manager :( <- ??? if you can do thid: braguzz: I've lauched the 'update extension list' and ... boom!
06:32:25 <mrboe> if you want to use TER releses from yesterday you have to switch to fluidboostraptheme banch 2.0 (not stable yet) after you switched from fluidcontent_bootstrap to fluidboostraptheme
06:32:57 <mrboe> you also have to use fluidcontent dev branch bacause the TER version has a bug
07:10:41 <Kalypso63> i just a have a little question with the new version of fluidpages (3.2.0).
07:12:28 <Kalypso63> If have 2 templates (Landing pages & standard) and i just set my root page with pages layouts (rootpage : Landing pages & all child : Standard)
07:14:20 <Kalypso63> but when i want to edit and set some options in my flux configuration on child page, the configuration is not goof. This i my home page configuration which is load
07:15:09 <Kalypso63> i see some new features on ConfigurationService.php and function resolvePageProvider
07:15:58 <Kalypso63> if the field tx_fed_page_controller_action is empty the configuration which is loaded is not the main conf but sub conf
10:16:22 <denyskoch> is there a way to change page templates from plugin controller? I have 2 fluigpage templates, 'Default' and 'Default with Sidebar'. On the page there is plugin, which need to switch the Template of the page from 'Default with sidebar' to Default.
10:26:59 <pedda> @denyskoch i'd rather consider a 100% width plugin layout and make the plugin template handle the rendering of the sidebar.. vioa partial or sth
10:29:39 <pedda> so you can teach your plugin to load a partial if plugin state = whatever
10:30:19 <pedda> or use view (if necessary) and move the somext-plugin-template-file to your provider extension, to keep the plugin reusable among projects
10:52:15 <pedda> you assign landing page templa to your root page, all other child pages get Standard page layout assigned
10:52:44 <Kalypso63> with the new version of fluidpages (3.2.0), if you choose on page layout configuration the option parent decides, the page load the subconfiguration instead of page configuration
10:53:00 <pedda> if you try to set flux options of standard page layout (so setting those for a certain child page of landing page) the values for landing page are set instead ?
10:53:49 <Kalypso63> yes, flux options are not used
10:54:10 <pedda> flux options are used, but of a different file than expected!
10:54:18 <Kalypso63> i think is due to resolvePageProvider function
10:54:37 <Kalypso63> the function test if the sql field tx_fed_page_controller_action is empty
10:54:42 <pedda> PageProvider = PageController of your provider extension
11:02:54 <pedda> sorry Kalypso63 never experienced your issue, neither do i use page flux options nor do i have a project with fluidpages 3.2 running
11:04:35 <Kalypso63> I upgrade fluidpages yesterday but is on developpment staging. I just see that anathor person have the same problem and push it on issue project. So just wait...
11:26:29 <pedda> NamelessCoder you have a minute ?
11:31:04 <NamelessCoder> there we go - sorry about the wrong tag
11:31:24 <NamelessCoder> pedda if it is only a minute, sure
11:31:41 <pedda> did you ever face ts based and fluid based assets not merging correctly?
11:32:31 <pedda> imagine ext:A assigning assets via TS and Ext:B relying on an Assets.html partial where assets are included by the help of viewhelpers
11:33:00 <NamelessCoder> if one context is cached and another is not, merging is prevented
11:33:12 <NamelessCoder> you can still use dependencies but for technical reasons the files cannot be merged
11:33:22 <pedda> when i debug $assetSettings in AbstractAssetViewhelper in Line 301 i get a debug output for each asset i included via fluid
11:33:31 <NamelessCoder> other than that no - they should transparently merge together
11:33:46 <NamelessCoder> TS assets don't go through the ViewHelper
11:34:04 <pedda> each of those outputs contains the ts based assets as if they would be properties of the currently debuged output
11:36:05 <NamelessCoder> if your assets with the same name exist in both places then yes: those defined in TS are applied on top of those defined in Fluid, those that don't exist in Fluid are created directly from the TS
11:36:08 <pedda> while mainCss.path is still valid
11:36:59 <pedda> there are two assets at the bottom in the debug output
11:37:22 <pedda> if this is expected, i'm fine with this, as everything works fine.. but i was wondering if this is wanted behaviour
11:39:13 <NamelessCoder> the intention is that TS has the "final word" over any other assets. The logic first loads all the assets that were NOT defined in TS, then loads the TS and applies attribute changes to any assets that were previously defined (so the result becomes a combination of attributes you set in fluid/php, overwritten selectively with those you set in TS). Finally, any assets that weren't already created in fluid/php are created as php assets based on the
11:45:27 <pedda> which is included via static ts in backend
11:45:40 <jost> Hi... just updated to flux 7.2.0... Now my template for <flux:widget.grid/> does not work any longer, because that viewhelper has been made useless. How do I influence backend preview rendering now?
11:46:03 <NamelessCoder> yeah but what is the location you used? plugin.tx_vhs.settings.asset.xyz.path = ... and so on?
11:47:39 <NamelessCoder> yes: it is expected, albeit a bit confusing.
11:48:00 <NamelessCoder> the reason is that your array contains those entries that weren't picked out because they had corresponding fluid/php assets.
11:48:20 <NamelessCoder> ...and we merge the settings internally in a way that those values end up there
11:48:47 <NamelessCoder> shouldn't hurt anything at all and they should still pop up as proper assets - it's just the entries that are redundant/inherited
11:50:02 <NamelessCoder> I suppose this can be avoided by checking asset attributes against the array, only transferring those array values that are named like asset attributes
11:50:25 <pedda> well .. there is no bad behaviour
11:53:18 <NamelessCoder> I'm not *that* sorry. Was working on a FAL driver...
11:54:26 <drlimbo> someone has an idea, why there is an "<p class="bodytext"></p>" before the content when i show RTE-Content with <f:format:html>? - in the RTE-Source it starts with a H2
11:55:07 <NamelessCoder> you probably add a line break in your template, drlimbo
11:55:15 <NamelessCoder> {value -> f:format.html()} is always safe
11:56:14 <NamelessCoder> then the RTE must contain the line break
11:56:33 <NamelessCoder> is H2 allowed by your RTE proc func?
11:56:49 <NamelessCoder> if not, that'd be removed and you may have an empty line
11:57:03 <drlimbo> yes, it also renders the H2 in the frontend (but add the empty p tag before)
11:57:36 <NamelessCoder> try checking the RTE in source mode. I've sometimes had those starting spaces and the RTE couldn't delete them with backspace/del
11:57:59 <drlimbo> i checked in source-mode, theres nothing before the h2
11:58:55 <drlimbo> also after saving the rte-field in backend, it starts with a h2 -> the empty p-tag is added while rendering the frontend i think
12:00:40 <NamelessCoder> hmm - in that case I'm out of guesses
12:01:38 <drlimbo> lib.parseFunc_RTE.nonTypoTagStdWrap.encapsLines.addAttributes.P.class > <- removes the class="bodytext"
12:02:36 <NamelessCoder> but why it adds it in the first place... dunny, sry
13:35:37 <JustAPoring> I looks like the lack of page.bodyTag makes it default to a plain <body>|</body>
13:41:38 <gbod> JustAPoring: What do you want to achieve?
13:42:41 <JustAPoring> gbod: I wanted the complete template in html files for ease of use - I am currently working on a newsletter template which means I have to do dirty stuff like inline styles on the body tag.
13:43:11 <JustAPoring> In the end it doesn't matter that much to me if I have to set it in TS, I just thought it would be nice to have everything in one template
06:32:35 <toph> Hi everyone. I upgraded my FluidTYPO3 extensions from GitHub (master branch) and now I'm just getting a fatal error: Call to a member function resolvePrimaryConfigurationProvider() on a non-object in typo3conf/ext/flux/Classes/Service/FluxService.php on line 373. What do I need to look at?
06:38:30 <Kalypso63> have you upgrade fluidpages too (version 3.2.0) ?
06:39:14 <toph> yes. did a fresh git clone on both.
06:39:44 <Kalypso63> clear cache system via install tool and compare database too
06:42:12 <toph> Oups, rookie mistake. Forgot to compare database. My bad.
06:42:40 <toph> However, now I'm getting: Uncaught TYPO3 Exception
06:42:40 <toph> #1: PHP Warning: strpos() expects parameter 1 to be string, array given in typo3conf/ext/flux/Classes/Utility/ExtensionNamingUtility.php line 27
06:43:55 <braguzz> I've update some ext but I got this Could not analyse class:Tx_Vhs_ViewHelpers_Extension_Path_ResourcesViewHelper maybe not loaded or no autoloader?
07:05:35 <NamelessCoder> you're rendering your menu manually but nowhere are you defining any <ul> or <li> tags, you only define a link that should be generated and this link will always be an <a>
07:05:45 <NamelessCoder> if you want the ul/li there, you have to add them
07:06:33 <NamelessCoder> the other thing is you should consider not using <f:link.page> to render the page link. In {subItem} you will have the {subItem.link} property which contains a pre-rendered link created exactly the way f:link.page would do it.
07:06:43 <NamelessCoder> (you can save a viewhelper call so you should)
07:08:27 <NamelessCoder> last: if you expect an ul > li > a structure and do not need any class names (from your example it doesn't look like you do) then the automatic rendering of plain and simple <v:page.menu /> (levels>1) will create exactly that output (with some added css classes)
07:08:55 <NamelessCoder> if you expect a nav > a structure you can manipulate "tagName" and "tagNameChildren" on v:page.menu
07:09:15 <NamelessCoder> (the automatic rendering fits many cases but not all)
07:13:47 <Jomungand> i was reffering to https://worksonmymachine.org/blog/a-guide-to-menu-rendering-with-fluidtypo3
07:14:19 <Jomungand> btw, my nick before was jonasjo, we already talked about that ;)
07:15:16 <Jomungand> what else then instead of <f:link.page> ?
07:45:16 <Jomungand> ah, ok, i guess it is faster? or what is the advantage here?
07:46:26 <NamelessCoder> yep, faster because link is already built and you don't need to do that again
07:48:42 <toph> I have a new site with all the latest (master) versions from git and I'm using fluidcontent_core instead of css_styled_content. I have created a provider extension with a custom content object, which correctly gets picked up in the display. However, for some reason, only the header is rendered in the frontend. Any ideas?
07:49:40 <NamelessCoder> run the fluidcontent_core install/update script from EM, toph
07:51:49 <toph> Configuration and preview in the backend work fine. Just the rendering doesn't.
07:52:10 <NamelessCoder> if you want the FCC handling of header/wrapper rendering you'll need to either copy the Layout from fluidcontent_core, replace your Layout root path (if this is possible) or name your own Layouts in a way that you can add the fluidcontent_core layoutRootPath so it gets checked after your own layoutRootPath (plural names in TS array)
07:52:59 <NamelessCoder> the key here is: your Layout doesn't use v:tag and doesn't have the small conditions required to show/hide header and to render it with the appropriate H(n) tag
07:52:59 <toph> No, the header is fine. It's the content itself that's not rendered at all.
07:55:21 <toph> Here's my layout file (just the standard one, in my_provider_ext/Resources/Private/Layouts/Content.html): https://gist.github.com/potofcoffee/0f545c2f669616ffac88
08:38:18 <NamelessCoder> that, and load the static TS file from fluidcontent_core, should be enough to render everything correctly
08:38:55 <NamelessCoder> your problem could be that fluidcontent_core is rendering the Default.html template and not the fluidcontent plugin because of missing TS.
08:45:18 <Jomungand> in the New content element Wizard. how do i remove Text & Images since there is no element for that in fluidcontent?
09:24:02 <toph> All of this is set, TS is loaded, cache is cleared.
09:24:21 <toph> One tiny difference however: My AdditionalConfiguration.php says this:
10:17:54 <Jomungand> it was. an now it seems to be broken. also pages just get rendered if you save them. talked with @NamelessCoder about it already ;)
10:42:30 <Jomungand> well im gone. i will be back later :-P
11:09:43 <toph> @Jomungand: It actually does render quite a lot: All of the CEs defined in fluidcontent_core render finde. I also installed fluidbootstraptheme and the page templates from there render fine as well (menu, etc.)--not the FCEs, however.
11:16:29 <toph> Okay, I must be looking at some weird caching issue here -- cleared the cache dozens of times without success, and now, with no other changes, all of a sudden it works.
11:16:42 <toph> Go figure... Well, at any rate, thanks guys.
11:17:15 <Torsten85> Hey, just saw that flux ect. is now marked compatible with typo3 7.1 ... can anyone confirm that drag & drop ect. is correctly working?
11:18:04 <Torsten85> the ajax request issued by a drop action in typo3v7 seems to be very different from the way typo3v6 does this
11:23:22 <Kalypso63> Hi @NamelessCoder !! Have you got an idea or tips to resolve this issue https://github.com/FluidTYPO3/fluidpages/issues/239
11:24:38 <Kalypso63> ConfigurationService.Php -> resolvePageProvider() : the problem comes her
14:07:20 <Danny^^^P> Hi! I startet to migrate my templates to the latest version and Typo3 7.1. In my template I defined a backend layout with one column. But in Backend I see the default 4 columns. is this still a bug or have i missed something?
16:18:06 <Jomungand> can anyone point me to a working example of a manually rendered menu with at least three level using <:vpage.menu> ?
21:08:32 <Jomungand> is it by chance by mistake that 3.4 Using variables and 3.4.1 Form values are missing from the documentation on https://fluidtypo3.org/ ?
10:25:37 <opk> I'm trying to use vhs in flux and I can't get current CE
10:26:10 <opk> {v:content.info(contentUid: 7347, field:'sys_language_uid')} works
10:26:16 <opk> {v:content.info(field:'sys_language_uid')} does not
10:28:51 <NamelessCoder> opk if you're in a content template and have correctly transferred the variable, {record} is available and contains {record.uid} which you can feed to various content viewhelpers
10:43:48 <opk> maybe you could help with the displayCond problem.
10:45:29 <opk> I can't get it to work displayCond="{v:content.info(field:'sys_language_uid',contentUid:'{record.uid}')} == 0" or displayCond="FIELD:sys_language_uid:<=:0"
10:54:16 <NamelessCoder> if you need a very complex condition (note: arrays are now supported as displayCond in TCA) you can still <f:if> around the Flux component you want to condition
10:54:47 <opk> i'm truing to hide field's for translation
10:55:56 <NamelessCoder> displayCond should work for that but I'm not sure about the syntax given that this is in a flexform context - please check the almighty core TCA docs ;)
11:08:30 <NamelessCoder> well you can use VHS to define the string that becomes the displaycond - but the displaycond itself is treated by typo3 internally
11:08:53 <NamelessCoder> if you want to only rely on vhs, f:if around the field
17:14:32 <tv_sebastian> You're not allowed to use it within a flux:form
17:25:27 <NamelessCoder> you should be able, but may need arguments="{_all}" for everything to be appended correctly (or a new Form instance is created as ad-hoc parent Form in your partial and this Form can never be retrieved)
20:15:58 <Jomungand> just read your article regarding phoenix/nes @NamlesCoder
20:25:38 <Jomungand> thx for the hard work btw :-)
20:26:08 <NamelessCoder> Alex Schnitzler has the completely correct point: viewing neos/flow as experimental and R&D makes so much sense - it's what I touch in my letter about "taking the lessons learned from Neos and applying them to TYPO3" to paraphrase
20:26:55 <Jomungand> cutting of the weak parts and focus on one strong thing, too
20:26:56 <NamelessCoder> heh, you're welcome :) I was mostly proving a point about the decoupling having been drawn out needlessly for a long, long time. All it takes is willingness to sacrifice some of the TYPO3-ness about Fluid.
20:27:29 <NamelessCoder> I even did it once before - but that time, in a much less refined way
20:29:48 <NamelessCoder> are you from the US Jomungand? You're always on late and your English is good enough that I'd guess it ;)
20:39:20 <opk1> NamelessCoder > There was a way in templavoila to disable TOC fields from translation . Is there some way for flux/extbase for enabling inheritance for fields?
20:40:47 <opk1> ie. monitor in store. Different description in different languages but the same diagonal in all of them
20:41:15 <NamelessCoder> still undocumented, but see recent addition for flux:form option "translation"
20:41:48 <NamelessCoder> I can't decouple Fluid, write a FAL driver *AND* Flux 7.2 release notes on the same weekend :p
20:42:33 <Jomungand> if there is something i could do to improve the documantation, let me know. got some free time on my hand
20:43:48 <opk1> i must say that fluidtypo3 is the best thing that happen to typo3 since the sliced bread :)
20:44:25 <NamelessCoder> Jomungand be VERY VERY careful what you offer ;)
05:02:50 <braguzz> hi I've update some ext but t3 doesnt work anymore
05:03:43 <braguzz> in apache err I got PHP Fatal error: Call to undefined method FluidTYPO3\\Fluidpages\\Service\\ConfigurationService::getTypoScriptSubConfiguration() in ../ConfigurationService.php on line 123,
05:20:08 <braguzz> yes I've also delete typo3temp from shell
05:23:53 <beo6> mhh. sorry no idea then. i had a similar error but with my own extension. But it should work with the fluidpages etc.
05:28:35 <Edek> Hi, I would like to know if it's possible to add a marker inline with fluid configuration .. for example: <v:page.menu excludePages="{$exclude}" />
05:34:43 <beo6> Edek: you cann add them in your typoscript as variable
05:36:16 <beo6> or maybe page.10.variables.exclude = TEXT | page.10.variables.exclude.value = {$exclude}
05:40:10 <Edek> Thank you for your answer, I am completely new to VHS. Would this still include the tag in the example, or just add the tag to all page.menu items available?
05:43:45 <beo6> Edek: it would add the constant wherever you use {$exclude} in your fluid page template.
05:44:36 <beo6> Edek: but the template does not access the constant but the variable. So you could also just enter the value directly into the template variable
05:46:41 <braguzz> if I enable fluidcontent_bootstrap I can see backend pages, but I have errors in frontend
05:47:13 <braguzz> Could not analyse class:Tx_Vhs_ViewHelpers_Extension_Path_ResourcesViewHelper
06:04:04 <NamelessCoder> braguzz update your VHS namespace registration, legacy class usages are dead and gone
06:09:24 <braguzz> if I disable fluidcontent_boostrap I havent' this error
06:09:56 <NamelessCoder> yep, that ext is long deprecated - fluidbootstraptheme is the replacement (you may need their 2.0 branch, not sure if they released for flux 7.2 yet)
06:11:43 <braguzz> but without fluidcontent_boostrap I got I got PHP Fatal error: Call to undefined method FluidTYPO3\\Fluidpages\\Service\\ConfigurationService::getTypoScriptSubConfiguration() in ../ConfigurationService.php
06:11:59 <NamelessCoder> which file exactly is *calling* the method=
06:12:05 <braguzz> and even backend page doesnt work
06:13:30 <braguzz> Call to undefined method FluidTYPO3\\Fluidpages\\Service\\ConfigurationService::getTypoScriptSubConfiguration() in /data/museo/SpecialityDistribution/typo3conf/ext/fluidpages/Classes/Service/ConfigurationService.php on line 123,
06:13:43 <NamelessCoder> fluidpages is not upgraded
06:14:02 <NamelessCoder> the current version of that class does not contain 123 lines of code ;)
06:37:31 <Bendtsen> Hello - I have just installed the fluid extensions and a provider extension (auto generated) but I don't see the flux.grid in the backend. The frontend works as expected
06:37:56 <NamelessCoder> select "Fluidpages" as backend layout to be used in the "Appearance" tab of your topmost page
11:01:23 <benjamin_654> hi, arte there atm known problems with copy/cut & paste on development?
11:01:57 <benjamin_654> .. except the one with pasting a ce into itself ..
11:03:45 <benjamin_654> d&d works fine - but i cant put a ce into a fce via cut or copy …
12:12:29 <pbiendl_> Hey there, maybe this is the "more correct" channel to ask this :-): Can someone give me a Link to a Howto which describes how to make a IRRE-like Element in Fluid? Is this even possible?
12:13:19 <pbiendl_> Like a Tab-Group Element where you can Click "New Tab" and can then set the Content for the new Tab.
12:21:00 <benjamin_654> if i remember right they do have a tab-element.
12:22:21 <benjamin_654> i dont know if this EXT is also in TER - you should first look there for a stable version ..
12:24:30 <Guest|65002> hi everyone. Do i have the possibility to override just one Partial from fluidcontent_core? I know how to use my own Partials directory via constants, but to not have to merge all partials on an update of fluidcontent_core i would like to just use one file: Partials/Menu/SubPagesOfSelectedPages.html , because there i have to add an additional css c
12:24:30 <Guest|65002> lass for use with bootstrap. Thanks in advance.
12:24:58 <Guest|65002> (i wnat to override that in my own provider extension)
12:27:32 <NamelessCoder> Guest|65002 fluidcontent <1.1.0 then no. Above that then yes - just add your partial root path as second in partialRootPaths view config.
12:29:15 <Guest|65002> ok, but doesn't my extension has to have all partials in place? i mean i have own partials in use, but i expected to add one with same name as fluidcontent_core inside, but it isn't used
12:29:35 <NamelessCoder> not if you *add* the path instead of *replacing* the existing one
12:30:01 <NamelessCoder> see difference between partialRootPath and partialRootPaths - new versions of fluidtypo3 extensions support and assume the plural form
12:40:28 <pbiendl_> Hey, sorry for AFK :-) Thanks Benjamin, i'll look into it! :-)
13:08:49 <Guest|65002> btw, a general question. is fluidcontent_bootstrap extension suggested by you guys? i Just ask because i have often problems with installations from TER versions...
13:21:27 <Guest|65002> fluidbootstraptheme seems to work better out of the box from TER, but not sure what you suggest as "good practice" to have bootstrap components integrated into typo3
05:27:45 <gencha__> i'm having a bit of an issue with caching and i'm wondering what i'm missing here
05:28:54 <gencha__> i have a site on which i want to display a button that leads to the users profile. on that button, i want to show the user's name. if i just directly attempt to do that, the first user who ever hits the site will have their name cached and all future users see his name on the site
05:29:06 <gencha__> so i went ahead and used v:render.uncache instead
05:29:41 <gencha__> which seemed to work great, but we starting getting serious issues with the site soon afterwards (apache would segfault)
05:30:07 <gencha__> so, where exactly did i go wrong in this whole process?
06:07:52 <NamelessCoder> alright that should be perfectly fine
06:08:44 <NamelessCoder> if an update of php (+deps) doesn't fix this, I'm out of guesses. I've tried and failed again and again to track down segfaults any other way than rolling back commits one by one which takes quite a while
06:08:58 <NamelessCoder> on my install it was libpcre + preg_callback
06:09:15 <gencha__> but, in general, there's nothing wrong with my approach to getting the username into the website, is there?
06:09:36 <NamelessCoder> not exactly, it all depends what you ALSO render inside that uncached part
06:10:05 <NamelessCoder> if you truly only require the username and the link is always the same for all users, has no cHash etc... then there is a standard marker TYPO3 will replace after the page is built, which would be MUCH faster
06:10:23 <gencha__> but i was already doubting the whole approach and my understanding of _INT objects
06:10:44 <NamelessCoder> there is that and a few other markers (for logins) which are replaced completely separately from anything automaketemplate, fluid etc. and after delivering from cache
06:10:53 <gencha__> ah, yeah, i think you already told me about that marker in a github issue
06:11:09 <gencha__> but at the time i couldn't figure it out
06:11:19 <gencha__> and now we ended up here... in segfault hell
06:11:25 <NamelessCoder> it's been in typo3 ever since the first time we had felogin :)
06:11:52 <NamelessCoder> well v:render.uncached does create closures etc. but I've never seen it so severely fail
06:12:02 <gencha__> i've been working with typo3 for a couple of years now, but am still constantly surprised by how little i know about it
07:06:31 <erredeco> HI there. I have a menu of pages (with v:page.menu of course ;)); I would like to assign to every page a category (sys_category) and have the category title printed as class in the menu items.
07:06:50 <erredeco> Do you have suggestions? Thank you
07:42:56 <braguzz> hi all I'm trying to update vhs flux fluidpages fluidcontent fluidcontent_core
07:43:20 <braguzz> and everything seems ok but homepage
07:43:34 <braguzz> it gives me Template could not be loaded. I tried "/data/museo/SpecialityDistribution/typo3conf/ext/fluidcontent/Resources/Private/Templates/Content/Index.html"
07:46:31 <erredeco> I think it could be something like
08:50:02 <batjony> NamelessCoder: When browsing fluidtypo3.org, the link for "ViewHelper reference" goes to https://fluidtypo3.org/viewhelpers.html where the user is not able to select "Fluid" from the dropdown box, maybe is more correct the link to go directly to https://fluidtypo3.org/viewhelpers/fluid/master.html
08:52:02 <batjony> Currently if you want to see the Fluid view helpers reference, you should choose something else for example "fluidbackend" and then again "fluid"
09:32:20 <erredeco> it works well but now I want to add a category to each page (sys_category) and retrieve the category title to use it as a class in the menu
09:32:41 <erredeco> But here I am stuck... I can't figure how to do that... can someone help me?
10:05:44 <braguzz> HomePage of my site gives me Template could not be loaded. I tried "/data/museo/SpecialityDistribution/typo3conf/ext/fluidcontent/Resources/Private/Templates/Content/Index.html"
10:38:55 <Outdoorsman> I am porting many websites to FT3 right now and am finding it very cumbersome to have to recreate about 1/4 of all my conent elements on some content heavy websites because drag/drop and cut/paste don't work when nested.
10:39:12 <Outdoorsman> So... I'm just curious if there's there's anyone with the technical know-how looking at this issue for Flux... https://github.com/FluidTYPO3/flux/issues/573
10:47:26 <Jomungand> @erredeco i'm pretty sure this is not the right way to do it, but at least it works. you could do something like
17:03:52 <Akii> my problem is that I don't get the problem
17:04:05 <Akii> missing documentation.. it's not like this is new
17:05:21 <Akii> why not just bring documentation with the features..
17:05:42 <Akii> well, the chances are good that this letter will just be ignored like every other letter
17:07:26 <NamelessCoder> maybe not, maybe someone reads it and agrees. The T3A is renewed each year, for example. I'm not too invested either way because I see a great future for CMS
17:07:55 <NamelessCoder> last two years proved enough people want it
19:11:06 <Jomungand> anyone has a clue why this example isn't working?
07:30:47 <dracol> and compliment: fluidtypo3 is a great work!!
07:31:15 <NamelessCoder> I almost feel bad recommending this because of the size, dracol, but the official TCA docs explain every little detail about every parameter and combination ;)
07:38:42 <Xatenev> is it possible to create the jsonview for one action only?
07:38:47 <Xatenev> instead of setting it for the whole controller?
09:29:15 <deffcon> hey there. i updated to typo3 6.2 and latest fluidcontent + vhs version and now when i use the vhs page header meta viewhelper like following:
10:03:36 <deffcon> it seems to be a general issue in the Page/Header/MetaViewHelper. if i replace the $this->renderTag() with an own implementation it works
10:04:30 <deffcon> in TagViewHelperTrait there is an undeclared variable $forceClosingTag used in line 76. maybe it is related with this?
03:57:47 <braguzz> hi I have upgrade some ext: vhs flux fluidpages ecc..
03:58:12 <braguzz> but I 've got an error in 'home' page
03:58:37 <braguzz> inBE I got Template could not be loaded. I tried "/data/museo/SpecialityDistribution/typo3conf/ext/fluidcontent/Resources/Private/Templates/Content/Index.html"
06:25:43 <drlimbo> is there a know bug in VHS 2.3.1 with page.header.meta?
06:26:07 <drlimbo> <v:page.header.meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no" /> will be rendered in frontend like this:
07:01:16 <drlimbo> do we know a date for the next release?
07:02:29 <bjo3rn> bugfix releases are intended to happen quite often but there's no concrete timeline. you can safely use the development branch of vhs in the meantime.
07:03:47 <drlimbo> mh, i prefer using the "stable-version" for TER instead of the the dev-branch
07:04:35 <bjo3rn> sure, but vhs has always been very stable in dev branch.
07:04:41 <gencha__> there is no stable version. just the "old" version ;D
08:51:03 <NamelessCoder_> I'm working on a BIG cmis project right now
08:53:19 <NamelessCoder> anywho: change those occurrences that are in PHP, to \FluidTYPO3\Vhs\Asset - and those that are in fluid templates, to FluidTYPO3\Vhs\Asset
08:53:39 <NamelessCoder> sry, in templates, FluidTYPO3\Vhs\ViewHelpers
08:53:53 <NamelessCoder> (but that error will only pop up after you fix the other one, I think)
09:22:41 <braguzz> the whole three is displayed whit the metadata of the files as description in T3
10:33:11 <erredeco> Hi there... a couple of questions about flux:form
10:33:37 <erredeco> 1) if I don't have fields inside the "options" tab, is it possible to hide it?
10:34:47 <erredeco> 2) if I have a flux:form.sheet like <flux:form.sheet name="elements">, is it possible to have it selected by default instead of Options?
10:44:15 <Zaphod76> Hi, is there a new bug with copy & paste using flux in backend?
10:45:34 <Zaphod76> I'm using the versions of tody from flux, vhs, fluidpages and fluidcontent and hav a problem with cp like a few month ago with buggy older version
11:16:55 <BBendtsen> Good afternoon. Is it no longer possible to use "variables" in a name attribute like this: <flux:form.content name="column{iteration.cycle}" label="{percent}%" />
11:20:25 <NamelessCoder> BBendtsen it appears you're using flux:form.content in a loop and expect multiple content areas to be created. This is not the case - the behavior of this viewhelper is to create a full grid, replacing the current one, containing a single row with a single column with the name you specify. In your case the expected output is the last flux:form.content added. Solution: Switch to flux:grid > flux:grid.row > flux:grid.column, do not use flux:form.cont
12:08:55 <NamelessCoder> erredeco 1) use "compact" option on flux:form (boolean) if you wish. 2) No, this would depend on the user session storage in TYPO3 which stores the active tab panel. 3) No, that is not possible since we do not override the page module view.
12:19:51 <punkka> Hi, i would like to add a typo url within a vhs asset script but the f:uri.page is not parsed. Has someone an idea to help ?
12:45:13 <Zaphod76> Sorry, i repeat my question from 3:44 pm: Does anybody know something about new bugs in FECs with c&p an d&d? If I try to put a standard ce from one fce to another it is not working. After reload stays in his "home FCE". With fluidpages 3.1.2 , fluidcontent 4.1.1 and flux 7.1.2 no probs. VHS is the newest version installed by extsnionmanager
12:57:16 <erredeco> @NamelessCoder: Thank you for your answers :) Ok, about #3 a slightly different question:
12:58:11 <erredeco> I would like to add in the page module a sort of "explanation" for editors about what the page does
12:59:00 <erredeco> Do you think it could be possible to add a "fake" <flux:grid.row><flux:grid.column>... with a text?
13:01:26 <NamelessCoder> not possible. Our only "API" is to deliver an array that supports what be_layout supports.
13:02:54 <erredeco> @NamelessCoder I see...thank you anyway
13:07:23 <erredeco> It is a shame... that could be a bit useful IMHO
13:36:36 <NamelessCoder> it would have to be a core feature first, using options in the grid array. After that we could use it from flux grids.
16:34:00 <Hennes_> NamelessCoder: is there a way to disable a provider in a part of pagetree?
16:37:49 <apiening> I've used the FE 'file list' to render PDF download links including thumbnails using 'Layout 2'. In my fluid based typo3 this option is not available anymore.
16:39:36 <apiening> Is there any solution or extension I should use for that? The file list gives me a link list but doesn't display thumbnails of my PDF-files.
17:14:21 <apiening> I also noticed that the CE 'Text with images' does not have any controls but the heading. No RTE, no image file selector, nothing.
17:16:08 <apiening> Do I have to include 'CSS styled content' in addition to 'Fluid styled content'?
05:54:47 <dracol> if I have a content like "<flux:form.content name="content" />"
05:55:18 <dracol> how can i check if exist any content insert into
05:56:38 <dracol> fro prevent render if an user insert a content element without any element...
06:37:34 <bjo3rn> dracol you can use v:content.get fx to check if there are any content elements in that column.
06:38:19 <bjo3rn> something like <f:if condition="{v:content.get(column: 0) -> f:count()}"></f:if>
06:50:10 <pedda> aah .. you guys use f:count() ... i was fooling around with f:if condition="{v:content.render(column: 1)} !== ' '" which obviously is very ugly kinda ;)
07:58:09 <dracol> but i have the name "content" instead of number of column
09:02:43 <benjamin_654> Kalypso63: what you try to do with variable.set is pretty good described in the doc: https://fluidtypo3.org/viewhelpers/vhs/development/Variable/SetViewHelper.html
16:16:45 <hirnschmalz> Hi there, since the last update of the FluidTYPO3 extensions I've strange problems. I've two extensions one provide a page template and the other one provide some special content elements. If I try to insert the custom content element I get the error "#1225709595: Template could not be loaded. I tried..."
10:04:35 <BBendtsen> Hello - I have created a fluid content element with some content areas using the flux:grid vh, works only to insert new content, but content can't be pasted into it
12:31:05 <JohPie> NamelessCoder: is there now a way to disable a provider in a part of the pagetree?
16:26:05 <BBendtsen> Good evening. If you use a flux:field.checkbox, how do you test whether this is checked or not?
05:49:42 <drlimbo> i can see some "Invalid argument supplied for foreach()" messages in the Typo3-Log - Problems with Fluid ForViewHelper.php - is there a way to get known, where this error occurs?
07:12:13 <BBendtsen> Hello - I have created a simple input field <flux:field.input name="test" /> in a page template and try to output the value, but nothing is outputted. <f:debug>{test}</f:debug> says 0 chars even though the field is not empty
16:12:21 <BBendtsen> Good evening. I have had no luck trying to fix this all day. In my page template I cant fetch the value from flux fields, ex. <flux:field.input name="{settings.test}" /> - no output with <f:debug>{settings.test}</f:debug> - Any help is appreciated
16:21:30 <NamelessCoder> BBendtsen might you be affected by this bug? https://github.com/FluidTYPO3/fluidpages/issues/239
16:22:01 <NamelessCoder> (you'd be able to tell if you fill some value in the "page configuration - subpages" field and the page uses that in the rendering)
16:34:30 <NamelessCoder> in that case: apologies - we're working on fixing that. Meanwhile, if you can, fake those variables and await a bugfix for TER versions ;)
02:41:26 <braguzz> someone could help in upgrade extensions in a site?
02:41:54 <braguzz> I've upgrade (with many tears) a development version
02:42:25 <braguzz> but I've some problem in upgrade the 'copy' of the 'real site
02:42:42 <braguzz> I got Could not analyse class:Tx_Vhs_ViewHelpers_Extension_Path_ResourcesViewHelper maybe not loaded or no autoloader?
02:57:16 <braguzz> some old {namespace v=Tx_Vhs_ViewHelpers}
04:17:40 <fger> hi guys, one quick question: if you change the configuration-section in an FCE you need to re-save all existing FCEs in the TYPO3 instance
04:18:29 <fger> does one know a nice functionality to do this by script ?
04:19:05 <fger> i.e. any contentelement with tx_fed_fcefile = X ...
04:19:45 <fger> just wanted to know about the "re-save" part. is there a nice core function or even a method/utility inside the fluidtypo3 universe :) ?
04:24:58 <Bomwollen> does anybody know how to emulate a page call for another uid? For example, a page should display all contents of sub pages at once (not just some elements), with full FLUID template support. I know 3 ways: a) use curl -> token/session problem? b) copy TSFE and manipulate the page-id -> works, except some plugin will not load, something need to be changed, inited - but what? c) generate a new...
04:25:00 <Bomwollen> ...TSFE -> uses too much memory.
04:25:01 <Bomwollen> Any help would be appreciated.
07:55:31 <BBendtsen> I have a problem with the promising allowedContentTypes feature. I added this <flux:form.variable name="allowedContentTypes" value="text" /> inside a column, but when I remove it, the restriction is still there.
09:59:12 <Bomwollen> does anybody know how to emulate a page call for another uid? For example, a page should display all contents of sub pages at once (not just some elements), with full FLUID template support. I know 3 ways: a) use curl -> token/session problem? b) copy TSFE and manipulate the page-id -> works, except some plugin will not load, something need to be changed, inited - but what? c) generate a new...
09:59:14 <Bomwollen> ...TSFE -> uses too much memory.
10:23:37 <ndee> when I have an extbase model, and the perfect name would be "Model", what do I do? :D It's for a Car Model.