eZ CMS is based on the Symfony2 framework and follows its organization o= f the app. Like in Symfony, where "everything is= a bundle", your eZ application is going to be a collection of bundles.=
A bundle in Symfony (and eZ) is a separate part of your application that= implements a feature. You can create bundles yourself or make use of avail= able open-source bundles. You can also reuse the bundles you create in othe= r projects or share them with the community.
Many eZ CMS functionalities are provided through separate bundles includ= ed in the installation.
By default, a clean eZ Platform installation contains an AppBundle where= you can place your code.
To learn more about organizing your eZ project, see Best Practices.
You can generate a new bundle using a generate:bundle comma=
nd. See Symfony documentation on generating bundles.
In addition to Symfony Bundles, eZ provides a set of bundl= es out of the box and some optional ones.
To remove a bundle (either one you created yourself, or an out-of-the-bo= x one that you do not need) see the How to Rem= ove a Bundle instruction in Symfony doc.
To get an overview of EzPublishCoreBundle's configuration, run the follo= wing command-line script:
php app/console config:dump-reference ezpublish=20
Default page is the default page to show or redirect to.
If set, it will be used for default redirection after user login, overri=
ding Symfony's default_target_path, giving the opportunit=
y to configure it by siteaccess.
ezpublish:
system:
ezdemo_site:
default_page: "/Getting-Started"
ezdemo_site_admin:
# For admin, redirect to dashboard after login.
default_page: "/content/dashboard"=20
This setting does not change anything to Symfony behavior regarding redirection after login. If set, it will only substi=
tute the value set for default_target_path. It is therefo=
re still possible to specify a custom target path using a dedicated form pa=
rameter.
Order of precedence is not modified.