10:46:04 <feelx> Hi folks :D Is it possible to include in a flux grid/column a default typo3 CE? I.E. 'table' which I need for 'tech. specs' on fluidtypo3 CE
10:46:49 <feelx> I can create one manually and include the UID element. but which vhs:VH do I need this way?
10:47:37 <feelx> however it should 'copy' the inserted element and NOT reference it.
12:25:29 <feelx> thx bjo3rn :) sorry... I have a content element with 3 columns. I one column I want to have a typo3 default CE (type 'table'). Can I insert a specific CE in a fluidpage template? I know I can get some specific CE with v:content.get (uid attribute) VH. But I assume it does 'overwrite' the source CE when I edit it afterwards, right?
12:26:31 <feelx> so it should GET the CE (by UID i.E.) and store it as a new one.
12:33:36 <bjo3rn> feelx v:content.get is FE stuff so nothing can be overwritten?
12:34:39 <bjo3rn> plus you can't get one specific content element by its id
12:34:58 <bjo3rn> you can get all inside of a given colPos fx
12:41:17 <feelx> bjo3rn, okay thx... maybe v:resource.record is suitable to get a CE by it's UID? What I like about the typo3-default CE table is, I can easy edit it by using '|' as separator. Sure I can insert it manually too but if it's possible to insert it automaticaly it saves a few clicks
12:42:23 <feelx> My idea was to create a hidden 'template page' with some prefilled content elements which I can insert in a fluidpage template and edit them
12:45:30 <bjo3rn> so the prefilled ces (like that table) should be edited on that hidden page and placed on several different pages with the same content?
12:48:01 <feelx> bjo3rn, the 2nd case... it's a kind of kickstarter. These are tables for 'technical specification' always the same header but different content for each product
12:55:00 <bjo3rn> ok, then you'd have to copy the original ce and I have no idea how to solve that with vhs, sorry. I don't even think it's possible.
12:58:52 <bjo3rn> this requires some BE logic to be executed which is beyond the scope of vhs
12:59:15 <bjo3rn> as this is a one time action to be invoked
13:09:14 <Guest|35632> Hey guys, is something changed with the v:switch viewhelper? I have the error in the frontend on a pic element value found for key "FluidTYPO3\Vhs\ViewHelpers\SwitchViewHelper->switchCaseValue", thus the key cannot be removed.
13:09:36 <Guest|35632> I use the new dev version of flux and co and fluidcontentcore
13:09:56 <bjo3rn> Guest|35632 in this case the key is null
13:10:37 <Guest|35632> okay so the image isnt in the element anymore, btw i updated a website with the new version
13:11:05 <Guest|35632> if i re-create a image element now i have this error The template files "/www/infoarchitekt.de/hosting/2376/dcn.de/kunden/tbg/typo3conf/ext/moox_core/Resources/Private/Partials/Image", "/www/infoarchitekt.de/hosting/2376/dcn.de/kunden/tbg/typo3conf/ext/moox_core/Resources/Private/Partials/Image.html" could not be loaded.
13:16:20 <feelx> bjo3rn, okay thx... So it would need a action controller right? TBH I'm absolutely not familar with extbase programming. But I've got this book about extensionpgrogramming (Rau&Kurf�rst). Maybe I'll try a bit :)
13:36:15 <bjo3rn> Guest|35632 then there's some syntax error on your template
13:36:39 <bjo3rn> there are some bc breaks like v:var is now v:variable
16:03:17 <rahulthewall> Hi guys, I am using Ext:ke_search (faceted search) and I was wondering how I would have a search box on every page using fluid
16:03:25 <rahulthewall> The typoscript example is written thus: http://kesearch.kennziffer.com/en/documentation/searchbox-on-every-page.html
16:03:31 <rahulthewall> how would I integrate it with Fluid?
16:12:24 <soee> rahulthewall: create content element somehwere on your page, and use RECORDS to pass it with variable to tempate
16:12:43 <soee> or create search form instanc ein TS and pass as variable
16:13:34 <BenjaminR> rahulthewall soee: create a ts constant pointing to a page where you store a content element for the search form and render it whereever you like with <v:content.render pageUid="{v:var.typoscript(path: 'xy')}" />
20:13:24 <witrin> I've found out (http://vschart.de/vergleich/grid-elements-typo3-extension/vs/fluid-content-engine) that it's not possible to import/export `fluidcontent` CEs. Is this right? And when how do you bring particular content from one tree into another one? See also http://stackoverflow.com/questions/24557790/how-to-import-export-content-elements-of-fluid
20:21:26 <xaver> fluidcontent elements are fluid template based. no record needed
20:21:55 <witrin> I just want create some CEs (e.g. Slider) with fluidcontent and would be very happy when I'm able to impoert/export them.
20:22:17 <witrin> But it seems I don't get the idea of this extension at all :S
20:22:40 <xaver> content from the ce? it is in flexform field. It hsould be exported via t3d
20:23:50 <xaver> you create a template like this: https://github.com/bootstraptheme-for-typo3/fluidbootstraptheme/blob/development/Resources/Private/Templates/Content/Accordion.html
20:25:03 <xaver> Configuration is your BE input, preview will be visible in Backend as Content like title or in this case a widget (means you can add new elements). Main Section is FE output
20:27:44 <xaver> witrin: Its hard to compare, both systems are really different ideas. I have a lot of reasons to support this project and not gridelements
20:27:54 <witrin> And after I've installed this and created some content records with this template. I would be able to import/export this through the BE via t3d (because its just a flexform field like which contains most of the stuff you wrote)?
20:28:13 <witrin> I've already used gridelements, and I don't like it :(
20:29:22 <witrin> What do you use for transfering ce's between maybe staging and production?
20:30:32 <xaver> thats always a problem. You have FAL and all that stuff. t3d is a lot of magic and options. Try it maybe it works :)
20:32:32 <xaver> you have a lot of content elements and users. You work in a environment with unique Ids and copy them is really hard to decide what stay and needs to go.
20:32:51 <witrin> I'll do that, thanks! But you'll face those problems too, don't you? I'm just wondering how you guys get those tasks done. SQL?
20:33:10 <xaver> I never add content on a stage server
20:33:21 <witrin> Yes you're right! But for some simple case within the dev process.
20:33:29 <xaver> its so fast to add it in live, a hidden page, workspaces
20:34:10 <witrin> Unfortunatelly hour writers mostly are involved during dev :(. And they won't all again ...
20:35:47 <xaver> we have always at least 3 stages. local, dev/test, live, often 4 with test or maybe more
20:39:30 <witrin> Yes, similar to us. And often content will be produced on test stage (in smaller pieces for demonstrating) and then it comes the question "could we not just export this? It's already there. Let's reuse this..." :(
20:40:37 <witrin> Well I'll try it! Thanks. But I'm aware that references to Media stuff get's lost when it's in flex field ...
20:41:13 <xaver> Database is a DB for a reason, a lot of traffic and information's
20:42:23 <xaver> some people try stuff like http://www.liquibase.org/ or surf. I never used surf
20:45:38 <xaver> A reason to use FluidTYPO3 - a big team of maintainers and a lot of contributor. Gridelements depends more on money and smaller team. It overwrites a lot in T3 backend and this code needs maintenance for every update.
20:48:25 <witrin> Don't get me wrong here! I'll want to get rid of Gridelements for several reasons. I just have to find a way how to handle content between the several T3 nodes effectively. :)
20:48:50 <xaver> if you find a good one, tell me :P
20:49:22 <xaver> this is a topic on every camp - i think the best solution is a intern or trainee :P
20:50:04 <witrin> LOL! Currently we have one :P ...
21:01:47 <xaver> you can always ask question's here - get a irc client :)