Hi Tino

That's weird because the console script is present on the repository. Where are you launching the command from? Is there any app/ folder?

Hi,

thanks for your response. Your are right. My app folder contains only /config and ezpublish_legacy/ sub folders. Mysterious.

Yesterday, I hadn't any errors while git clone... ..... anyhow... today, I reinstall all the stuff and now, all these files exists.

eZPublish5 works great now!

---

Another little questions:

I configure the config.yml and change the db connection - okay.

parameters:   

ezpublish.api.storage_engine.default: legacy   

ezpublish.api.storage_engine.legacy.dsn: mysql://root:supersecretpw@localhost/ez-legacy

 # Siteaccess matching, this is dummy configuration for tests   

ezpublish.siteaccess.default: ezdemo_site   
ezpublish.siteaccess.config:       
    Map\URI:           
        ezdemo_site: ezdemo_site           
        ezdemo_site_admin: ezdemo_site_admin       
    Map\Host:           
        ezpublish: ezdemo_site           
        ezpublish.admin: ezdemo_site_admin

How does it works with multisite installations? Can I override this config per site extension?

This is an interesting question. At the moment all configuration for db in ezpublish is done in ini files.

In the above example now it is stored in config.yml. 

...

We have an ezinstallation with > 50 sites with different DBs with many siteaccesses. How the config.yml should be for legacy support?

...

by the way i like the new web profiler toolbar from symfony

Quote from Felix Woldt :

This is an interesting question. At the moment all configuration for db in ezpublish is done in ini files.

In the above example now it is stored in config.yml. 

...

We have an ezinstallation with > 50 sites with different DBs with many siteaccesses. How the config.yml should be for legacy support?

...

by the way i like the new web profiler toolbar from symfony

HI.
Good question!
This is where one of the first steps in the install doc should be about: install symphony and get a feel for it.  There are various ways to accomplish this in symphony and even more options depending on which ORM is used.

I have not looked at eZ5 yet other than browsing the repo as I want things to settle for a week or so (mod times on files indicate huge development push right now).  However, in symphony terms, here are some ways to accomplish multiple websites.

• In Symphony, previous discussions would be 'Why would you want a single core for multiple websites'. I mention this because it is a a mindset of many Symphony developers.  But there is, of course a need for a single core in many scenerios and since it is part of eZP, it would make sense to ignore the Symphony threads that are against this.
• Share a core(sumphony), but have multiple web/app directories: This is a vague statement, but you can see plenty of examples of people sharing a core while having separate installs. Depending on the amount of 'sharing' needed, this is accomplished in simple ways all the way down to symlinking certain directories.
• A single app with multilpe databases (usin routing logic);  I know that if Doctrine is used, for instance, you can use multiple databases and swicth between them in your logic (so, route to the tight content and use right database.  An example is here: http://devdream.wordpress.com/2011/09/01/using-multiple-databases-in-symfony2/
• Symphony2 default is a very good routing system (search for examples of routing.yml)
• Each domain as a bundle, maybe?

I think it's at the point of the 'proof of concept' just ending and development really starting to kick off.  It's probably early days for there to be a 'difinitive way' to do 'A' or 'B' or 'C' in eZ/Symphony as things are still being worked out(plus, why start now - there are multiple ways of doing things in eZ Publish - all of which are equally under-documented leading to people just using their preferred choice
So, posing questions like the above now are critical for the core developers to align themselves with the priorities and needs of the users. Perhaps this way, standard practices for accomplishing tasks can be defined and adopted.

Quote from David Ennis :

So, posing questions like the above now are critical for the core developers to align themselves with the priorities and needs of the users. Perhaps this way, standard practices for accomplishing tasks can be defined and adopted.

You perfectly got it David . This is exactly the point giving feedback to us. Of course, we're still in a very early phase and, as you said, leaving the POC status to enter in hardcore development.

As of Siteaccess, we're currently working on it but I can't give you answers on the how for configuration yet. This is indeed still under discussion internally.

However, here are some ideas we already agreed:

• We will stick on the "single core for multiple sites" approach. The main reason is BC of course, but not only. There are many cases where this is very relevant like mini-websites, multi-lang... Remember that (at the moment at least) a SiteAccess is a bunch of settings!
  But of course it will be possible to set up a new core to match a completely different website (with a different front controller and a different app/ directory). However we won't focus on this use case right now.
• We want to provide some kind of "SiteAccess groups" in order to fix this annoying limitation when you want to share some settings between siteaccesses without making overrides. Currently, the only way to fix this is to symlink your configuration files, which is not very clean.
• Configuration will be semantically exposed and validated, as Symfony gives the opportunity to do so. So settings like ezpublish.api.storage_engine.legacy.dsn are temporary and will exposed in a user-friendly way.

Quote from Felix Woldt :

by the way i like the new web profiler toolbar from symfony

Glad you like it . It's indeed very handy...

Thank's David and

Thank's Jérôme for your quick reply .

Quote from Jérôme Vieilledent :

 

Quote from David Ennis :

So, posing questions like the above now are critical for the core developers to align themselves with the priorities and needs of the users. Perhaps this way, standard practices for accomplishing tasks can be defined and adopted.

You perfectly got it David . This is exactly the point giving feedback to us. Of course, we're still in a very early phase and, as you said, leaving the POC status to enter in hardcore development.

As of Siteaccess, we're currently working on it but I can't give you answers on the how for configuration yet. This is indeed still under discussion internally.

However, here are some ideas we already agreed:

• We will stick on the "single core for multiple sites" approach. The main reason is BC of course, but not only. There are many cases where this is very relevant like mini-websites, multi-lang... Remember that (at the moment at least) a SiteAccess is a bunch of settings!
  But of course it will be possible to set up a new core to match a completely different website (with a different front controller and a different app/ directory). However we won't focus on this use case right now.
• We want to provide some kind of "SiteAccess groups" in order to fix this annoying limitation when you want to share some settings between siteaccesses without making overrides. Currently, the only way to fix this is to symlink your configuration files, which is not very clean.
• Configuration will be semantically exposed and validated, as Symfony gives the opportunity to do so. So settings like ezpublish.api.storage_engine.legacy.dsn are temporary and will exposed in a user-friendly way.

Quote from Felix Woldt :

by the way i like the new web profiler toolbar from symfony

Glad you like it . It's indeed very handy...

Hi.
Good Reply - thanks.  When discussing siteaccessGroups internally, consider bundles as a way to (A) replace siteaccesses and (B) Achieve the siteaccess Grouping you mention.  I have not delved that deep into bundles, but I understand that one bundle can inherit specific parts of another bundle, so what you really have is controlled inheritance of everything from settings to controllers, etc.
Example: http://symfony.com/doc/current/cookbook/bundles/inheritance.html

Quote from David Ennis :

When discussing siteaccessGroups internally, consider bundles as a way to (A) replace siteaccesses and (B) Achieve the siteaccess Grouping you mention.  I have not delved that deep into bundles, but I understand that one bundle can inherit specific parts of another bundle, so what you really have is controlled inheritance of everything from settings to controllers, etc.

Yes, bundle inheritance is nice but it's a bit limitated for siteaccesses IMHO. What we actually need is runtime configuration. I saw OpenSkyRuntimeConfigBundle, but didn't dug into yet.

Anyway, we might continue this siteaccess discussion in another topic

Hi all

I have another problem while trying to install eZ v5. I follow installation instructions from github page (https://github.com/ezsystems/ezpublish5/blob/master/INSTALL.md)

I set this symbolic link to my ezpublish 4 version (i'm not sure if it should be like that, there's no clear info about that):

 ln -s /home/developer/Projects/eZ/ /home/developer/Projects/ez5/app/ezpublish_legacy

I had to comment out line

define( 'EZCBASE_ENABLED', $baseEnabled );

from ezpublish_legacy/autoload.php because there were error that constant is already defined.

After that all went fine, and now when I hit index.php in browser I get fatal error:

Fatal error: Class 'ezpKernel' not found in /home/developer/Projects/ez5/vendor/ezsystems/ezpublish/eZ/Publish/Legacy/Kernel.php on line 17

I tried to find this ezpKernel class but I can't find it anywhere.

Any clues what is wrong?

Sounds like you don't update your ez 4 version to ez 4 legacy.

INSTALL PART 1 => Step 2

eZ Publish 4 (aka legacy) part

1. Start from an eZ Publish CP 2012.5 installation

2. Upgrade it to the enhanced version (get the source from eZ Publish legacy's ezpublish5-integration branch, or just download the ZIP file). No upgrade script is needed, only replace all source files (except your own extensions, templates and settings).

   Very important: Be sure you have upgraded your index.php as well

Modified on Thursday 05 July 2012 3:37:59 pm by Tino Maaß

Hi all, forgive me if this is an incorrect place to ask this but I've been trying to install a clean version of ezpublish5 and cannot get this to work. I used the Composer method from the install instructions (https://github.com/ezsystems/ezpublish5/blob/master/INSTALL.md) and all files installed correctly.

I ran the install script http://localhost/ezpublish/index.php/ezsetup but got a 503 error. After debugging I found it was a Symfony config error: 

Invalid configuration for path for ezpublish_legacy.root_dir. Provided eZ Publish Legacy root dir does not exist!

So I commented this out as I don;t have a legacy root.
ez_publish_legacy:   
enabled: false
#     root_dir: %kernel.root_dir%/../ezpublish_legacy 

After running again I got this error:

The parent definition "ezpublish_legacy.security.firewall_listener" defined for definition "ezpublish_legacy.security.firewall_listener.ezpublish_front" does not exist.

Has anyone managed to install a clean install? or does anyone have any ideas on how to fix this error?

Thanks in advance

Hi Craig

eZ Publish 5 won't work at all if you don't have eZ Publish legacy, so please don't disable it .

First of all, when developing use index_dev.php as a front controller instead of index.php so that you have the debug mode and stack traces for all exceptions.

Then your error message clearly shows that eZ Publish legacy is not installed. Please refer to step 2 in installation process.