12:32:57 <erredeco> removing titleFields="'nav_title,title'" --> the text of link becomes nav_title, but the "title" attribute is title
12:33:31 <erredeco> if I explicit titleFields="'nav_title,title'" then both text and title attribute are title field
12:44:31 <JustAPoring> Hi guys. Is it possible to do something along the lines of {object.{key}}, or is there a viewhelper already available for something along those lines?
12:45:08 <JustAPoring> In fluid, that is, in case that wasn't clear.
12:49:39 <Guest|76921> Is there a ViewHelper to get Values from Flexform fields?
13:08:28 <NamelessCoder> just practicing my sniping :p
13:10:19 <NamelessCoder> JustAPoring the answer to your question is v:variable.get (assuming you use the development branch, in TER it's still v:var.get)
13:10:47 <NamelessCoder> {v:variable.get(name: 'myobjectname.{dynamicVariablePart}') -> v:variable.set(name: 'newVariableName')} for example
13:12:00 <JustAPoring> NamelessCoder: Duh, of course. Thanks a bunch.
13:12:34 <NamelessCoder> by the way, the reason why that works is ObjectAccess::getPropertyPath is used
13:13:16 <NamelessCoder> you may find that relevant if you ever need to for example extract a deep TS path from a full typoscript array - $value = ObjectAccess::getPropertyPath($fullTypoScript, 'plugin.tx_myext.settings.variable.foobar');
13:13:35 <NamelessCoder> it also works with flexform arrays ;)
16:21:09 <xaver> what is the argument stack - it is not registered
16:31:54 <Outdoorsman> Hmmm so now that files in fileadmin are tracked... where is the appropriate place to put my customized extension file overrides?
16:37:26 <Outdoorsman> I noticed that in the TYPO3 bootstrap demo it's set up like this...
16:44:03 <Outdoorsman> erredeco I'm very new to vhs still, but when I found the only way to have multiple conditions for one statement like you mentioned aboved was to nest them.
16:54:55 <erredeco> Is it possible to use this value in a typoscript object (like a TMENU ;) )?
16:56:28 <erredeco> @outdoorsman - about your question - I'm using the approach suggested by fluidtypo3 and built an extension that provides the configuration for the frontend :)
17:02:52 <Outdoorsman> erredeco So about extension customization, you're saying that for every extension I customize I need to create a "provider extension"?
17:04:00 <erredeco> usually an extbase extension has some typoscript constants that let you decide the path where to retrieve your templates/layouts/partials
17:04:42 <Outdoorsman> Yes, I could just set those to something like fileadmin/ext/news/Templates/ for example.
17:05:11 <erredeco> ok instead of fileadmin/etc/etc
17:05:26 <xaver> Outdoorsman: i think so - but every condition needs cache and will be rendered on every subpage
17:05:47 <erredeco> use as path: EXT:yourproviderextension/Resources/Private/Ext/news/templates/
17:06:25 <xaver> Use a provider extension, clean package no access for customer, htaccess rules are secure /Resource/Private
17:07:05 <xaver> no fileadmin in git and a lot of other advantages
17:07:35 <Outdoorsman> Ahhh just one provider extension segregated into subdirectories for each customized extension.
17:08:39 <Outdoorsman> xaver Yikes... TS caching could add up if there's a lot of conditions or at least specific ones. But that would be the case for fluid as well I suppose.
17:10:05 <xaver> Outdoorsman: TS rendering is really slow. its not a XMl rendered, implemented in php and optimized - its text, rendered to a giant array
17:10:49 <xaver> also use view extension if you use news or powermail. Overwrite only needed templates partials...
17:11:17 <Outdoorsman> I do have view installed but had already forgot why :)
17:17:25 <xaver> 6.2 has a new implementation, but something was a disadvantage. You can use view for all extensions.
17:18:47 <erredeco> I'll try ASAP to unleash the power of view.overlays !!
17:20:03 <xaver> fluidcontent_core isn't released, but works. It will get rid you the div div div, also text with image. Allows you to have different versions and variants.
17:22:21 <erredeco> as far as I can see from the documentation of view the correct syntax is:
17:22:21 <Outdoorsman> xaver Are there plans for a conversion script down the road to move from CSS Styled Content to fluidcontent_core?
17:23:53 <erredeco> at least because I'm not very happy with the CSC rendering
17:24:13 <Outdoorsman> I'll jump on the fluidcontent_core bandwagon but not until I know it's stable and is going to be around a looooong time. I don't want to have to migrate content manually for 50 websites down the road.
17:29:27 <Outdoorsman> Porting script. Port CSS Styled Content content elements to fluidcontent_core content elements.
17:29:44 <xaver> you can uninstall csc and install fluidcore_content - only "problems" are text with image and also if you relay on some standard classes. You need to added them in your template.
17:30:16 <xaver> you cant convert text with image, because it depends on your solution
17:31:25 <xaver> Why text with image is gone - You can't style every possible case, Customers are able to destroy the layout, not really responsive
17:33:05 <Outdoorsman> So if I have csc installed and create a Text Only CE, then uninstall csc and install fluidcontent_core, the CE will just work?
17:34:46 <xaver> Outdoorsman: maybe some styles classes you need to set, you have no avoidable tags.
17:34:56 <xaver> also images and other stuff works
17:45:17 <Outdoorsman> Soooo excited to hear about that. I thought fluidcontent_core was a breaking solution but it sounds more like a native solution???
17:46:25 <xaver> csc is a extension and it can be replaced. its deep in TYPO3, but it is possible
17:47:38 <xaver> a switch is not so easy and a lot of people want csc. Maybe if fluidcontent_core grows in popularity a own solution from T3 core will be planed. I don't know.
17:48:58 <Outdoorsman> I bet it will get more popular, but until it has good following and is stable the big-timers may drag their feet a bit.
17:49:30 <Outdoorsman> Anything to get away from inline styles would be good.