04:35:29 <jagmanetta> After updating my fluid/vhs extensions I have an error while editing pages from backend
04:35:45 <jagmanetta> This is the exception message: #1289386765: Could not analyse class:Tx_Vhs_ViewHelpers_Extension_Path_ResourcesViewHelper maybe not loaded or no autoloader?
04:36:36 <jagmanetta> I readed that I need to disable extensions that contains the namespace declaration like {namespace v=FluidTYPO3\Vhs\ViewHelpers}
04:37:14 <jagmanetta> I've done it, but the only one extension that use that namespace in my extensions list now is the fluidcontent_core
04:37:31 <jagmanetta> I think I'm missing something! :) Could anyone help me? Thanks a lot :)
04:37:56 <JohPie> I think you use the old namespaces
04:41:57 <jmverges> did you update the ft3 extensions from development version?
04:43:04 <jagmanetta> clear caches by filesystem, nothing changes
04:43:17 <JohPie> If I update to the develop versions, nothing works anymore
04:43:39 <jagmanetta> I confirm: I've updated the extension via the extensions manager and I'have my typo3 in development mode
04:45:09 <jagmanetta> The problem still exists with the Page/List module selected
04:45:52 <NamelessCoder> jagmanetta you probably have a {namespace v=Tx_Vhs_ViewHelpers} somewhere. That must be changed to {namespace v=FluidTYPO3\Vhs\ViewHelpers}
04:45:56 <JohPie> jmverges: after switch to flux develop, I get '#1257246929: "" is not a valid template resource URI' Page Modul
04:47:00 <jagmanetta> @NamelessCoder thanks, I'm gonna find and change it
05:04:03 <JohPie> I try to debug, but I don't have much time right now :(
05:04:44 <JohPie> Is there anything changed with Template Files and Path from master to develop?
05:05:17 <JohPie> or something that I "must have" in develop?
05:16:45 <jmverges> I really don't know JohPie, you could try to download all the ft3 extensions from github development branch and try to install uninstall them and clear caches
05:17:51 <jagmanetta> @NamelessCoder, something has changed now the error is #1289386765: Could not analyse class:FluidTYPO3\Vhs\ViewHelpers\Var\SetViewHelper maybe not loaded or no autoloader?
05:18:17 <jmverges> jagmanetta: try to install uninstall the extension
05:51:33 <jagmanetta> @jmverges sorry, but i see that the helper still exists https://github.com/FluidTYPO3/vhs/blob/development/Classes/ViewHelpers/Variable/SetViewHelper.php
05:52:10 <jagmanetta> many extensions in my installation use it, why should be no more available if is still in the vhs extension?
05:53:57 <jmverges> you are using var instead of variable jagmanetta
05:54:15 <jmverges> you only need to change all your .var. to .variable.
06:13:18 <featdd> how do I render a image in a fluid template fetched from an local filemount as a \TYPO3\CMS\Core\Resource\File
06:13:24 <featdd> can only get the dump file link but not display the real image :-/
06:30:45 <BennyS> Hi guys! Im trying to integrate a page template using fluidpages. How can render the party outside <body>? For head-meta-data i found viewhelpers. But how to render for example: <!DOCTYPE html>
14:33:02 <sitegeist_alex> Hi @NamelessCoder, could you have a look at my comment on https://github.com/FluidTYPO3/flux/commit/c4046ffb87ffd081b0abdaad9896a9653c37e5f5 please? Do you have any hint for me to bypass this error?
16:49:30 <xaver> sitegeist_alex: i can provide only a workaround
16:53:26 <pedda> anyone already dealed with #1257246929: "" is not a valid template resource URI. in latest ft3 extensions (development branch)
17:04:39 <pedda> NamelessCoder the latest version of EXT:builder generates provider extensions where typoscript configuration starts with plugin.tx_MyVendor.MyExtKey. is this the way to go for 7.x ?
17:08:32 <pedda> in fact i was trying latest master core in a working project, related to the core update i updated all ft3 extensions too. I'm facing a few issues now, which i tried to solve by generating a dummy extension, to see how a "modern" extbase extension should look like now
17:09:54 <pedda> i was setting up websites by the help of EXT:view by now, this seems obsolete since stdWrap was introduced to view.templateRootPath for example. am i correct ?
17:32:23 <pedda> i use a php based provider in an extension called profiles
17:33:41 <pedda> i have 2 fe plugins, so i do have 2 php classes in Classes/Provider/Configuration/CarouselPluginProvider and register those in my ext_tables by the help of 2 lines
17:34:01 <jmverges> however, if you are trying to overlay you need your extension https://gist.github.com/jmverges/86a8f49f6921f976d355
17:34:51 <pedda> i will need to deal with overlays afterwards, the EXT:profiles uses its "own" templates atm
17:40:12 <pedda> worked until i upgraded from 6.2 LTS to 7.x
17:40:38 <pedda> to be more precise: 7.5-dev and edgy ft3 tools
17:41:56 <pedda> i used the ts based "flux de plugin settings" approach for a while, but i moved back to php based as the ts based one failed several times after EXT:flux upgrade
17:42:24 <pedda> do you use flux for fe plugin settings in your custom extensions?