eZ Community » Forums » eZ Publish 5 Platform » ezpulish.yml
expandshrink

ezpulish.yml

ezpulish.yml

Tuesday 30 July 2013 1:20:04 pm - 5 replies

Hi, is there some documentation explaining what configuration options are available in ezpublish.yml (and also config.yml and all the other *.yml in the config directory) and what effect they have ?

 

Thanks

Tuesday 30 July 2013 1:31:59 pm

Hi Francesco

You can use config:dump-reference command for this:

php ezpublish/console config:dump-reference ezpublish

This will dump all available config for ezpublish namespace. You can replace ezpublish by any other bundle (e.g. framework will dump available settings for the Symfony FrameworkBundle)

Tuesday 30 July 2013 4:15:56 pm

Thanks, that helps a little but I was hoping for something a bit more in depth.

For example: what is the relationship between the siteaccesses defined in  ezpulish.yml and those defined in ezpublish_legacy/settings/siteaccess ?

Friday 02 August 2013 8:10:24 pm

Quote from Francesco Nardone :

Thanks, that helps a little but I was hoping for something a bit more in depth.

For example: what is the relationship between the siteaccesses defined in  ezpulish.yml and those defined in ezpublish_legacy/settings/siteaccess ?

 

Hello Francesco, Im in the same place as you. I have been working in my first implementation of Ez really hard, but have not been able to configure the eZ Publish Community Project 2013.06 as I should.
I explain my particular case:

I started my implementation using the EzDemo+EzFlow extensions, I made my customized templates on EzFlow, I have changed a lot of the GUI with the bootstrap, I have activated all the blocks included in EzFlow for been used in EzDemo, I have created a new main menu based in a dropdown mega Menu using basic concepts of node, and I have changed and redesigned the header and footer.

Now, I am facing a problem:  When I enter in the index of the site, according with some books, I should be redirected to the default site: www.example.com/index.php/content/view/full/2  but for some reason is charging by default www.example.com/index.php/, so the standard design is overwriting  my design...

I have been tracing the logs searching information about what can I do. In the Ez kernel 5 logs I found this:

 

  [2013-08-02 12:46:02] app.NOTICE: Siteaccess not matched against configuration, returning default siteaccess. [] [][2013-08-02 12:46:02] app.INFO: Router eZ\Bundle\EzPublishCoreBundle\Routing\DefaultRouter was not able to match, message "" [] [][2013-08-02 12:46:02] app.INFO: UrlAlias matched location #2. Forwarding to ViewController [] [][2013-08-02 12:46:02] request.INFO: Matched route "ez_urlalias" (parameters: "_route": "ez_urlalias", "_controller": "ezpublish.controller.content.view:viewLocation", "locationId": "2", "viewType": "full", "layout": "true") [] [][2013-08-02 12:46:02] security.DEBUG: Read SecurityContext from the session [][][2013-08-02 12:46:02] security.DEBUG: Reloading user from user provider. [] [][2013-08-02 12:46:02] security.DEBUG: Username "anonymous" was reloaded from user provider. [] [][2013-08-02 12:46:02] app.DEBUG: Checking secure context token: PreAuthenticatedToken(user="anonymous", authenticated=false, roles="") [][][2013-08-02 12:46:02] app.DEBUG: Trying to pre-authenticate user "10" [] [][2013-08-02 12:46:02] app.INFO: Authentication success: PreAuthenticatedToken(user="anonymous", authenticated=true, roles="ROLE_USER") [] [][2013-08-02 12:46:02] app.NOTICE: 'location' is not scalar, cannot pass it to legacy content module. Skipping. ["eZ\\Publish\\Core\\MVC\\Legacy\\View\\Provider\\Location::eZ\\Publish\\Core\\MVC\\Legacy\\View\\Provider\\{closure}"] [][2013-08-02 12:46:02] app.NOTICE: 'content' is not scalar, cannot pass it to legacy content module. Skipping. ["eZ\\Publish\\Core\\MVC\\Legacy\\View\\Provider\\Location::eZ\\Publish\\Core\\MVC\\Legacy\\View\\Provider\\{closure}"] [][2013-08-02 12:46:05] app.INFO: Router eZ\Bundle\EzPublishCoreBundle\Routing\DefaultRouter was unable to generate route. Reason: 'Route 'ez_legacy' not found': Unable to generate a URL for the named route "ez_legacy" as such route does not exist. [] [][2013-08-02 12:46:05] app.INFO: Router eZ\Bundle\EzPublishCoreBundle\Routing\DefaultRouter was unable to generate route. Reason: 'Route 'ez_legacy' not found': Unable to generate a URL for the named route "ez_legacy" as such route does not exist. [] [][2013-08-02 12:46:05] app.INFO: Router eZ\Bundle\EzPublishCoreBundle\Routing\DefaultRouter was unable to generate route. Reason: 'Route 'ez_legacy' not found': Unable to generate a URL for the named route "ez_legacy" as such route does not exist. [] [][2013-08-02 12:46:05] app.INFO: Router eZ\Bundle\EzPublishCoreBundle\Routing\DefaultRouter was unable to generate route. Reason: 'Route 'ez_legacy' not found': Unable to generate a URL for the named route "ez_legacy" as such route does not exist. [] [][2013-08-02 12:46:05] app.INFO: Router eZ\Bundle\EzPublishCoreBundle\Routing\DefaultRouter was unable to generate route. Reason: 'Route 'ez_legacy' not found': Unable to generate a URL for the named route "ez_legacy" as such route does not exist. [] [][2013-08-02 12:46:05] security.DEBUG: Write SecurityContext in the session [] [][2013-08-02 12:46:05] security.DEBUG: Read SecurityContext from the session [] [][2013-08-02 12:46:05] security.DEBUG: Reloading user from user provider. [] [][2013-08-02 12:46:05] security.DEBUG: Username "anonymous" was reloaded from user provider. [] [][2013-08-02 12:46:05] app.DEBUG: Checking secure context token: PreAuthenticatedToken(user="anonymous", authenticated=false, roles="ROLE_USER") [][][2013-08-02 12:46:05] app.DEBUG: Trying to pre-authenticate user "10" [] [][2013-08-02 12:46:05] app.INFO: Authentication success: PreAuthenticatedToken(user="anonymous", authenticated=true, roles="ROLE_USER") [] [][2013-08-02 12:46:05] security.DEBUG: Write SecurityContext in the session [] [][2013-08-02 12:46:05] security.DEBUG: Write SecurityContext in the session [] [][2013-08-02 12:46:05] security.DEBUG: Read SecurityContext from the session [] [][2013-08-02 12:46:05] security.DEBUG: Reloading user from user provider. [] [][2013-08-02 12:46:05] security.DEBUG: Username "anonymous" was reloaded from user provider. [] [][2013-08-02 12:46:05] app.DEBUG: Checking secure context token: PreAuthenticatedToken(user="anonymous", authenticated=false, roles="ROLE_USER") [] [][2013-08-02 12:46:05] app.DEBUG: Trying to pre-authenticate user "10" [] [][2013-08-02 12:46:05] app.INFO: Authentication success: PreAuthenticatedToken(user="anonymous", authenticated=true, roles="ROLE_USER") [] [][2013-08-02 12:46:05] request.CRITICAL: Uncaught PHP Exception eZ\Publish\Core\Base\Exceptions\NotFoundException: "Could not find 'location' with identifier '60'" at /var/www/html/Ez6-2013/vendor/ezsystems/ezpublish-kernel/eZ/Publish/Core/Persistence/Legacy/Content/Location/Gateway/EzcDatabase.php line 78 [] [][2013-08-02 12:46:05] security.DEBUG: Write SecurityContext in the session [] [][2013-08-02 12:46:05] security.DEBUG: Write SecurityContext in the session [] [][2013-08-02 12:46:05] security.DEBUG: Write SecurityContext in the session [] []

Somebody know what should I do in order to use only my design without fall backs to the standard design? 
As I explained before, Im a new comer and for sure I have done a lot of mistakes. 
Many thanks!

Friday 02 August 2013 8:34:13 pm

Quote from Francesco Nardone :

For example: what is the relationship between the siteaccesses defined in  ezpulish.yml and those defined in ezpublish_legacy/settings/siteaccess ?

In a 5.x setup the yml settings will be injected into 4.x and overwrite the corresponding settings.
So those settings specified in yml files only needs to be confoigured there, assuming you run all request, including legacy scripts and cronjobs using: 

 php ezpublish/consoleezpublish:legacy:script

@Freddy: In your case you might benefit from just using legacy(point apache to legacy folder and look to 4.7 documentation for how it should be like), or enabling legacy_mode to avoid having to deal with both kernels for this specific site as it sounds like 5.x and DemoBundle takes over some of your url's.

Saturday 10 August 2013 12:08:12 am

Hi 

@Francesco 

For example: what is the relationship between the siteaccesses defined in  ezpulish.yml and those defined in ezpublish_legacy/settings/siteaccess ?

-> you can genarate your siteaccess ini settings in ezpublish.yml. I like it : (Backup your ezpublish.yml first and see what happen):

php ezpublish/console ezpublish:configure <YOURSITEACCESS1> <YOURSITEACEES2> <YOUR-ADMIN-SITEACCESS> ...

Best Practice: try to specify your own configuration in ezpublish_prod.yml or ezpublish_dev.yml (depend on environement). and keep ezpublish.yml original. also applies for config.yml and parameters.yml

You can also define your configuration in your bundle and import them in your configs files.

 

DO NOT FORGET: legacy_mode:false will take cae about your yml configuration. If you set it to true, then you redirect your request to the ezpublish_legacy and your siteaccess ini are adressed e.g backend (also using legacy_mode:true ). 

  

expandshrink

You must be logged in to post messages in this topic!

36 542 Users on board!

Forums menu

Proudly Developed with from