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.