09:59:02 <randomresult> the question is: does he want to follow
09:59:36 <mrboe> @randomresult go and clean your branch
10:00:43 <randomresult> what mrboe means: until flux 7.0 the naming of fields was flux:flexform - with 7.0 the names changed to flux:form - and the xsd-files of claus use the old ones. you are now using the news ones. but ur templates still use the old ones... wow. and now ur confused
10:01:17 <randomresult> or better : the dev versions use the new ones. your templates still use the old ones.
11:31:15 <danilobuerger> Denyerec the xsds are auto generated, if you want them generated for the branches development / staging too you need to file an issue at https://github.com/FluidTYPO3/fedext.net
11:53:36 <Denyerec> So the autogen ones are for master / release tags
11:53:48 <Denyerec> Do you have a release timeline that co-incides with the 6.2 LTS release?
11:55:49 <randomresult> Denyerec https://fedext.net/overview.html - there u see a timeline
12:16:43 <mrboe> @randomresult is there a possibility to get a mrboe viewhelper
12:17:57 <randomresult> https://fedext.net/viewhelpers/vhs/master/Content/Random/MisterBo.html her you go. just commited it. - Selects a random ugly image from www.ugly.com
12:25:31 <danilobuerger> everything is cached except if you explicitly uncache it
12:25:47 <danilobuerger> which you can because i wrote the view helper for that
12:25:51 <Denyerec> So how does one manage a frequently updated news ticker or such?
12:26:50 <danilobuerger> on high frequent sides you would use something like varnish
12:27:01 <danilobuerger> if its low frequent you are fine with using the uncache viewhelper
12:28:09 <danilobuerger> so with v:render:uncache you can render a partial... your whole site will be cached except that partial and in that partial you can use your random view helper
12:28:38 <danilobuerger> but only use on low frequent sites, for high frequency you can go the varnish route fx
12:30:11 <Denyerec> varnish will not be necessary here
12:30:15 <Denyerec> we're talking < 500 hits a day
12:30:33 <danilobuerger> ah then use v:render.uncache
12:30:39 <danilobuerger> and render that one partial uncached
12:30:44 <danilobuerger> everything else will still be cached
12:31:30 <Denyerec> What if the dynamic part is a content element ? Use the render.uncache VH in the content element's template I suppose ?
12:32:03 <danilobuerger> the whole content element is dynamic or just part of the content elements template?
12:33:19 <Denyerec> They want a "random testimonial" content element they can drop into pages.
12:34:06 <danilobuerger> so in your content elements template use v:render.uncache, and put the randomness in a separate partial
12:39:04 <Denyerec> OK, so my page template doesn't know antyin about this, the content element template contains, say, some <blockquote> HTML, and then the actual raw quote information is rendered via a partial called by render.uncache
12:44:35 <danilobuerger> and only that partial will be uncached
12:45:17 <danilobuerger> but obviously it still needs to fire up the whole framework, so its rather expensive to do it.. thats why i said its fine for low frequent sites
12:48:38 <Denyerec> I suppose pulling said data via ajax would be preferable ?
12:48:51 <Denyerec> IIRC there's a "reduced size" stack you can interface with via ajax?
12:54:14 <danilobuerger> Denyerec yes, ajax would be preferable
12:54:38 <Denyerec> What's the ajax interface called
12:54:42 <Denyerec> I've never touched that before
13:05:04 <Guest|81769> I just installed the fedext bootstrap and it seems to run smooth. Now I run into a little uncertainty where all information is coming from.
15:13:23 <mrboe> if you debug <f:debug>{subMenu}</f:debug>
15:13:34 <syssi> But I get: #1237823695: Argument "as" was not registered.
15:14:02 <syssi> I'm using flux 6.0.1. Is this a known issue?
15:15:28 <mrboe> @danilobuerger back to Workspaces - so this will be fixed and is a known issue
15:17:28 <Guest|99236> if i debug i get a var dump for every item
15:19:53 <NamelessCoder> syssi the "as" argument was added on october 23rd last year, so it is right on the border between 6.0.1 / 6.0.2. The ViewHelper reference could be incorrect - check the ViewHelper class file to be absolutely sure. If the "as" argument is not defined, you need to upgrade to at least 6.0.2.
15:20:19 <NamelessCoder> alternative syntax: {flux:flexform.data(...) -> v:var.set(name: 'pidFlexform')}
15:34:53 <NamelessCoder> will catch you when I get a break, currently on another project
15:35:18 <randomresult> ill be here for another 2 hours i guess.
15:35:31 <randomresult> otherwise you can also speak to mrboe. he will help me
15:35:41 <danilobuerger> mrboe workspaces is a known issue
15:36:08 <randomresult> it only a question on how the workflow is the best using upstreams etc.
15:36:42 <NamelessCoder> if anyone fixes workspace support before the 25th I will personally donate a full day of my time to a project of their choosing ;)
15:39:54 <syssi> NamelessCoder: The alternative syntax gives the same error, so I was trying to find new ways ;-)
15:41:05 <NamelessCoder> if you get the same error, remove the "as" argument from flux:flexform.data
15:42:16 <syssi> Without the "as" it works fine but I need to access an array.
15:42:42 <syssi> So upgrading flux is the way I go.
15:43:18 <syssi> I have upgraded to 6.0.3 and the error is the same.
15:50:27 <danilobuerger> NamelessCoder flux & workspaces needs a surgeons hand ;-)
15:51:34 <syssi> NamelessCode: The argument "as" of flux:flexform.data is also broken in 6.0.3
15:52:07 <NamelessCoder> I see, yeah. This feature was never backported - the viewhelper reference is simply wrong
15:52:27 <danilobuerger> syssi time for staging or development branch :D
15:52:33 <NamelessCoder> {flux:flexform.data(...) -> v:var.set(name: 'pidFlexform')} then {pidFlexform.fieldname}
15:54:07 <syssi> Yep. This is my current workaround: <v:var.set name="pIdFF" value="{flux:flexform.data(uid: '{page.pid}', table: 'pages', field: 'tx_fed_page_flexform')}" />
16:51:52 <mrboe> i had also the problem that the default chmod rights have changed (install tool)
16:52:13 <mrboe> have you cleared typo3temp folder
16:52:56 <Krystian> tnx mtboe - I will llok into that and give you answer in few minutes
17:01:39 <randomresult> Krystian if u work in 6.2 take a look at the file and folder rights of typo3temp (for ext) - they changed it to something like 2770 instead of 0755 and 0644 (see Installtool)
17:01:48 <randomresult> that messed up my dev-server.
17:15:13 <Krystian> Thank you guys. The https://github.com/FluidTYPO3/documentation/blob/master/Namespaces.md helped me to make backend usable.
17:15:31 <Krystian> But on frontend I am getting The requested page didn't have a proper connection to the tree-root!
17:15:48 <Krystian> I know this error is werid. I will try to uninstall most of the extesnions.
17:21:00 <Tjark> Krystian try Compare Database. This is what helped me once
17:32:26 <Krystian> Yes Tjark. That was it! Now the FAL images seems to be broken :)
17:32:48 <Krystian> Maybe some problems while upgrade. Let me check.
18:06:48 <Guest|20212> Hello! I'm looking for the best way to access page media resources in a template through the rootline (i.e. i want to find the first page in the pagetree that has an image in the resources). Is this possible?
18:29:11 <danilobuerger> in that case you can ignore that whole page because alias mapping will work for you
18:29:41 <danilobuerger> and i can tell you first hand that 6.2-git and ft3 dev branches are working fine with each other
18:29:46 <danilobuerger> so just upgrade and relax :-)
18:30:12 <Denyerec> Fatal error: Call to a member function getCache() on a non-object in /home/denyerec/clients/alba/htdocs/typo3conf/ext/fluidcontent/Classes/Service/ConfigurationService.php on line 125
18:32:32 <danilobuerger> no just the master of what i just posted
18:36:46 <Denyerec> Fatal error: Call to a member function getCache() on a non-object in /home/denyerec/clients/alba/htdocs/typo3conf/ext/fluidcontent/Classes/Service/ConfigurationService.php on line 125
18:44:35 <danilobuerger> nearly never, but this might be a case..
18:44:43 <danilobuerger> just make sure the cache tables in the database are all empty
18:45:13 <danilobuerger> if that doesnt do it -> you said your project is practically empty ... just zip it up to a db dump and send it over to me and i will take a look
18:46:24 <Denyerec> You are spared that torture, the DB cache flush fixed it.
18:46:32 <Denyerec> Worth adding that one to the FAQ!
18:47:01 <NamelessCoder> "Hello, Rob from IT. Have you tried manually flushing the cache tables?"