09:29:50 <Xatenev> xaver: nope, onclick is better for this specific case
09:32:53 <rosieres> Xatenev: nope. See this -> https://fluidtypo3.org/library/code-examples.html?tx_fluidshare_display%5Bgist%5D=19&tx_fluidshare_display%5Baction%5D=display&tx_fluidshare_display%5Bcontroller%5D=Gist&cHash=ca4eb1b45d865196a7e605f6a14f409f
10:28:15 <jmverges> well, I have other thing in mind, that is more interesting that this realurl shit xD I have a vagrant machine like the one provided by fluidtypo3. I'm trying to configure phpstorm with the phpunit inside the vagrant to run my own UT, could anyone help me a bit?
10:28:44 <danilobuerger> lol... i am out on that one
10:48:21 <jmverges> I don't know how do you say in english "me has tocado la vena sensible"
10:49:17 <rosieres> I just implement my libraries in 1 file or concate them. And another file for my individual functions, which I always only call If I find any element on page regarding them.
10:50:34 <jmverges> " you have touched a soft spot in me"
13:43:27 <TomL2> Hi guys! I've run into a problem with the flux grid and some custom content elements which are defined by TSconfig and ext_tables.php from the core elements (Example Button-Element: http://pastebin.com/LzLxakAz). When I add this element into a flux grid column the value for the tx_flux_column is missing in the database. This only happens with my ad
13:43:28 <TomL2> apted content elements, the default elements (text, textpic, ...) are ok.
13:44:57 <TomL2> I've used fluidcontent only for the grid container, the other elements are from the core or a adaption of the core elements via TCEFROM
03:34:20 <TomL2> Hi guys! I've run into a problem with the flux grid and some custom content elements which are defined by TSconfig and ext_tables.php (Example Button-Element: http://pastebin.com/LzLxakAz). When I add this element into a flux grid column the value for the tx_flux_column is missing in the database. This only happens with my adapted content elements,
03:34:20 <TomL2> the default elements (text, textpic, ...) are ok.
03:34:30 <TomL2> Add text, textpic etc. to the grid -> no problem
03:34:45 <TomL2> Add button (custom) to the grid -> tx_flux_column in db is empty
03:35:50 <TomL2> new pastebin, since the other link doesn't work http://pastebin.com/ibwMaH9v
03:36:16 <TomL2> I've used fluidcontent only for the grid container, the other elements are from the core or a adaption of the core elements via TCEFROM
04:44:06 <jmverges> hey folks, do you know some extension to do a database dump with typo3 console or with some BE module? I saw some fedext extension (old) from Claus that do it
04:56:13 <webz> Why I get the Error "Data Structure ERROR: No proper configuration!" on page Setup?
06:24:08 <pedda> did someone of you guys managed to successfully offer a flux plugin setting in BE where one can select a category in order to filte records in FE ?
11:55:05 <jmverges> I have a extension made with extension builder and I would like to show one register as a CE, can I do this with fluidcontent_core?
12:23:41 <t3sam> Why can't I choose a Layout under the Tab Page Layouts (edit page)?
12:24:07 <t3sam> I created a builder extension and included the typoscript template.
03:30:46 <t3sam> Is there a easy tutorial (step-by-step) how to set up a TYPO3 with fluidtypo3? I know the documentation on fluidtypo3.org, but in the most cases I search every step again....
04:06:32 <rosieres> t3sam: there's no how to set up with fluidtypo3 unless you define the purpose as you can combine different approaches quite infinite. So you have to define, what you want exactly or just try this -> https://github.com/FluidTYPO3/site
06:44:59 <Joewaschl> I learned that fluidcontent_core doesn't have textpic CE. What if I want to create it myself? Simply add "Textpic.html" to the template folder seems not to do the Job... Can someone push me in the right direction? :)
09:42:45 <t3sam> <rosieres> thanks, that's enough. Very helpful!
09:56:55 <pedda> i have some tricky case i'm struggeling with in fluid
09:57:40 <pedda> i have a table rendered in fluid, which should be extended by 2 additional th'S and td's if one item of an object storage has a certain property set to true
14:11:26 <Joewaschl> I learned that fluidcontent_core doesn't have textpic CE. What if I want to create it myself? Simply add "Textpic.html" to the template folder seems not to do the Job... Can someone push me in the right direction? :)
07:21:14 <batjony> is there a way to change the page template dynamicly based on some condition, lets say for example in a PageController or in the Provider /
09:27:22 <trendzetter> hi, I am setting up an environment for fluidtypo3. I downloaded 6.2.9 and the latest extensions in ter (also tried the fuildtypo3 distribution)
09:29:35 <trendzetter> The section Main is not displayed on page, only the title.
09:31:00 <cedricziel> are you talking about page templates?
09:31:04 <trendzetter> I have been wrestling with this for days. Can someone give me some hints on getting started with the new ways?
09:31:27 <trendzetter> I tried adding a example fluid content element
09:31:57 <trendzetter> 't is included in the distribution and with the provider extension if created by the builder
09:32:21 <cedricziel> once gain then: have you set up any kind of page template?
09:33:05 <trendzetter> yes, I have "Standard fluid page"
09:33:39 <cedricziel> do standard content elements work?
09:33:53 <trendzetter> and the template is empty with a provider extension in the includes
09:34:44 <trendzetter> standard content is displayed normally
09:35:20 <trendzetter> but the fluid content only has the title
09:37:43 <cedricziel> well, as i have no introspection into your code; can you please cross check with this example extension? https://github.com/FluidTYPO3/fluidtypo3org
09:37:57 <trendzetter> it could be useful to know a working combination of versions of the cms and the extensions required to get fluid working. I suspect that I have an incompatebility.
09:38:30 <trendzetter> I will download the version from github and give it a try
09:38:45 <cedricziel> ter combinations with a recent 6.2 shouldnt have problems
09:49:36 <trendzetter> I can add the content and the different types of pages in the backend. The pagelayout seems to be correct but the content elements are not displayed
09:58:35 <trendzetter> so basicly I have a plain 6.2.9 install without errors. the fluid extensions from ter and the fluidtypo3org provider extension delivering page template and content element template. for some reason the main section of the fluid content elements is missing
10:07:00 <NamelessCoder> trendzetter the fluidcontent elements included in the fluidtypo3org extension are written specifically for fluidtypo3.org and depend on typoscript as well as local folders - empty output is to be expected. You should try creating your own element or use some of the collections out there.
10:10:08 <trendzetter> I also used the example FCE saying <f:section name="Main">
10:10:08 <trendzetter> <h3>I am a content element!</h3>
10:11:20 <NamelessCoder> did you load the static typoscript belonging to the provider extension?
10:11:50 <trendzetter> I included the provider extension in includes of my root template
10:12:36 <NamelessCoder> and are you using css_styled_content or fluidcontent_core? If it's the former, you have to load that typoscript as well. If it's the latter, make sure you ran the update script via EM and that it wrote the typo3conf/AdditionalConfiguration.php file
10:12:59 <trendzetter> no css_styled_content, it is uninstalled.
10:13:40 <NamelessCoder> and if you are *completely* new at this and the site is still blank, you may want to try installing the "site" distribution from TER. It creates pages and setup for you so you eliminate potential errors in that area.
10:14:12 <NamelessCoder> there is a checklist with some 10+ items that all have to be done correctly for it to work - EXT:site automates that part.
10:14:20 <trendzetter> I started first from the site distribution
10:15:19 <trendzetter> I already have a fluid site running on 6.1 so it's not completely new but I got it from a typo3 with all extensions included (the bootstrap demo from a year ago or something)
10:15:39 <trendzetter> I cannot find the typo3conf/AdditionalConfiguration.php
10:15:50 <NamelessCoder> I assume you use fluidcontent_core since you don't use css_styled_content
10:16:41 <NamelessCoder> then either use EM to run the update script for fluidcontent_core or manually copy the file into place from Resources/Private/Configuration/AdditionalConfiguration.php
10:17:52 <NamelessCoder> that's item #8 on the list hehe
10:18:19 <trendzetter> it seems that was skipped by the site distribution because it gave some error about vhs installing multiple versions
10:18:23 <NamelessCoder> it SUCKS that it has to be copied this way but, sadly, there is no way around it. It's *extremely* legacy but required to be so
10:19:14 <NamelessCoder> ah yes... there is a dependency conflict somewhere I think... VHS is available in a too-recent version not supported by some exts (well, it is, but the metadata says no)
10:20:06 <trendzetter> I think the underlying issue might be ter having difficulties with certain combinations in dependncies
10:20:38 <trendzetter> thanks again! I am getting started now. you guys are the best
08:14:05 <trezndzetter> last week you saved me from giving up on the deployment
08:14:31 <trezndzetter> now I am happily trying out and developing the first templates
08:14:57 <trezndzetter> I wonder how you guys get rid of cache
08:15:22 <trezndzetter> If I change my translationsfile it doesn't appear immediatly
08:15:36 <trezndzetter> and not after flushing all caches.
08:15:36 <NamelessCoder> mikemm you can safely ignore that version constraint but you may need to explicitly install VHS then fluidcontent_core and ignore the warning.
08:16:16 <NamelessCoder> trezndzetter use development context for TYPO3 and the "clear system cache" cache clear method
10:05:37 <jmverges> NamelessCoder, did you see the issue that I raised? https://github.com/FluidTYPO3/fluidcontent_core/issues/132
10:05:48 <NamelessCoder> jmverges yes, I will get to that when I have time
10:06:13 <pedda> tsob tells me there is a plugin.tx_fluidpages.siteRootInheritance property available
10:06:23 <jmverges> ok, so, do you think that is a issue or is working for you?
10:06:40 <pedda> but not at the moment if a page is created in list mode
10:06:53 <pedda> i can coppy a page within the page tree though
10:07:07 <NamelessCoder> pedda the difference from before to now is that the Flux ConfigurationManager is expected to be registered as implementation. It works the same way as the standard ConfigurationManager except it supports additional ways of determining the page UID
10:10:09 <NamelessCoder> https://github.com/FluidTYPO3/flux/blob/development/Classes/Configuration/BackendConfigurationManager.php#L114 should be called and should return the right page UID
10:11:56 <NamelessCoder> this is purely a matter of resolving the TS that applies to the currently edited page UID - it should be quite simple
10:17:43 <pedda> if i debug the whole configurationManager->getConfiguration(…) i get some output where plugin. is not empty but fluidpages is missing
10:18:37 <pedda> i can see felogin, flux, formhandler and tt_address, lets say .. all those "i include my own piece of ts config on load" extensions
10:19:42 <pedda> as mentioned earlier.. because of basic.autoload em setting i would expect fluidpages to get listed among these
10:20:48 <NamelessCoder> that's fine in that location: the typoscript at that point is only responsible for controlling your overrides of inheritance behavior for the template selector field
10:21:50 <NamelessCoder> https://github.com/FluidTYPO3/fluidpages/blob/development/Classes/Service/PageService.php#L155 is used to resolve available selections
10:22:02 <NamelessCoder> (it also uses the overridden ConfigurationManager)
10:23:23 <NamelessCoder> https://github.com/FluidTYPO3/fluidpages/blob/development/Classes/Service/ConfigurationService.php#L73 is where the TS-related part happens: fluidpages reads all registered provider keys and resolves the view configuration (either what is set in TS or it uses fallbacks with default paths) and stores the path configurations for each provider extension key
10:24:00 <pedda> but as $typoScript['plugin.']['tx_fluidpages.' ] i'm talking about line 112 and 113 of PageLayoutSelector (just to make sure) where in line 113 removeDotsFromTS is utilized on a null value because line 112'S var is lacking of plugin.ty_fluzidpages
10:24:03 <NamelessCoder> pedda I assume you also have seen https://github.com/FluidTYPO3/fluidpages/commit/b5fd17bd69315589ea77a77202fc5eb0255cf0f1
10:24:43 <NamelessCoder> yes pedda - that's expected. The TS option is not documented and may be removed and fluidpages itself does not define the TS in plugin.tx_fluidpages
10:25:10 <NamelessCoder> but it is NOT that location that is responsible for storing your actual template paths - that has to reside in plugin.tx_yourext.view
10:26:36 <NamelessCoder> what works now: registering a provider extension key + controller name "Page" and having valid template files in that location. The TS defining view paths for your provider extension is optional now - and you can use any of the supported ways of setting the paths
10:27:03 <NamelessCoder> let me just throw some more links at you... ^^
10:27:44 <pedda> always good to know about those, as the most information about breaking changes can be taken from commits only regarding ft3 tools imo
10:27:49 <NamelessCoder> pedda you already have the links that removed the legacy bit and I've shown you the places where we now rely on the new ConfigurationManager to resolve our TS.
10:28:21 <NamelessCoder> pedda then comes, once merge, https://github.com/FluidTYPO3/flux/pull/758 - which will enable the use of any supported structure for defining templateRootPath, templateRootPaths, overlays.xyz.templateRootPath etc.
10:29:29 <NamelessCoder> currently to resolve the view configuration we call this method: https://github.com/FluidTYPO3/flux/blob/development/Classes/Service/FluxService.php#L288 which checks if TS is set and if not, uses the method right above it to generate defaults
10:29:51 <pedda> as i was able to create pages until yesterday, and i didn't update/upgrade flux by now
10:29:56 <NamelessCoder> the method there should be 100% safe from any errors that is NOT caused by incorrectly setting the TS (which I assume you are doing correctly)
10:30:22 <pedda> i enabled some overlay by the help of View.. this is the only thing i did in the last 24 hours related to template paths
10:31:19 <NamelessCoder> you should consider EXT:view deprecated; flux either has or is soon getting native support for the ways the core defines multiple root paths
10:31:37 <drlimbo> we used this way to include an icon: icon="{v:extension.path.resources(path: 'Icons/icon-twitter.png')}" - but icon="" is depreceated, so we should use options="{icon: 'Icons/Content/Example.gif', ...
10:31:42 <NamelessCoder> and I very much would appreciate if you find the time to test the pull request(s) flux#758 ;)
10:31:52 <drlimbo> is there a way to use the v:extension.path.resources with the options="{icon: way?
10:34:02 <NamelessCoder> drlimbo see https://github.com/FluidTYPO3/flux/blob/development/Classes/ViewHelpers/Form/Option/IconViewHelper.php (not yet published to docs). Usage: <flux:form.option.icon value="{v:extension.path...}" />
10:35:34 <NamelessCoder> it's easier to use than <flux:form options="{icon: '{v:extension...}'}"> but has the same effect - and you don't have to escape single quotes inside the options array values
10:36:04 <drlimbo> thanks NamelessCoder, so <flux:form.option.icon should be used inside <flux:form, right?
10:37:22 <xaver> icon should work without any option /Resources/Public/Icons/{Content,Page}/id.(png,gif...)
10:37:56 <NamelessCoder> drlimbo true, what xaver said. You may want to check out the automatic icon-by-convention resolving
10:38:23 <NamelessCoder> place your icon at the expected location and Flux uses it automatically, no need for the flux:form.option at all and better performance.
10:38:37 <drlimbo> if i add the <flux:form.option.icon viewhelper, it crashes the "Tab-Layout" -> https://www.evernote.com/shard/s8/sh/b816c4ee-f9c1-4d60-b2c3-b486a1fde994/a51b7e56c46ddbddcb9ff5e73d36afd1/deep/0/ogbase--TYPO3-CMS-6.2.9-.png
10:39:04 <NamelessCoder> drlimbo then you don't have the most recent code and much of what has been suggested will not work
11:02:21 <drlimbo> i can't find a way to re-enable the messages (i changed debug to 1 or 2 in extension settings of flux)
11:02:45 <xaver> drlimbo: or take a look here https://github.com/bootstraptheme-for-typo3/fluidbootstraptheme/blob/development/Resources/Private/Templates/Content/Carousel.html
13:58:18 <pedda> i can solve my issue only if i revert fluidpages right before 28ac27f
13:58:48 <pedda> i tried to follow your explanation, which was a bit too much for me, but anyway
14:01:28 <pedda> as far as i can understand what happens on the mentioned lines 112 and 113 in PageLayoutSelector, there is no way to perform GeneralUtility::removeDotsFromTS($typoScript['plugin.']['tx_fluidpages.']) successfully if $typoScript['plugin.']['tx_fluidpages.'] is null
14:03:11 <pedda> i can'T explain why it is null, as i would expect the ts path to exist due to the em setting of EXT:fluidpages called basic.autoload
16:49:12 <jousch> Are there any plans to support dynamically precompile sass,less files combined with the assets viewhelpers?
17:31:53 <NamelessCoder> hey jousch - the plan is to have an extension that's dedicated to assets and uses assetic or similar as engine, but nobody seems to want to do it :)
18:28:17 <jousch> Thanks NamelessCoder, the question came up at the t3board15
18:33:20 <NamelessCoder> people ask it now and then :)
04:48:45 <trendzetter> I created a fluid content element in my provider extension: a form. How do I access the form values from my controller? Which method will my form submit call?
04:50:02 <trendzetter> Has anyone written about that? It seems to be missing in the docs
06:10:49 <trendzetter> just some feedback on my own question about capturing the postback from a form in fluid: http://extbaseblog.michelleretzlaff.com/category/extbase-frontend-forms/
07:58:38 <drlimbo> in the "page language-view" i have an addiotional content-row i never mapped somewhere -> Fluid Content Area -- is this a know bug? https://www.evernote.com/shard/s8/sh/89961fda-7a10-45ac-a4b5-783166ae3f67/92aee2d806d4882edfd5a971394d113f/deep/0/t3lang.jpg
08:05:00 <drlimbo> looks like its this bug https://github.com/FluidTYPO3/fluidpages/issues/212
08:13:10 <trendzetter> I have a fluid form which produces a link like this: index.php?id=3&tx_sbat_content[action]=create&tx_sbat_content[controller]=Post
08:14:47 <trendzetter> I am expecting a call of createAction in controller PostController but it appears that it is not called
08:15:39 <trendzetter> Is there a page which explains fluid postback handling?
08:35:56 <trendzetter> no one ? https://fluidtypo3.org/documentation/templating-manual/advanced-provider-extensions/custom-flux-controllers/controller-actions.html
08:36:06 <trendzetter> I don't seem to understand some of the docs
08:37:09 <trendzetter> it says I need a function myElementAction.. But in which file should it be placed?
08:38:16 <NamelessCoder> trendzetter sounds like you are making a custom plugin, so the flux controller bits are not that relevant to you
08:39:05 <NamelessCoder> the form URL you posted seems to call a Post controller which means you require an actual plugin
08:40:24 <NamelessCoder> if you already have that, the most common pitfalls causing your troubles are: 1) incorrect context; missing either pluginName, extensionName or other parameter on f:form, 2) plugin definition in ext_localconf.php does not allow the controller Post for that plugin.
08:41:47 <trendzetter> i don't have a post controller
08:42:14 <trendzetter> i am just picking some clues from different related manuals such as extbase
08:43:13 <trendzetter> i want to start from a basic form i added to the sample fluidcontent element
08:44:33 <trendzetter> and then send an email with the data from the form; preferable from within contentcontroller
08:46:31 <trendzetter> What are the minimum requirements to receive data from a form?
08:54:34 <NamelessCoder> in this case it sounds like you *may* be able to get by if you create a secondary action on a custom ContentController and making your form post to that action, but whenever you need to receive data, a full Extbase plugin is usually the better idea.
09:09:30 <NamelessCoder> my advise is to have a full extbase plugin for this. Using Flux's controllers works for simple stuff but it has limitations when it comes to form handling (because it emulates a plugin rendered through a plugin).
09:11:15 <NamelessCoder> I would keep the content read-only and the interactive stuff in controllers - gives you much better control over how the plugin acts when receiving input. And if you need input validation with feedback in the form there's really no way around a full plugin.
09:21:56 <jmverges> NamelessCoder, did you saw what I wrote about fluidpages?
09:22:21 <jmverges> Here we are 3 developers and we cannot select a Page Layout
10:37:06 <Guest|22275> Hi everybody. I have a problem and can't figure out what I'm doing wrong. I created a FCE and want to display it inside a new Tab in the 'New Content Element Wizard'. After clearing the caches through the toolbar on top my FCE is within the Tab 'Plugins' with neither a name nor an icon. When I now clear all caches through the Install Tool it is dis
10:37:06 <Guest|22275> played correctly. But when I clear the cache again through the toolbar on top it's broken again. Any ideas where I made a mistake? :)
05:04:52 <FFF> hi... anybody knows why <v:link.typolink> is not inserting 'c' before uid (for links to page element like ?id=123#c456)
05:06:21 <FFF> I'm getting just W3C invalid links like ?id=123#456
05:21:08 <rosieres> FFF: shwitch to html5 and your validation problem is gone
05:27:33 <FFF> rosieres: interesting workaround... but this is not compatible with non fluid/flux content elements...
05:29:20 <MartinBless> Good morning. Can I send JS with the ext:vhs "script" viewhelper to the <head> part of a page? https://fluidtypo3.org/viewhelpers/vhs/master/Asset/ScriptViewHelper.html
05:30:13 <rosieres> MartinBless: https://fluidtypo3.org/library/code-examples.html?tx_fluidshare_display%5Bgist%5D=19&tx_fluidshare_display%5Baction%5D=display&tx_fluidshare_display%5Bcontroller%5D=Gist&cHash=ca4eb1b45d865196a7e605f6a14f409f should answer your question
05:34:36 <rosieres> FFF: Dont see a reason why it should not work -> https://github.com/FluidTYPO3/vhs/blob/development/Classes/ViewHelpers/Link/TypolinkViewHelper.php
05:37:28 <MartinBless> rosieres: I don't understand. I'm just starting with Extbase and added ext:vhs. No ext:fluidcontent or flux. I just want the JS goto <head>, not footer.
05:41:42 <rosieres> MartinBless: line 24 is your friend. With v:asset you define it with fluid="TRUE" you set it inline inbetween from v:asset you place your script. What do you want to achieve?
05:42:32 <rosieres> set allowMoveToFooter="0" to not allow moving to the footer ... BTW
05:44:30 <FFF> rosieres: links from standard typo3 elements cointain /page/#c[uid] in the URL and elements processed with css_styled_content starts like id="c[uid]"
05:54:41 <FFF> rosieres: I think that there is some postprocessing of standard TYPO3 Link field which is missing in vhs TypolinkViewHelper... If I add parametr "section:" to <v:uri.typolink configuration="" it works... I'm thinking about extracting uid for "section:" from Link Wizard string using v:iterator.explode... Is this the only way? (except writing custom
07:20:19 <drlimbo> is there a way to Translate flux:form -> flux:field.text?
07:21:32 <rosieres> examine the github typo3org ... should be in there
09:29:07 <pi-phi> hi. I use fluid_content and want the defined icon to be displayed in the preview section (shown in web->page module).
09:29:07 <pi-phi> is there a var or viewhelper which resolves the current resource path? <v:extension.path.resources(extensionName:'myCes',path:'Icons' /> does not work for page-module as the page-module has the url <webroot>/typo3/sysext/cms/layout/db_layout.php instead of <webroot>/typo3/index.php
09:47:33 <trendzetter> does someone has a basic example to set up a simple form and process the submitted data using fluid/extbase?
09:48:21 <trendzetter> i tried the blog_example but it's not working and it seems to be old by now
10:39:44 <jost> Hi! I do my page template rendering with EXT:fluidpages. Now I'd like to access the fluidpages-properties of a page (known by uid) from another page. How do I do that? I can't find any ViewHelper that converts a flexform to an array, nor do I really want to do that...
10:44:20 <jost> Nevermind, ViewHelper <flux:form.data> is what I need
10:52:08 <trendzetter> just some feedback on my own questions an hour ago. I am despartely trying to learn extbase/fluid but I seem to have a problem getting started with basic examples
10:52:44 <trendzetter> the best current example seems to be the pluginextension efempty
10:53:07 <trendzetter> I am studying that now. will look further into that tomorrow
10:55:29 <NamelessCoder> trendzetter perhaps https://github.com/FluidTYPO3/fluidshare is a good example since it has a very specific purpose that's a lot like yours: accepting a form, validating the input (and displaying a list of received+validated items)e
10:55:42 <trendzetter> the most up to date docs seem to be only in german: http://docs.typo3.org/typo3cms/ExtbaseGuide/
10:56:13 <NamelessCoder> yeah, a lot of that going around
10:56:48 <trendzetter> ok. I will look into fluidshare tomorrow. thanks for the tip
10:57:01 <NamelessCoder> it's the simplest example I know of atm
11:45:43 <jost> Ok, I'm retrieving flexform data from another page, and get it parsed using the flex:form.data-ViewHelper. That works fine for most fields, but one field is a FAL-Field referencing an image. How can I get the image ID to render it?
11:46:42 <jost> Usually I use the something like this to get FAL fields: v:content.resources.fal(field: 'file') - but what should I fill into the "field" parameter here?
12:08:51 <jost> Ok, got it - you can use: {v:resource.record.fal(table: 'pages', field: 'image', uid: pageUid)}, where "image" is the name the field has in the flexform.
17:01:51 <FFF> why is flux:form mergeValues param DEPRECATED AND IGNORED? Wouldn't be nice be nice to have possibility of mapping flex fields to real tt_content table columns?
03:56:50 <denisdroid> Is it possible to optimize the default look of the backend layout to make it more compact in Typo3 6.2? (e.g. moving the headline to the grey bar which holds the quick access stuff)
03:57:38 <denisdroid> (the headline of the content elements)
08:19:52 <thyri0n> Forget it, figured it out after running all the extensions' update scripts
10:39:33 <Guest|22255> I created an accordion FCE (http://pastebin.com/JDpydUmY) and now have following issue: If I reorder the panels, the child elements stay in the previous order. Is there anything I missed?
10:55:02 <Guest|94863> Moin! Wie kann ich in einem Custom Fluid Content Element auf die Container Settings zugreifen?
15:30:03 <Guest|96226> Hy, is it ok to ask newbie Questions in here about "How to load my own Viewhleper"?
03:40:41 <Guest|60815> Hi! I created an accordion FCE (http://pastebin.com/JDpydUmY) and now have following issue: If I reorder the panels, the child elements stay in the previous order. Is there anything I missed?
04:50:09 <mrboe> @Guest|60815 searching - one moment
05:03:01 <Guest|60815> Ok, thanks. I'll give it a try :)
07:45:47 <mobilat> Hi, how can I slide content with FLUX/fluidcontent? for example: http://wiki.typo3.org/Content_Slide
08:00:07 <Nurbs> Hi, I'm currently setting up a new site with T3 6.2.9 and installed the most recent versions of fluidcontent(_core), fluidpages, flux and vhs, started a new template, set up the includes etc. and it's rendering fine in the FE. Also, my page layout options are displayed in the BE, but the BE is still showing left/main/right/border columns instead of the grid that I defined. What may I be missing?
08:01:04 <Nurbs> most recent => most recent that are available from the extension manager
08:03:33 <mobilat> check your page properties (root page) -> Appearance
08:06:31 <Nurbs> Oh, thank you, forgot about that one and didn't add it to my setup notes. Working now :)
08:21:45 <mobilat> I'm try to use the 'content slide'-function. How can I use this: styles.content.getRight.slide = -1 - but my FLux Content is at colPos=0 <flux:grid.column colPos="0" name="Slider" colspan="2" />
09:01:42 <drlimbo> hi there.. we have a Typo3 6.2.9 Installation with Flux 7.1.2 - but the Flux Debug (set on Mode 1) won't show any messages in backend =(
09:10:57 <drlimbo> someone has an idea whats wrong? maybe NamelessCoder?
10:10:48 <papillon6> Hey guys! Anyone ever tried to use l10nmgr with fluidcontent? l10nmgr does not export any content of type 'fluidcontent'.
08:39:35 <jmverges> PHP Warning: class_implements(): object or string expected in /home/vagrant/www/extensions/flux/Classes/Provider/ProviderResolver.php line 160
04:30:38 <denisdroid> Xatenev: Thank you. Do you know an wiki page or something like that with an overview of the default 6.2 tables and the purpose of each table
04:31:16 <denisdroid> I'm just thinking about which tables can be truncated when starting a new instance from an old one.
05:47:08 <fger> hi guys, is there no way to detect mobile devices using vhs viewhelpers anymore ?
05:47:16 <fger> i remember having a if.client.isMobile etc.
05:47:36 <fger> or can it now be solved with another "construct" ?
06:42:16 <fger> and 2nd question: I need to switch on a property of a content element in a v:content.render viewhelper
06:42:46 <fger> afaik i can only set render=0 or render=1 to get the record itself or the rendered content ... thus i have to call the v:content.render twice
06:43:41 <fger> is there a possibility, where i can iterate over elements inside the viewhelper, which contain the rendered html AND record-properties ?
06:49:48 <NamelessCoder> fger the client/browser conditions were removed because they can only ever work in an uncached context which makes their usefulness very limited. It's better to just do such conditions in the controller or as TS conditions (which makes the page cache contain another cached version per condition).
06:50:20 <NamelessCoder> and regarding the other one, if "condition" won't solve your use case then v:content.get + v:content.render
06:51:15 <NamelessCoder> strike that: v:content.get + v:content.render is the only way. No conditions for v:content.*
07:07:55 <NamelessCoder> it would only make sense if you disable caching for that page or redefine the top level PAGE object's configuration as USER_INT
07:08:28 <NamelessCoder> if you don't, the code only executes until page is cached. That's why TS conditions create a second cached version for each (combination of) condition
07:08:53 <fger> ok, but how could we "deliver" content-objects per column different for desktop/mobile (we use flags in content-elements) then ?
07:09:09 <fger> not use the v:content.render viewhelper at all ?
07:09:17 <fger> and do it with typoscript-objects ?
07:09:57 <fger> I mean, doesnt fluid(pages) create a different cache-version for i.e. various conditions ?
07:11:22 <NamelessCoder> first: you may be designing an approach that is not ideal. It might make more sense to replace the template paths via a condition than to modify each and every content element being rendered.
07:12:13 <NamelessCoder> second: no, we do not create a different cached version for each condition. Doing so would require us to render the template in order to determine which conditions apply - which completely defeats the purpose and is equal to fully uncached rendering of every request
07:13:15 <fger> ok, get that. to your first statement: We have to decide, WHICH contentelements are rendered on the page desktop/mobile
07:13:42 <fger> so if that cannot be decided inside the fluid-template, we have to go with typoscript-objects then
07:14:07 <fger> because we need to process the properties showMobile=yes/no etc.
07:14:17 <NamelessCoder> unless the elements are huge HTML outputs I suggest doing so with a CSS class on the container (possible in CSC as well as FCC) and eliminating that from display on mobile using your preferred CSS selector.
07:18:42 <NamelessCoder> if you use CSC: add an "if" sub-structure that evaluates the record's field, inside the general element rendering instruction inside a TS condition that applies only on mobile.
07:19:31 <NamelessCoder> if you use FCC: override or overlay the Layout used by content elements inside a TS condition, then make the overridden Layout file contain a condition that only renders anything if your record's field is disabled.
07:31:17 <fger> hmm... we use csc, so fluidpages still uses the content.20 etc. objects to fetch the contentelements ?
07:32:03 <NamelessCoder> yes, v:content.render will render the TS object associated with the CType/list_type of the record (that's all internal in the core)
07:32:19 <fger> ah fine, then we are done quickly i think :)
07:43:06 <fger> seems to work - maybe i should post a snippet to fluidtypo3.org ;)
04:54:32 <shaggz> Here's the gist for my template https://gist.github.com/tkasper/91fba32c85560850d178
05:45:27 <shaggz> Another problem I recognize is that my changes are not visible. I have to uninstall and then install the extension again. And I have set the configuration "Disable Fluid caching of Flux forms"
06:00:07 <cedricziel> the fluid cache gets reloaded in development context
07:36:31 <shaggz> @cedricziel I set basic.debugMode to 1 (flux configuration)
07:36:59 <shaggz> Thought that this should be sufficient
08:48:35 <s-andersen> I'm trying to assign a custom variable to my template in my provider extension, but I can't figure out how to do it. Have tried following this page, but get a "Cannot redeclare pagecontroller": https://fluidtypo3.org/documentation/templating-manual/advanced-provider-extensions/custom-flux-controllers/controller-actions.html
08:53:30 <cedricziel> shaggz: Development Context is for development. Production is for .. well. Production.
08:56:52 <cedricziel> Uhm. How does your controller look like, s-andersen?
09:03:26 <s-andersen> cedricziel: I think the problem was the way I registered my provider extension in ext_tables.php
09:04:09 <s-andersen> cedricziel: No not completely, because now I get: Template could not be loaded. I tried "/var/www/jvk.dk/ny/web/typo3conf/ext/flux/Resources/Private/Templates/Page/Default.html"
09:04:47 <s-andersen> Do I have to call the render() function in my pagecontroller?
09:06:50 <s-andersen> cedricziel:This is what my controller looks like: http://pastebin.com/cbQvqnCd
09:10:30 <cedricziel> Interesting. This shoud run in your extensions scope.
09:10:42 <cedricziel> NamelessCoder knows best around custom controller.
09:11:24 <cedricziel> btw. grabbing raw request parameters wont significantly improve your security
09:49:49 <s-andersen> Is there another way to assign a simple variable from PHP to a fluid template, than to make a controller in the provider extension.
09:56:22 <NamelessCoder> plus some other circumstances which are taken care of by PageController to make it perfect for pages
10:00:08 <s-andersen> NamelessCoder: something like this: http://pastebin.com/uSbnMDqW
10:00:31 <s-andersen> Returns no error, but it seems the function is not called.
10:00:54 <NamelessCoder> hmm now it's a viewhelper, not a controller
10:01:23 <NamelessCoder> or rather a controller placed in the viewhelper scope
10:01:43 <NamelessCoder> the things you should do, in order:
10:02:11 <NamelessCoder> 1) General note: you should use another vendor name than FluidTYPO3 and you should include this other vendor name in the calls to register your provider
10:02:59 <NamelessCoder> 2) Your controller should be YourVendor\Newjvk\Controllers\PageController and should extend FluidTYPO3\Fluidpages\Controller\PageController
10:03:34 <NamelessCoder> 3) Your action should be public (but it technically does not have to be)
10:05:00 <NamelessCoder> 4) Your template file and action should not be named "ProductID" and "productID" respectively. The uppercase "ID" part may mess with detection. UpperCamelCase is the appropriate template file naming (e.g. ProductId.html) and lowerCamelCase is appropriate for controller actions (e.g. productIdAction).
10:05:29 <NamelessCoder> 5) Your controller uses a raw GET argument; this should be left to the argument mapping of Extbase.
10:06:29 <NamelessCoder> 6) Your controller may, in a broader perspective, make more sense as an actual plugin that you insert on a page, rather than an emulated page template. It looks like you will be needing argument mappings and appropriate contexts, which means a proper plugin context is preferable.
10:07:18 <NamelessCoder> formalities: your controller action has @return integer which is incorrect. It should @return void.
10:07:44 <NamelessCoder> and your file uses a closing php tag which is no longer allowed according to the TYPO3 CGL.
10:08:01 <NamelessCoder> that should be everything, with medium detail ;)
10:08:18 <gbod> Hope that author's name in annotation is right. :D
10:09:08 <NamelessCoder> there's a LOT of side stuff to do with controllers ;)
10:12:29 <s-andersen> NamelessCoder: Thank you for you elaborate explanation. I began with a viewhelper, then thought a controller would be the better choice. I then mixed up the code in my editor and put the wrong thing on pastebin :)
10:12:40 <s-andersen> gbod: The authors name seems to be the only thing that is correct :)
10:13:13 <NamelessCoder> s-andersen I guessed that you were experimenting a bit ;)
10:15:15 <NamelessCoder> s-andersen I think that in the end, you will be happier with a proper plugin that renders your product info. You can, if you want to, limit the allowed CTypes in the fluidpages template so your product template is only allowed to contain for example your list or detail plugin.
10:16:33 <s-andersen> NamelessCoder: Am I getting close: http://pastebin.com/ZjfUPki8
10:16:43 <NamelessCoder> I've been doing that myself for as long as I can remember and it's the way that causes least "crap, have to rethink/redo that"-moments during developent
10:17:40 <NamelessCoder> when you register the provider extension in ext_* files, use 'JVK.Newjvk' as extension key
10:17:51 <s-andersen> Yep, I have already done that.
10:18:09 <NamelessCoder> your template file should then be Page/ProductList.html
10:18:18 <s-andersen> The code where I extended the AbstractFluxController provoked an error, so somehow my function got called. But now, the function doesn't seem to get called.
10:19:20 <NamelessCoder> s-andersen the problem when you only extend the basic controller class is that you will lack the tablename and fieldname properties that connect your Provider to the controller. You would either get no Provider in $this->provider or an incorrect one.
10:19:56 <NamelessCoder> alright - assuming the registration is okay and you've got template paths right, your controller should work
10:20:57 <s-andersen> I have \FluidTYPO3\Flux\Core::registerProviderExtensionKey('JVK.Newjvk', 'Page');
10:25:54 <NamelessCoder> if you select ProductList as template to use on a page, your controller should be called. But make sure you return something more than an integer or Extbase may see it as an empty result
10:27:14 <s-andersen> ProductList is selected and the template is rendered, but the variable I assign is not displayed. And if I place a die() function in the code, the template still renders. Seems like the function is not processed
10:28:12 <shaggz> Hey NamelessCoder, I have a problem that my provider extension does not recognize changes like adding a new content element template. I set basic.debugMode to 1 (development) but I have to uninstall and reinstall the extension.
10:28:14 <s-andersen> I had some "returns" from my viewhelper attempt
10:28:49 <shaggz> I created the provider extension using the builder extension. Is there anything I have to register manually?
10:29:34 <shaggz> In former version I just had to add a new html file but that does not work this time and I use the newest versions of flux, fluidcontent etc
10:30:45 <s-andersen> NamelessCoder: Thank you for your help!
10:32:21 <NamelessCoder> you're welcome, hope it works!
10:33:13 <NamelessCoder> shaggz you probably either need to clear the system cache or there's some error in your template.
10:33:26 <NamelessCoder> fluidcontent caches pageTSconfig in the "system" group
10:34:07 <shaggz> I tried to clear general caches and manually cleared typo3temp/Cache/*
04:20:29 <s-andersen> I have created a controller for my provider extension, to pass on a GET var to template. However, it seems that fluidpages cache the result of the controller on a per page basis. So the code only works when the page is uncached i.e. backend user is logged in. Any ideas on how to prevent this?
05:36:49 <cedricziel> enable no_cache in the page properties?
06:31:25 <s-andersen> cedricziel: Thank you for the hint. I remembered that fluidpages in page.5 is defined as a USER function. Using typoscript to convert it to USER_INT when the GET-var is present did the trick
06:54:19 <benjamin_654> yes, the element goes to the new position but after a reload it is not moved
06:54:57 <cedricziel> pls report an issue in fluidcontent
06:55:51 <s-andersen> cedricziel: development context doesn't work either. Well if it disables all cache it does the same as setting no_cache in page properties. Or actually it performs a little bit better, because the page is cached, but not when the parameter is set.
06:55:55 <benjamin_654> i am not sure what the cause is, i would first like to have this confirmed by someone else
06:56:29 <cedricziel> pls report an issue in fluidcontent
07:03:29 <cedricziel> I dont know why so many people fear issue creation. my coworker himself is too shy and wastes hours and hours trying to find solutions in software made by 3rd party.
07:04:41 <benjamin_654> most of the time when something does not work its not a bug but a wrong configuration on my side..
07:05:23 <cedricziel> we dont judge you, nobody does. Even if there is an easy solution, issues are legit questions and completely neutral
14:25:44 <Guest|66332> hi together, how can i use info of a field form individual page Configuration (e.g. input-field within section Configuration) within the viewhelper vhs v:page.menu?
14:29:04 <Outdoorsman> I'm not sure if this is what you're talking about but I believe this might be what you're looking for... <v:page.menu entryLevel="{settings.entryLevel}" useShortcutData="TRUE">
14:37:48 <Guest|66332> not exactly ... <v:page.menu.directory as="menu" pages="23"> within I can iterate through all items with <f:for each="{menu}" as="menuitem"> ... and i can use for example {menuitem.uid} ... but i dont know how to use the information of the flux-page Configuration, which is saved in a flexform
14:41:58 <NamelessCoder> Guest|66332 see https://fluidtypo3.org/viewhelpers/flux/master/Form/DataViewHelper.html
14:49:22 <Guest|66332> thanks ... but i am afraid i dont see how to use this within <v:menu ... (i am not a "hard coder") ... are there examples how to use it somewhere?
14:56:42 <Guest|66332> i tried it this way: within <v:page.menu .. ... <flux:form.data table="page" field="tx_fed_page_flexform" uid="{menuitem.uid}" record="{field: 'settings.keyvisual'}" \>
14:57:27 <NamelessCoder> you'll need to combine that viewhelper with manual rendering of menus - there's an example of the menu rendering here: https://fluidtypo3.org/library/code-examples.html?tx_fluidshare_display%5Bgist%5D=2&tx_fluidshare_display%5Baction%5D=display&tx_fluidshare_display%5Bcontroller%5D=Gist&cHash=d501a3d334ac0d9a1b6a00fa8f3da8b4 and you then add flux:form.data inside the f:for (it works the same way as f:for, with an "as" argument) and supply table
14:57:27 <NamelessCoder> and record arguments. Table is pages and record is of course each menu item.
15:06:45 <Guest|66332> ok thanks, the menu-example i did use already, and i am very happy about these expamles, i will try ...
15:41:24 <Guest|66332> @NamelessCoder ... Thank you ... I seems to work ;-)
13:33:11 <Outdoorsman> Do you guys put plugin.tx_vhs.settings.asset in a TYPO3 typoscript template in the backend or do you put in your provider extension?
17:29:07 <Outdoorsman> I just changed to Flux development and am having trouble with template overlays.
17:30:12 <Outdoorsman> This isn't working any more... plugin.tx_fluidbootstraptheme.view.overlays.provider_extension.templateRootPath
17:36:13 <Outdoorsman> I see that NamelessCoder mentioned something about templateRootPath here in the IRC logs... https://fluidtypo3.org/community/irc-logs.html?tx_fluidtypo3org_content%5Bdate%5D=20141204&tx_fluidtypo3org_content%5Bcontroller%5D=Content&cHash=fffdfc03c21b8aea6f0be944b041e18b#22:37:27
17:37:01 <Outdoorsman> Also NamelessCoder mentioned some things about overlays in a recent blog post: https://fluidtypo3.org/blog/news/coming-changes-in-flux-72.html
17:40:35 <Outdoorsman> I see mention the plurl option (templatRootPaths) in the blog but I didn't see the other one was deprecated... thoughts?
17:51:42 <NamelessCoder> there might be some bug hidden in the way it processes those paths though. What is the complete TS inside plugin.tx_fluidbootstraptheme.view?
18:01:30 <Outdoorsman> Okay NamelessCoder, I'm not trying to take up your time, but I'm trying to figure out what I'm doing wrong... here's a Gist:
18:05:16 <Outdoorsman> It's way to long but haven't got a better method yet I guess.
18:05:49 <NamelessCoder> could you try switching those templateRootPath etc. to templateRootPaths? syntax would be plugin.tx_fluidbootstraptheme.view.templateRootPaths.0 = EXT:...
18:06:15 <NamelessCoder> then add the paths currently set in "overlays" as plugin.tx_fluidbootstraptheme.view.templateRootPaths.10 and set it after the other one
18:06:52 <NamelessCoder> this is the new default approach in Fluid and may be more compatible. I'm not sure if all the corners of singular paths + overlay were tested...
18:07:37 <NamelessCoder> you *may* need to do plugin.tx_fluidbootstraptheme.view > before your own definition - not sure which TS is added by the ext.
18:08:28 <NamelessCoder> last thing is to make sure your ext's TS is loaded after fluidbootstraptheme's TS (just to eliminate possible problems with priority)
18:08:44 <Outdoorsman> I have made sure it was loaded last in the TS template.
18:09:09 <NamelessCoder> yeah, usually a good idea with providers :) just put them last :)
18:10:56 <Outdoorsman> So is all that stuff necessary in my Gist at the beginning?
18:12:57 <NamelessCoder> you don't have to define the view paths for your own provider, but if you need to reference those paths in other setups (like overrides of EXT:news template paths) then storing them in a constant may be a good idea
18:13:37 <NamelessCoder> and afaik you don't need the widget sub-configuration at all
18:13:59 <Outdoorsman> Good it's getting nixed now.
18:14:57 <NamelessCoder> sounds like the .overlays way is broken...
18:15:37 <Outdoorsman> I updated my gist and it still doesn't seem to work.
18:16:03 <Outdoorsman> I changed to templateRootPaths.0 = ______
18:16:26 <NamelessCoder> if you use the TS object browser, is plugin.tx_fluidbootstraptheme.view.templateRootPath still defined?
18:16:53 <Outdoorsman> I'm not a pro at that tool... I'll do my best to check using that.
18:19:36 <Outdoorsman> Yes it is still set. I'm using fluidbootstraptheme development.
18:21:54 <NamelessCoder> start with a plugin.tx_fluidbootstraptheme.view >
18:22:08 <NamelessCoder> then you remove all the old paths and your own view object becomes the only one
18:23:37 <NamelessCoder> I think the issue is support for the old fallback paths combined with overlays - that's the one case I don't have in my own test setup from back when testing it
18:24:02 <NamelessCoder> I'm investigating that here as well
18:25:15 <Outdoorsman> I've added that and it's still not working... see my updated Gist to see what I did.
18:34:25 <NamelessCoder> just to make sure we are 100% in sync, would you mind sending me your provider extension and while I check, update flux, fluidcontent, fluidpages and fluidcontent_core if you use it.
06:00:45 <feelx75> Hi Channel :) I'm using Flux/fluidtypo3 github (dev branch) and T3 6.10-rc1. Is there any known issue with drag and drop of content elements between flux columns. Sometimes the green 'destination-bar' is missing. Sometimes the dropped CE disapear. CE are normal T3 elements (text/header or images).
06:48:24 <Kaimane> Hey guys. Trying to get json data via ajax from extbase controller action. How to disable the "parsetime" output in the last line?
06:49:30 <Kaimane> Set ['FE']['debug'] to 0, config.debug = 0 but parsetime is still rendered.
07:22:54 <Torsten85> hey... is it possible to specify fluidcontent elements with "allowedContentTypes" inside flow:grid?
08:22:12 <feelx75> Torsten85, you mean flux:grid, right?
08:22:48 <feelx75> Torsten85, please refer to: https://fluidtypo3.org/blog/news/coming-changes-in-flux-72.html - See Typoscript overrides (at the bottom)
08:23:31 <feelx75> Torsten85, "Although this feature is still on the drawing board and cannot be described in detail (...) will for example allow the integrator to use TypoScript to control which page/content template may be used, as well as selectively override settings like the sorting value of Fluidcontent elements or the allowed content types inside a Fluidpages-enabled page template's Grid.
08:25:09 <feelx75> I think there will be a feature sometimes... i.E. with the flux:form.options VH. Actually I don't know a way... but just found this above in the blog
08:32:10 <NamelessCoder> Torsten85 set on flux:grid.column, attribute options="{Fluidcontent: {allowedContentTypes: 'C,S,V'}}" where the C,S,V part is a comma separated values list of tx_fed_fcefile values that are allowed.
08:40:48 <Torsten85> NamelessCoder thanks for your help, but I can't get it to work. Is there an example somewhere?
08:48:10 <Torsten85> I think I missing something. How should the variables attribute on a flux:grid.column tag look like if I only want to show one specific fluid content element? all other elements (text, image ....) should be hidden
08:54:05 <Torsten85> NamelessCoder Me again.. I think I found a bug! here you return the array key "tt_content": https://github.com/FluidTYPO3/flux/blob/development/Classes/Hooks/WizardItemsHookSubscriber.php#L111
08:54:39 <Torsten85> but here you still traverse to that key (which is non existent) https://github.com/FluidTYPO3/flux/blob/development/Classes/Hooks/WizardItemsHookSubscriber.php#L138
09:01:41 <feelx75> Torsten85, maybe it works like this? https://www.snip2code.com/Snippet/198359/Allow-Deney-Fluid-Content-FCE-s-in-colum
09:14:08 <Torsten85> feelx75 yes this works for columns inside page templates but not inside content templates due to the bug i mentioned.
09:16:54 <cedricziel> Torsten85: Give me a second to traverse your previous conversation :9
09:17:22 <Guest|66253> hi i use v:page.menu to build an menu... my menu does not include the L param for languages... when i use v:page.languageMenu to build a language-menu it is included... are there any settings for v:page.menu to support languages?
12:43:51 <shaggz> Hey guys, is there a way to simply link the sections in a fluidcontent element?
12:44:47 <shaggz> I'd like to set an anchor for some content elements to jump directly to tit
12:48:27 <NamelessCoder> I don't think it's possible but you can of course always manually type an anchor link
12:50:04 <shaggz> Would you recommend to use fluidcontent_core instead of csc?
12:50:24 <NamelessCoder> it completely depends on your requirements for other exts.
12:50:44 <NamelessCoder> a lot of other exts depend on csc and you can't use both at the same time
12:51:20 <NamelessCoder> if you prefer TS to define how your content should be rendered, CSC is your friend. If you prefer Fluid, FCC is the better choice.
12:53:05 <shaggz> Okay, then I have to check if I have to choose CSC because I really don't like the TypoScript ;)
12:53:39 <NamelessCoder> plan your dependencies ahead, then there won't be any headaches later ;)
14:20:55 <f000> Hello... I'm trying development branches of flux, vhs, fluidcontent and fluid pages because of performance issues with (now deprecated) flux.widget.grid. After upgrade I can't see any elements in Page->Columns view. It shows just "(Not assigned)" in the content area... Do you have any clue how to solve it?
14:23:32 <NamelessCoder> f000 did you read https://fluidtypo3.org/blog/news/fluidcontent-and-fluidpages-released.html?
14:26:18 <f000> NamelessCoder: sure, with master branches of flux etc. there were no problems
14:30:21 <f000> NamelessCoder: if I select "Page Layout: Fluidpages" there is no content and if I select "Page Layout: None" there are 4 columns with content my FCEs in the Normal column
14:40:50 <NamelessCoder> did you also see https://fluidtypo3.org/documentation/templating-manual/appendix/migration/to-flux-71.html#after?
15:01:36 <f000> NamelessCoder: my page template is like <f:section name="Configuration"><flux:form id="default">...</flux:form><flux:grid><flux:grid.row><flux:grid.column /></flux:grid.row></flux:grid></flux:form></f:section>
15:01:55 <f000> NamelessCoder: I think this might be the problem
15:02:16 <NamelessCoder> your flux:grid.column must have a columnPosition value
15:04:19 <f000> NamelessCoder: This looks like I need complex update of tt_content table :(
15:05:20 <NamelessCoder> SQL schema? If so, that's definitely important
15:14:09 <f000> NamelessCoder: I thought to change tt_content colPos... but I was wrong.. now I tried to just add colPos parametr and it works!!! thank you!
15:37:00 <NamelessCoder> it should contain a vendorName entry, that block
15:37:53 <NamelessCoder> if you have a provider extension which contains controllers and those controllers extend that old class, change it to the new one
15:43:12 <f000> yes vendorName was the issue... now everyting works... thank you again!
15:45:40 <f000> NamelessCoder: can you say when we can expect relase of Flux 7.2?
16:16:21 <NamelessCoder> well it all depends on how quickly we can get the last issues closed - if you want to take a look at some of it, the todo list is: https://github.com/FluidTYPO3/flux/milestones/7.2
16:17:08 <NamelessCoder> you can also help just by testing the reported problems in those issues - some may have been closed by other fixes
17:24:15 <Outdoorsman> I'm getting this error from my provider extension which overlays fluidbootstraptheme...
17:24:44 <Outdoorsman> #1225709596: The template files "/home/some_directory/public_html/typo3conf/ext/fluidbootstraptheme/Resources/Private/Layouts/Page.html", "/home/some_directory/public_html/typo3conf/ext/fluidbootstraptheme/Resources/Private/Layouts/Page", "/home/some_directory/public_html/typo3conf/ext/provider_extension/Resources/Private/Extensions/Fluidbootstraptheme/Layouts/Page.html", "/home/some_directory/public_html/typo3conf/ext/provider_extension/Resources/
17:24:44 <Outdoorsman> Private/Extensions/Fluidbootstraptheme/Layouts/Page" could not be loaded.
17:25:33 <Outdoorsman> There's a more information link that points to this info: http://typo3.org/go/exception/CMS/debug/1225709596
17:28:59 <Outdoorsman> I have no idea why it's looking for Page.html, that file doesn't exist in my provider extension and the text "Page.html" doesn't exist anywhere in any of the other files. I don't get this error when I uninstall my provider_extension, so fluidbootstraptheme is working properly.
17:36:58 <Outdoorsman> Here's an error in Apache error log...
17:37:00 <Outdoorsman> PHP Fatal error: Class 'Tx_Fluid_Core_Parser_SyntaxTree_TextNode' not found in /home/some_directory/public_html/typo3conf/ext/view/Classes/Override/Parser/SyntaxTree/ExtendedViewHelperNode.php on line 86, referer: http://www.example.com/typo3/backend.php
17:38:09 <Outdoorsman> I'm still working on the same issue from yesterday NamelessCoder though this error started happening when I uploaded the extension you modified for me.
17:39:18 <Outdoorsman> I'm using PHP 5.4.16, Apache 2.4
18:20:59 <NamelessCoder> yeah - I assume you're just using it for EXT:news so do the same with that as you did with fluidbootstraptheme to override templates without having to copy all of them
18:23:29 <Outdoorsman> Okay... I've uninstalled view and modified setup.txt.
18:24:15 <NamelessCoder> don't forget to unset the existing view setup like the other one - I'm not sure it uses the plural names for paths.
18:25:55 <Outdoorsman> Ahhh I was wondering about that very thing, the plurl paths thing.
18:26:57 <NamelessCoder> the singular naming is considered legacy and gets used as fallback
18:28:03 <Outdoorsman> Well I'm still gettting the same "The template files __ ___ ___ __ could not be loaded."
18:31:49 <NamelessCoder> with the right paths or the ones from EXT:news only?
18:32:49 <Outdoorsman> I don't even ahve EXT:news installed or configured on this site yet.
18:43:35 <NamelessCoder> Page.html doesn't exist in fluidbootstraptheme/Resources/Private/Layouts/ here in my copy. Did you create it in your own Layouts folder? If not, it is expected to fail.
18:44:06 <NamelessCoder> possible Layouts are: Content, ErrorPage, FCE, FrontPage, Render or WithSideBar
18:44:30 <NamelessCoder> you probably want one of the FrontPage, Render or WithSideBar values as <f:layout>
18:53:51 <NamelessCoder> but another Q is: are you sure you want to add a *new* page template selection instead of *replace* an existing one from fluidbootstraptheme?
18:54:23 <NamelessCoder> if you want to *replace* you need to rename the file so it matches the name of the template file in fluidbootstraptheme - and you should make sure to use the same "id" value for flux:form in your override.
18:55:39 <NamelessCoder> in particular, "Render" may be a very bad name to choose as it also matches the default action used to render the page. You'll be better off in the long run with more appropriate names. Name length is not an issue ;)
18:56:07 <Outdoorsman> So I think that Templates/Page/Render.html and Templates/Content/Example.html were both created when I used Builder to create the provider extension and that <f:layout name="Page" /> was still in there from Builder.
18:56:41 <NamelessCoder> yeah I think Builder is actually creating that file. It needs a touch-up too, because it sets the old singular name template paths
18:56:42 <Outdoorsman> I can just delete Templates/Page/Render.html if I haven't customized it right?
18:56:58 <Outdoorsman> It will fall back to the fluidbootstrap theme one.
18:57:16 <NamelessCoder> if you delete the file and any pages currently have it assigned as template file and it doesn't exist in fluidbootstraptheme then yes, an error will be shown (until you select another page template)
18:57:53 <NamelessCoder> in this case it does exist so that should be fine
18:58:42 <Outdoorsman> Well I'm out of time now. I have an appointment to be at thanks for your help. I'm not getting that template errors any more although the overlay doesn't seem to be working yet. At least I can move on to debugging that now. What an ordeal a simple line made.
18:58:56 <Outdoorsman> I would NOT have understood that without you.
18:59:12 <Outdoorsman> I have to run... have a good one and thanks for the help again!
18:59:21 <NamelessCoder> it's easy to get off track and not really see it until much later, after you've been through everything else
03:15:57 <feelx75> good morning. When I copy a CE I don't have a "paste-after icon" anymore between other CE's. I have only a paste-in-icon on the top of the page. What could cause this? I have to paste it on the top and move it... this way it works... but why?
07:53:06 <matt1808> Hi Everyone. I am having a problem with inheritance of values in page templates. I need to disable the inheritance of certain values to subpages. Ive tries adding inherit="FALSE" inheritEmpty="FALSE" and inherit="0" inheritEmpty="0" and various combinations but not had any luck. How can I do this?
08:42:44 <matt1808> Can anyone help with my inheritance problem??
08:50:12 <matt1808> The case I am looking at is to do with the inheritance of objects within a section in the page configuration. I am using this to add multiple buttons to the top of the screen. Basically I dont want these buttons replicated to child pages.
08:55:14 <NamelessCoder> matt1808 this stackoverflow thread may be of use to you: http://stackoverflow.com/questions/22073264/section-in-fedext-fluidpage
08:57:57 <NamelessCoder> the TL;DR - our only way to achieve inheritance is through default values of fields and those exact types of fields (section, object) don't support default values (e.g. a list of fields which must be created if no value is saved).
08:58:52 <Guest|57732> Hi. I'm running in a problem deploying a website to a customers site. It seems that the vhs-Viewhelpers doesn't produce any output. Any ideas where to figure this problem out?
08:59:05 <Guest|57732> local and on staging it works perfect.
08:59:27 <NamelessCoder> Guest|57732 if by vhs viewhelper you mean the v:content.* ones, then there are two things to check:
08:59:57 <Guest|57732> <v:content.render column="1" /> is the problem, correct
09:00:01 <NamelessCoder> if you use CSC, make sure the extension is installed and you have the TS from it loaded (and that you don't destroy the TS somehow through site setup)
09:00:18 <Guest|57732> we use fluidcontent_core instead
09:00:23 <matt1808> Thanks, my problem is that it is beign inherited. I have https://gist.github.com/anonymous/0d32bc986aa91a1a7a57 in a partial that that is used by all page templates. If I look at the page config of a sub page, it is empty but when i look at the front end, it is inheriting the configuration from the parent page
09:00:35 <NamelessCoder> if you use FCC, make sure the typo3conf/AdditionalConfiguration.php file was created and contains the code from FCC's shipped file, make sure FCC is installed and finally, make sure the TS is loaded.
09:01:12 <Guest|57732> hmm. I'll double-check this, but I'm pretty sure it should be in place...
09:01:16 <NamelessCoder> key difference: typo3conf/AdditionalConfiguration.php - can be initialised by running the update script for FCC via EM.
09:01:50 <matt1808> The partial in the frontend for adding the buttons - https://gist.github.com/anonymous/7cc94b65bc129255ab2c
09:01:58 <NamelessCoder> if you have pending DB schema changes that would make queries on tt_content fail, fix those of course. It may not break the BE but still prevent FE from loading records.
09:02:43 <Guest|57732> db compare tracks no issues...
09:02:58 <matt1808> Is the problem with the way I am referencing the objects in the front end??
09:03:04 <NamelessCoder> matt1808 correct - the problem with support for inheritance is entirely in the editing of the fields. We can't pre-fill sections with objects so you won't see what you would get in FE when you edit in BE.
09:04:01 <Guest|19542> sorry; accidentally closed this window. ;-)
09:04:34 <Guest|19542> thanks for your help; you were right about additionalConfig - the customers it has overwritten these...
09:05:05 <NamelessCoder> the stackoverflow thread has an alternative suggestion which builds on content sliding and a custom content element in a custom colPos - it's approximately the same amount of overhead and editing complexity, but explaining it to editors is very different in the two cases...
09:06:42 <NamelessCoder> matt1808 it's less than ideal but it's the best we can do under the circumstances of TCEforms ;)
09:07:22 <matt1808> Would you suggest moving this to a CE rather than in page configuration? Is there a way to check for the objects exist on the current page?
09:10:42 <NamelessCoder> I would actually let this be decided by your customer. The CE slide solution is good if you know that the customer will want to change these at points in the page tree, but it is somewhat harder to explain to the customer how that will work. The page inheritance solution is good if you expect these objects to only be defined and changed on the top page and never on sub pages and you can explain to the customer that even though the section/object
09:10:42 <NamelessCoder> is empty on sub pages in BE, it will still be available in FE.
09:12:42 <NamelessCoder> I suspect your use case sort of treats these objects as if they were practically content elements that you edit inline, are inherited and have very simple options. So using CE+sliding is sensible here - assuming you can educate your customer ;)
09:19:07 <matt1808> Hmmmmm... time to have a rethink about this. I think adding a CE might make it more difficult for the editors to know what they are doing. As the number of this buttons will be limited to a max of three, I might try removing the section/object configuration and then use three sets of fields for button1, button2 etc. This would then allow for the in
09:19:07 <matt1808> heritance of these fields to be managed??? I'll give it a go and see what happens, if not, a CE it is. Thanks for your help with this. Cheers
09:21:45 <NamelessCoder> matt1808 makes perfect sense to use three sheets if you're already wanting to fix the number of buttons
09:21:56 <NamelessCoder> since sections don't support maxItems that's perhaps an even better way
09:32:41 <matt1808> I'll give it a go. Thanks for all your help
09:46:15 <matt1808> One final question. i have named my varaiables settings.button1.text, settings.button2.text etc. Is there a way to loop though these with a for statement incrementing the number, rather than creating three <f:if condition="..." statements?
10:06:07 <Guest|57655> When i add the "enabledControls" param to my IRRE in my FCE Configuration i get the error "Wrong configuration in table tt_content" when i try to add new relation records.
10:06:12 <Guest|57655> My Code: <flux:field.inline
10:25:02 <fger> hi guys, how can i access the iterated array/object for options inside a f:form.select or v:form.select viewhelper in the fluid template ?
10:25:23 <fger> use case: we want to add a data-parent attribute to each <option> - element
10:25:48 <fger> its value should be the key of the current rendered option
10:27:51 <Guest|57655> @Xatenev: heres the pastebin http://pastebin.com/9bkjP3mH
10:28:31 <Guest|57655> Once i add the enabledControls param the error appears. If i leave it empty ("{}") or dont add it it works fine (i need the delete option as the hide option actually doesnt work)
10:34:58 <Guest|57655> i see my error beign discussed several times in this channel but never a solution was logged.
10:35:06 <Guest|57655> does noone have any intel on this?
10:36:31 <Guest|57655> the enabledControls actually work and the delete icon is correctly shown and it works
10:36:38 <Guest|57655> but once i add the setting i cant add new records anymore
10:37:16 <Guest|57655> the main issue why i found this issue is the fact that hiding records in a FCE based inline relation doesnt work at all
10:37:28 <Guest|57655> the records gets shown hidden and once i save and reload its unhidden again
10:46:41 <Guest|57655> So i think i have to use the workaround and hide/delete records using the WEB=>List view as the constellation of IRRE inside Flexform inside FCE is not working.
10:51:00 <fger> anyone can answer the data-attribute / option -array question ?
11:12:54 <Outdoorsman> fger maybe additionalAttributes="{foo: 'bar'}" is what you're looking for? https://fluidtypo3.org/viewhelpers/vhs/master/Form/SelectViewHelper.html
11:13:31 <Outdoorsman> I haven't tried using this, I just browsed the documentation looking for something that looked like it might be what you're looking for.
11:29:50 <fger> well, yes, but how can I access the option-keys/values for the current loop inside the v:form.select.option viewhelper for example ?
11:30:00 <fger> i wanted to stay inside the fluid template
11:41:31 <Outdoorsman> I can't get overlays to work for the life of me!!! Don't know what I'm doing wrong. Everything looks correct.
12:30:22 <NamelessCoder> Outdoorsman how much have you solved so far? Still trying to overlay page templates?
12:31:19 <Outdoorsman> I'm stiiiiill trying to get overlays to work.
12:34:21 <Outdoorsman> This is totally ignored... overlays.provider_extension.templateRootPaths.10
12:35:07 <NamelessCoder> yes - that is by design; the "overlays." array only supports the singular naming (they were invented to allow multiple paths before the plurals were possible)
12:36:20 <NamelessCoder> you should be adding these paths directly in "view." of the extension you want to overlay, just skip the whole "overlays.provider_extension." part.
13:38:25 <frustration> Greetings, I'm trying to use T3 6.2.9 and "FluidTypo3", however I'm struggling with viewhelpers not beeing loaded. Are the extensions listed in TER all compadable with 6.2.9 or do i have to use specific versions of the extensions together ?