11:09:40 <SuburbanWorrier> Hi guys, is there a simple (viewhelper?) way to build page meta keywords from an extbase extension?
11:10:08 <cedricziel> SuburbanWorrier: what are you trying to do?
11:10:53 <cedricziel> setting keywords from within a frontend plugin?
11:11:14 <SuburbanWorrier> Hi Cedric, I'm trying to get a list of keywords from a loop of objects. So if my page is showinf all VW models then the models are also meta keywords.
11:12:17 <SuburbanWorrier> I'm using v:page.header.title for the title and I just explored https://github.com/benjaminkott/bk2k_collection
11:12:49 <cedricziel> despite keywords are useless in modern search engines you'd need a new array for http://fluidtypo3.org/viewhelpers/vhs/master/Page/Header/MetaViewHelper.html
11:14:00 <cedricziel> sooo... easy in your case as you have a model
11:14:44 <cedricziel> do the collection in the controller and then assign with v:page.meta(name: 'keywords', content: {keywordsFromController})
11:19:02 <cedricziel> there's an article, linked in this article stating "That year — 1997 — was the last year that the meta keywords tag enjoyed support among the majority of major crawlers out there (4 out of 7 – Excite, WebCrawler and Northern Light, also crawling the web that year, did not support it)."
11:20:02 <SuburbanWorrier> lol. Yeah - that was _the_ year my boss bought his web fu. Majesterially switching from FrontPage to Dreamweaver ;-)
11:20:22 <cedricziel> hehe, i like your Humour, Dude!
12:19:14 <SuburbanWorrier> Can u explain why {namespace v=FluidTYPO3\Vhs\ViewHelpers} breaks a template that works fine with {namespace v=Tx_Vhs_ViewHelpers}?
12:20:48 <SuburbanWorrier> spits out http://typo3.org/go/exception/CMS/debug/1289386765
12:31:05 <NamelessCoder> error message indicates which deprecated ViewHelper is being used. Replace with alternatives.
12:38:18 <SuburbanWorrier> Thanks again Claus. This must be my deprecated code then : {brands->v:iterator.chunk(count:3,fixed:1)->v:var.set(name:'chunks')}
12:39:31 <SuburbanWorrier> Hmm - "Could not analyse class:FluidTYPO3\Vhs\ViewHelpers\Var\SetViewHelper maybe not loaded or no autoloader" was my error
13:12:17 <Guest|20428> Hi 2all, i have on nested fluid content elements the message 'invalid value ("18181")'
13:12:56 <Guest|20428> actual i have the newest versions of flux, fluid pages, fluid content etc
13:13:21 <Guest|20428> colpos in tt_content record contains 18181
13:14:29 <Guest|20428> the content element view in the backend reflects the colpos labels from my PAGE Template for colpos 0 -3
13:24:19 <NamelessCoder> Guest|20428 you will see that "invalid value" thing on 6.1 and 6.2 when fluidpages is *not* installed. It doesn't break anything though.
13:26:16 <Guest|20428> i have 6.2 an fluidpages installed
13:27:08 <Guest|20428> functionally there is no problem - only the selector "column" shows "invalid value"
14:21:41 <Defos> @NamelessCoder: I had the same question yesterday like Guest|20428. I think you should link to http://fluidtypo3.org/documentation/templating-manual/appendix/migration/to-flux-71.html in your blog post as it contains vital information about the grid changes when upgrading.
14:26:37 <jgo> a question about fluid page layouts: i'm creating a flux grid for a page layout in the backend. gist: https://gist.github.com/anonymous/3a48a7d0bfdae44bfa2b
14:27:39 <jgo> ... is there a way to restrict access of the first two columns to admins?
14:28:12 <jgo> either invisible or just not editable for regular users would be fine
14:42:56 <NamelessCoder> using identical names for columns might also break how the layout gets built, overriding all previously defined columns
14:46:31 <jgo> ok, fixed that too. but the issue still remains
14:47:45 <jgo> strangely enough the first paste example results in the first two columns being hidden for admins and every other BE user as well
14:47:56 <NamelessCoder> here, both .deny and .allow work just fine, but they do throw an error when the THEN case is matched (due to missing TSFE instance)
14:48:47 <NamelessCoder> you are certain that: 1) you are in fact using the layout from the page template and not a manually selected be_layout, 2) VHS is a recent version, 3) your backend user is indeed an admin?
14:50:13 <NamelessCoder> that warning would not make it fail that way though
14:51:09 <jgo> definite yes for 1) and 3) ... have to check which vhs version is running though
14:53:32 <NamelessCoder> and just now confirmed this also works to hide/show layout columns
14:54:09 <jgo> ok then ill have to look for the cause somewhere else i guess ;)
14:54:11 <NamelessCoder> my template uses the namespace-style VHS inclusion but other than that, it's the same as yours
14:54:33 <NamelessCoder> the causes I listed should be the only ways this might fail
14:55:06 <NamelessCoder> one thing though... I'm not sure how nice it is to use colPos values that high. Try to stay below 10, just in case
14:56:45 <NamelessCoder> oh and last thing: your second of the two examples will never work. The f:section ViewHelper is retrieved without caring about what is surrounding it - and this is simply how Fluid works with sections in any fluid template
14:57:22 <NamelessCoder> it is, for example, also the reason why you can add <html> tags that don't get rendered when your template contains sections that you render from the layout
14:57:43 <jgo> ok will keep that in mind. thanks for heads up
15:15:03 <jgo> ok ive tested it with lower colPos values and it works with every value >= 3