You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 14, 2026. It is now read-only.
Good afternoon,
Just started with LiipThemeBundle - so apologies if I'm trying to run before i can walk.
I have set up 2 themes (say, Brand1 and Brand2) and set fallback to Resources/views/
If I have a template which loaded from the fallback - this works. If I then place a template in (say) Resources/themes/Brand1/ and reload the page, it still pulls the template from the fallback.
Once I clear the cache though, the newly added override template is (correctly) loaded.
I think the cause is down in the Liip\ThemeBundle\Locator\TemplateLocator::locate method - as I understand things, once a template is added to the cache, the locator method then relies on this rather than relocating the template.
Would this be better to use the %%kernel_debug%% value, and always relocate the template if the app is in an environment with debug=true?
Good afternoon,
Just started with LiipThemeBundle - so apologies if I'm trying to run before i can walk.
I have set up 2 themes (say, Brand1 and Brand2) and set fallback to Resources/views/
If I have a template which loaded from the fallback - this works. If I then place a template in (say) Resources/themes/Brand1/ and reload the page, it still pulls the template from the fallback.
Once I clear the cache though, the newly added override template is (correctly) loaded.
I think the cause is down in the Liip\ThemeBundle\Locator\TemplateLocator::locate method - as I understand things, once a template is added to the cache, the locator method then relies on this rather than relocating the template.
Would this be better to use the %%kernel_debug%% value, and always relocate the template if the app is in an environment with debug=true?
Regards,
Ryan