IRC logs

20150317

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

IRC log range: 20150317*

20150317

  • 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
  • 09:48:42 <Guest|5028> Thank you, I will try that
  • 10:11:53 <Rabe69|43669> Could it be that if i put about 10 elements on a page that backend needs up to 15 seconds to load?
  • 10:13:22 <Rabe69|43669> I using fluidpages/fluidcontent/fluidcontent_core
  • 10:13:42 <Rabe69|43669> I use fluidpages/fluidcontent/fluidcontent_core
  • 10:15:11 <NamelessCoder> Rabe69|43669 which version are you using?
  • 10:16:02 <Rabe69|43669> fluidpages: 3.1.2 / fluidcontent: 4.1.1
  • 10:16:39 <Rabe69|43669> it themes to has nothing to do with fluidcontent_core
  • 10:17:21 <Rabe69|43669> i tried to put only some other fluidcontent elements on a page
  • 10:17:50 <Rabe69|43669> every new element expand the loading time about 2 sec
  • 10:19:27 <NamelessCoder> which flux version do you have?
  • 10:19:49 <Rabe69|43669> 7.1.2
  • 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:19 <Rabe69|43669> ok, i will check
  • 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:23:25 <Rabe69|43669> custom
  • 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:34 <Rabe69|43669> Ok
  • 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:30:22 <Rabe69|43669> tmpfs sounds interresting
  • 10:30:41 <NamelessCoder> - makes a lot of sense for typo3temp ;) esp. if you don't use ssd
  • 10:30:43 <Rabe69|43669> but why not using the caching framework?
  • 10:31:00 <NamelessCoder> even with the caching framework, the fluid template cache is filesystem based
  • 10:31:06 <Rabe69|43669> i have ssd's
  • 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.
  • 10:35:35 <Rabe69|43669> sounds goot
  • 10:35:37 <Rabe69|43669> sounds good
  • 10:35:44 <NamelessCoder> (beefy computer though so don't expect *that* much. It's a mac pro, the ssd makes a huge diff)
  • 10:36:20 <NamelessCoder> eager to hear the results... I'll be here if you run into upgrade issues
  • 10:36:35 <NamelessCoder> there are no EM scripts to run, it's all about the Fluid/TS in this one
  • 10:36:43 <Rabe69|43669> thanks so fare
  • 10:37:06 <NamelessCoder> you're welcome - sure hope it helps!
  • 10:39:03 <NamelessCoder> oh yeah Rabe69|43669 what core version do you run?
  • 10:40:59 <Rabe69|43669> 6.2.10
  • 10:41:31 <NamelessCoder> you might also gain a bit via env COMPOSER_AUTOLOAD for the site
  • 10:41:45 <Rabe69|43669> already done
  • 10:41:52 <NamelessCoder> ^^
  • 10:41:56 <Rabe69|43669> :-)
  • 12:15:14 <Guest|95568> Hi! Who knows how to translate an item list in a flux:field.select ?
  • 14:15:08 <jonasjo> hey :-)
  • 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:20:55 <jonasjo> what am i missing?
  • 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