tag: ezpublish

With coming of the eZ Publish CMS version 5 and introduction of the Public API a new naming convention was established, the version 4 technology was called legacy stack and the new technology, with the Public API as the cornerstone, was called the new stack. Recently by using this new stuff more and more I realised that this naming is a bit misleading.

One month ago we announced a double event: the 3rd eZ Publish Summer Camp and the 1st PHP Summer Camp. Today we released some more information on each web site and are calling PHP, Symfony and eZ Publish gurus to send us proposals for workshops. There is an opportunity for interested companies and organisations to sponsor the events as well.

This post will be all about my experiences on the Faculty of Electrical Engineering in Osijek, how the whole idea of a lecture and workshop came to me, and how it all realised in the end.

Solr is an excellent search engine. We are using it for years through eZ Find (its an eZ Publish extension for searching) and its really powerful and flexible solution. Our use cases are not that complex so we never actually hit into a wall with Solr. But there is one problem when building search solutions in general which we encountered few times and for which Solr has no feature. It happens when the language of the indexed content is some language that we as integrators don't understand.  

Responsive web design (RWD) redefined the way we design web sites. The disruption went deep and changed both the processes and deliverables we hold dear for so long, and today in Netgen RWD is the default route we take with every new project. But, bundled with its core unifying principle of every browser getting the same HTML, some tough problems arose. One of the most discussed is the responsive images problem of providing alternate images based on device capabilities and screen sizes.

There is a lot to learn about new eZ Publish 5 stack. The reason is simple: new architecture and new frameworks are being used. Lot of legacy knowledge is going to be deprecated, many tips & tricks you know now are no longer usable. The good thing is that the new platform is much more powerful simply because it uses Symfony framework. This blog post gives a perfect example on how to deal with problems when trying to use the new stack in your project.