[SUPPORT] Context awareness enabled? about flux HOT 10 CLOSED

Hi Fabien,

How are you registering the template paths? If you use TS I assume you use the extension key as index where the templates are added (fx plugin.tx_fed.page.speciality or plugin.tx_fluidpages.collections.speciality). Perhaps some detection is failing to read the extension key from your setup, for whatever reason - I just need to pinpoint which detection it is :)

from flux.

here, still plugin.tx_fed.page.speciality -> changing that to plugin.tx_fluidpages.collections.speciality. Currently reading the error message Fluid Pages Error #1364685651 ... Unable to read a working path set from the Provider. The extension that caused this error was "Speciality"...

Nice output BTW.

from flux.

Don't you have a Bootstrap Instance at hand? Can you try putting this content into EXT:speciality/Configuration/TypoScript/Plugin/tx_flux.ts and reload the FE? I do get an Exception.

plugin.tx_fluidpages {
    page.speciality {
        templateRootPath = EXT:speciality/Resources/Private/Templates/
        partialRootPath = EXT:speciality/Resources/Private/Partials/
        layoutRootPath = EXT:speciality/Resources/Private/Layouts/
    }
}

#plugin.tx_flux.view.widget.Tx_Fluid_ViewHelpers_Widget_PaginateViewHelper.templateRootPath < plugin.tx_fluidpages.page.fluidpages.templateRootPath
#plugin.tx_news.view.widget.Tx_Fluid_ViewHelpers_Widget_PaginateViewHelper.templateRootPath < plugin.tx_fluidpages.page.fluidpages.templateRootPath

from flux.

Not template to select in Page property... investigating...

from flux.

Ah, yes collections !!

from flux.

Alright, I changed this file taking into account latest development. Display is fine.

Q1: Do I still need line 13?
Q:2 If I put in EXT:speciality/Resources/Private/Partials/Header.html following line {f:uri.resource(path:'Images/logo.png')} I still get it resolved to "fluidpages". Still missing something?

from flux.

I can confirm this also for <v:l>some.label</v:l> which only works when I provide the extensionName argument.

from flux.

Q1: Do I still need line 13?

No - assuming instead, you define that Widget template override in your own extension's view configuration.

I still get it resolved to "fluidpages". Still missing something?

Investigating that now.

from flux.

Hi Fabien,

I'll close this one - I'm assuming your problem was also fixed by the PR merged yesterday, but if that's not the case of course we should simply re-open this one (and do some further investigation).

Cheers,
Claus

from flux.

I just have tested and it works as expected :)

from flux.