This site has been archived and you can no longer log in or post new messages. For up-to-date community resources please visit

eZ Community » Forums » Discussions » eZ Publish 5 Coding best Practices

Friday 19 September 2014 12:13:55 pm - 2 replies

» Read full blog post


A question often asked by partners / customers / developers is about "what are the best practices for developing eZ Publish 5 projects".

It is true that the community at large does not have the same amount of experience with the new version as it had with the legacy one. Any feedback is thus welcome, such as the excellent one from Donat.

Also, compared to eZ4, Symfony often offers looser guidelines and a more open structure, which might leave developers stranded and development team members in conflict with each other.

Having had the opportunity to participate in a couple of "biggish" projects based on eZ Publish 5, I have made some notes on development practices which helped the teams develop better code faster.

Read on, and please do comment on anything which you feel is missing / inappropriate. This is supposed to be a work-in-progress, not a cast-in-stone manual.

Friday 19 September 2014 2:03:09 pm


Never change the current repository user to admin unless there is a good reason to

Never ever do that, except maybe in console commands (but you should always prefer accept an argument giving the user to use).

Instead of manually logging in admin, use Repository->sudo() blunk.gif Emoticon.

Modified on Friday 19 September 2014 2:03:21 pm by Jérôme Vieilledent

Thursday 09 October 2014 10:16:30 am

hi. Regarding the Camel|Case, wondering if we should switch from eZ to Ez in ez5 kernel... 


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

36 542 Users on board!

Forums menu

Proudly Developed with from