06:57:27 <Rawai> we are working with Flux 7 etc and our rootpage stays blank in the backend with page Module while list module shows the content correctly. The errorlog says "mod_fcgid: stderr: PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 105 bytes)" /typo3_src-6.2.1/typo3/sysext/extbase/Classes/Persistence/ObjectStorage.php
13:37:30 <randomresult> seems everybody has easter-holidays
13:38:04 <floxx1> how would you solve that with ft3: a menu with additional content like here http://www.esta.com/en/ -> Products & Solutions -> hover over "Products"
13:41:08 <floxx1> danilobuerger: yes, but what about multilanguage?
13:41:41 <floxx1> page properties added by ft3 aren't translateable afair
13:42:04 <danilobuerger> you can either translate the whole page configuration (thats available right now) or wait a few weeks until RR gets merged and then translate each field individually
13:51:51 <floxx1> ah ok. and page configuration is translateable out of the box? is this a new feature? i had a multilanguage project with sliders in page properties. they were not translateable…
13:53:29 <danilobuerger> this should have always worked... you will have to translate the whole flexform in pages->tx_fed_page_flexform
14:39:30 <floxx1> danilobuerger: sorry for asking again. but could you give me another hint? i added pegeproperties in flux template, now i translated page in be and the fields are missing for translated page.
14:40:08 <danilobuerger> you need to add tx_fed_page_flexform to the fields of pages that get translated
15:01:03 <floxx1> danilobuerger: yes. that's the configuration i meant before. and additonally i have to extend pages_language_overlay with tx_fed_page_flexform. right?
15:18:50 <danilobuerger> floxx1 probably yes if that doesnt happen automagically
15:28:30 <Torsten> Hey.. I'm still unable to drag / drop or copy / paste a CE element into an flux grid... is there a bugfix on the way? Currently im on development branch
15:32:07 <BenjaminR> Torsten: You know that danilobuerger is working hard on it, dont you?
15:32:58 <danilobuerger> to appreciate the size and complexity of that fix, one can go to https://github.com/FluidTYPO3/flux/pull/524 and see the number of commits
15:33:25 <Torsten> benjaminr No, I was idle until now.
15:33:36 <Torsten> danilobuerger thank you for your hard work.
15:34:20 <BenjaminR> Torsten: I was pretty sure you repeatenly asked about that the days before
15:35:14 <Torsten> benjaminr I asked that about 4 days ago and someone told me to switch workbench/commands... but with no luck.
15:35:47 <danilobuerger> np, Torsten if you want to help (and that means getting the fix into our branches sooner) you can checkout https://github.com/FluidTYPO3/flux/tree/workbench/commands instead of branch development and test it... what should be working is : new elements / drap&drop / localization / hiding&showing
15:36:28 <danilobuerger> the only thing not properly working in workbench/commands is copy&paste
15:37:21 <danilobuerger> if you try out workbench/commands and experience any issues beside copy&paste please report that in flux#524 .. that way we will have a fix ready sooner.
15:39:42 <pedda> it seems as if it is supported by default, but i don't get it at a certain point
15:40:08 <pedda> ext:news is equipped with some youtube interface already
15:40:34 <pedda> so everything is in place but my resource
15:40:45 <pedda> did you ever embed youtube videos in news ?
15:41:25 <BenjaminR> ...not in TX_news (what i guess is what you really want to know) :)
15:41:34 <BenjaminR> but cant be very difficult :)
15:42:01 <pedda> agreed.. it's rather like i'm just to dumb
15:44:38 <Guest|44946> Hi everyone, Greg here. I got a question regarding the builder extension. Wanted to try the system and installed all extension mentions in the docu. But the builder menu item does not show up in a fresh 6.2.1installation. Anything you have to do beside just install the extension and reload?
15:45:17 <pedda> reload the backend should do the trick
15:45:29 <pedda> as the left sidebar does not get refreshed sometimes
15:50:20 <danilobuerger> pedda i think you missed your calling as IT Support
15:50:40 <randomresult> did u turn the computer on?
15:51:17 <pedda> well.. if you knew what happened to me before the weekend, and espacially the consequences i was confronted with talking to my wife after she returned ...
15:51:45 <Guest|44946> pedda, yes, its active according to ext manager
15:51:56 <Guest|44946> currently installed extensions: builder, vhs, flux, fluipages,fluidcontent
15:52:12 <pedda> she told me, i'd spend too much time digging for a comma in some slideshow code, rather than giving some training to students or some sort of trainees
15:52:16 <Guest|44946> just cleared typotemp, caches and browser cache. Same result :(
15:52:55 <danilobuerger> Guest|44946 lust clearing try: go to install tool and clear all caches from inside the install tool
15:52:57 <pedda> Guest|44946 try disabling and reenabling builder
15:54:29 <Guest|44946> here's a screenshot of the installed extensions: http://oi57.tinypic.com/24w5a84.jpg. I'll try the install tool and disable/enable stuff now
15:56:01 <pedda> i have a 6.2 project running currently .. and builder is displayed on the left
16:05:11 <pedda> one should definetly gow ith a local dev env.. but as mentioned, it might be hard to get all this knowledge.. at least if it's just too expensive to buy a mac only because of this neat command ;)
16:05:15 <danilobuerger> thats the first thing web developers hsould learn, how to set up local dev and not work on production :D
16:22:34 <Denyerec> Fatal error: require_once(): Failed opening required '/home/denyerec/clients/alba/htdocs/typo3conf/ext/vhs/Classes/ViewHelpers/Page/Content/RenderViewHelper.php' (include_path='/home/denyerec/htdocs/alba/typo3/contrib/pear/:.:/usr/share/php:/usr/share/pear') in /home/denyerec/src/typo3-6.2/typo3/sysext/core/Classes/Core/ClassLoader.php on line 189
16:22:48 <Denyerec> everything else at the last release tag.
16:22:51 <BenjaminR> Harpagophyt: Use the experience you gethered from these bugs to complete our documenation and create a pull request. we would love to merge it
16:22:51 <Harpagophyt> therefor, please add this to the documentation
16:23:41 <danilobuerger> we deprecated that over a year ago, so dont tell me it was sudden ;-)
16:23:47 <Harpagophyt> ok, now i told you my frustrating weekend *gggg*
16:24:27 <BenjaminR> Sending a Pull request for documentation additions is easy with github. fork the repository, press the edit button for one of the files. Create a commit and afterwards a pull request :) No additonal tool necessary
16:25:10 <Harpagophyt> and what can i do with the builder bug?
16:25:24 <BenjaminR> Harpagophyt: Happens to all of us. But its a question of how you tell somebody who invested dozends of weekens before to make you able to come to that point anyway
16:26:17 <BenjaminR> And its not that we wouldnt love feedback (also crictics) - even more we love productive feedback like bug reports or pull requests / contributions of any kind
16:26:32 <Denyerec> That will teach me for using the bootstrap package as a guide...
16:26:45 <BenjaminR> Also you told about a bug in builder... report it.
16:28:59 <Denyerec> danilobuerger - content.get seems to want to fetch all the content from a given page ?
16:29:05 <Denyerec> At lwast, that's what the params suggest.
16:46:03 <Denyerec> Nothing there made it too clear :)
16:46:33 <Denyerec> And the code looked like it just ripped data from the DB. Might be worth updating the comments on that one to reflect its true purpose, before someone generates a singularity ;)
16:47:44 <NamelessCoder> you can edit the doc comment here: https://github.com/FluidTYPO3/vhs/edit/development/Classes/ViewHelpers/Resource/RecordViewHelper.php
16:48:09 <NamelessCoder> add text above @author and it will be displaed in docs on next rendering
17:01:01 <Harpagophyt> i think it comes from fluidcontent_bootstrap
17:02:25 <BenjaminR> fluidcontent_bootstrap will be replaced with https://github.com/bootstraptheme-for-typo3/fluidbootstraptheme one day
17:02:35 <Harpagophyt> #1225709596: The template files "/srv/vhosts/typo3.kraftl.at/htdocs/typo3conf/ext/fluidcontent_bootstrap/Resources/Private/Layouts/Content", "/srv/vhosts/typo3.kraftl.at/htdocs/typo3conf/ext/fluidcontent_bootstrap/Resources/Private/Layouts/Content.html" could not be loaded
17:02:38 <BenjaminR> that is the place you find the last examples
17:03:09 <BenjaminR> Seems you are using a layout "Content" which is not there
17:07:28 <BenjaminR> YOu shouldnt do such things during easter - you should have spend that time with your family. whould have saved you some anger it seams :)
17:07:30 <Defos> Hey there. Is EXT:builder working with Typo3 6.2 ? Doesn't seem like it for me
17:09:35 <BenjaminR> NamelessCoder: is Content Layout really missing here or am i blind?? https://github.com/FluidTYPO3/fluidcontent_bootstrap/tree/development/Resources/Private
17:09:36 <Harpagophyt> these are only my first steps
17:11:34 <BenjaminR> danilobuerger - anyone to confirm i am blind ;)
17:11:47 <Defos> odd. I can install it but in backend it says "null null" in the menu. CLI doesnt work either
17:11:49 <NamelessCoder> BenjaminR they are ;) TS for this ext points to fluidontent's default layout iirc
17:18:57 <Harpagophyt> last question (hope) if i insert css and js, is it better as asset or typoscript?
17:19:30 <BenjaminR> cedricziel: do you know what would be genius? making FT3BOT echo´ing the link to viewhelper documentation with some trick as we do with github issues
17:20:05 <Defos> doesn't work for me :-/ still "null null" in Backend.
17:30:05 <Harpagophyt> i am not really a t3 integrator ;-)
17:30:46 <moger> hey... I have a conventional plugin (shop_catalog) which shows a product that is selected via flexform. now i want to replace it by a fluidcontent element which determines the product, renders some other stuff AND then renders the shop_catalog plugin with the configured product. is there a way to hand over the configuration (uid of the product) fro
17:36:10 <pedda> instead of the oldfashioned way to have a sysfolder where all "special content elements" reside
17:37:35 <moger> complicated, but in short words: it's just a container for other content elements and the plugin that holds the catalog. the container used to be a typo3 page, but the problem is that the container needs to know the product that is being displayed inside it.
17:38:30 <BenjaminR> than id use page properties as pedda suggests and use v:get.typoscript to read that value in your extensioin
17:38:32 <moger> so i could simply add a product reference to the page, but i dont want the editor having to set the product twice (in page or FCE and in the plugin itself)
17:38:55 <BenjaminR> anyway there are also viewhelpers to render a plugin
17:38:59 <pedda> well.. an issue from a completely different person, but solution fits as well ;)
17:39:31 <NamelessCoder> moger flexforms or flux alone will not let you do that
17:39:49 <pedda> just read the single sentence with product and container ... -> should be a small products plugin fired via extension_builder
17:41:56 <pedda> was a pain in the ass and feels like a decade ago ..
17:42:43 <pedda> it was a time where pdf, print, email link to friend (in nowerdays social media share) were introduced
17:42:48 <BenjaminR> same here. migrated a website with 310.000 records in gallery module alone
17:43:04 <NamelessCoder> this is completely bat shit crazy but you could, in page properties, use default="{flux:form.data(table: 'tt_content', field: 'pi_flexform', uid: '{v:content.get() -> v:iterator.first() -> v:iterator.extract(key: 'uid') -> v:iterator.first()}') -> v:iterator.extract(key: 'path.to.setting.in.pluginFlexForm') -> v:iterator.first()}"
17:43:15 <pedda> all those three icons were spread among different files surrounded by some invalid tr td construct
17:43:26 <NamelessCoder> and then instruct that ONE content element exist on the page and that this CE gets added BEFORE you edit the page itself
17:43:36 <pedda> it was like: open row 1 in file 2 and close it in file 3 again..
17:44:59 <pedda> when i was a trainee at a advert-agency i was asked to make a choice between drupal 4 (iirc), conenido, joomla and typo light (contao)
17:45:21 <NamelessCoder> but moger there are so many places this could go wrong - I won't recommend doing it. The complexity of that expression above points to a problem in the structure itself. Consider if perhaps it would be best to replicate the plugin you're attempting to use, but have it fetch settings from page settings instead of flexform.
17:45:23 <soee_> gusy do you know maybe if it is possible to configure RealUrl so instead of including action and controller name just use a word that maps to it ?
17:48:28 <Guest|90502> hi, i'm using latest version of typo3 and the extensions flux, fluidcontent, fluidcontent_core, vhs and fluipages to create both page templates and content elements. Pages work fine and FCE also, but there is no fe ouput for my additional FCEs. I followed the manual on http://fluidtypo3.org (Sec 3.2.3) and i used the exact same snippets and don kno
17:49:35 <pedda> depends on your needs if you want to map a word per argument, or combine several arguments into one single word
17:50:17 <NamelessCoder> Guest|90502 or you may have forgotten to add the TS for your own provider extension - or it could be one or more caches messing with you. In summary, it's usually either TS or caches.
17:51:29 <Guest|90502> nameless: no, i used your install bash script, and removed css_styled_content, and added fluicontent_core...the "fce" gets registered and i can input some values, but the "Main" section does not get rendered at all...preview/config section works fine
17:51:31 <pedda> if it#s caches -> install ext:uncache
17:51:40 <pedda> if it's ts -> you need to fight it ;)
17:52:38 <BenjaminR> Guest: you added the line to AdditinoalConfiguration.php as documented?
17:55:24 <Guest|90502> Benjamin: no, i must have overlooked that, where can i find this?
18:00:49 <Guest|90502> benjamin: thats it, thanks alot...now i can also use the overridden fluidcontent_core files to recode the defualt content elements (Header, Bullets, Text etc.), right?
18:03:04 <BenjaminR> Guest: fluidcontent_core overwrites ALL core elements now. You then again can overwrite the fluidcontent_core tmeplate with your own with "overlays" - see documentation for that again :)
18:16:19 <moger> I first tried the most simple approach: use fluidpages to create a special page, the page has a product relation. on the page resides my plugin. so everything like before, but now the page knows its product.
18:17:02 <moger> now i need to read out the product uid from another template
18:17:45 <BenjaminR> _maybe_ v:page.info helps here
18:18:26 <BenjaminR> remembered that i wanted to make v:page.info to do that... but wasnt allowed by you ^^:D
18:18:54 <Guest|90502> i have just one more question...is there some more documentation to the concept of overlays. i'm not 100% familiar with that. i guess i can reuse the coreelements inside my extension, regarding to the naming convention of fluid?
18:43:24 <Guest|90502> in my extension setup.ts i added "plugin.extkey.view.overlays.tx_fluidcontentcore.templateRootPath = PATH" and i copied athe file Text.html to myext/Resources/Private/Templates/CoreContent so that the default "Text" Content Element should be overridden?
19:13:28 <BenjaminR> Outdoorsman: what means that your image or image processor is corrupt
19:26:28 <Guest|90502> Benjamin: i added plugin.tx_fluidcontentcore.view.overlays.myext.templateRootPath = EXT:myext/Resources/Private/Templates/ and i copied the file Text.html to .../Templates/CoreContent/ is there anything i'm missing, or known issues
19:28:31 <BenjaminR> maybe you forgot to include the static template from your provider extension