Novactive eZ Static Templates bundle
This repository is what we call a "subtree split": a read-only copy of one directory of the main repository.
It is used by Composer to allow developers to depend on specific bundles., (*1)
If you want to report or contribute, you should instead open your issue on the main repository: https://github.com/Novactive/Nova-eZPlatform-Bundles, (*2)
Documentation is available in this repository via .md
files but also packaged here: https://novactive.github.io/Nova-eZPlatform-Bundles/master/StaticTemplatesBundle/README.md.html, (*3)
, (*4)
Novactive eZ Static Templates bundle is an eZ Platform bundle providing an ultra easy way to access twig templates from an url., (*5)
It uses the siteaccess and the design engine provided by eZ Platform., (*6)
Features
When you access a siteaccess in the siteaccess group static_group
, it will take the url and show the twig template having the corresponding path., (*7)
You can configure as many siteaccess as you want, and using the design engine you can configure a different theme for each siteaccess., (*8)
As we are using the siteaccess feature, u can also use the permissions to control the access., (*9)
Example
Considering a theme static_test
, a siteaccess static-test
is automatically generated. The siteaccess is then matched by URI, the url http://localhost/static-test/news/details
will show the template in themes\static_test\news\details.html.twig
, (*10)
That's it!, (*11)
Installation
Get the bundle
Add the lib to your composer.json, run composer require novactive/ezstatictemplatesbundle
to refresh dependencies., (*12)
Then inject the bundle in the bundles.php
of your application., (*13)
Novactive\Bundle\EzStaticTemplatesBundle\EzStaticTemplatesBundle::class => [ 'all'=> true ],
Configuration
None!, (*14)
The siteaccess configuration is autogenerated based on existing themes whose name start with "static_", (*15)