Book Image

eZ Publish 4: Enterprise Web Sites Step-by-Step

Book Image

eZ Publish 4: Enterprise Web Sites Step-by-Step

Overview of this book

eZ Publish provides developers with a structure to build highly impressive applications and then quickly deploy them into a live environment. eZ Publish is complex, with a steep learning curve, but with the right direction it offers great flexibility and power. What makes eZ Publish special is not the long list of features, but what's going on behind the scenes. Created specifically for newcomers to eZ Publish, and using an example Magazine web site, this book focuses on designing, building and deploying eZ Publish to create an enterprise site quickly and easily. This tutorial takes eZ Publish's steep learning curve head-on, and walks you through the process of designing and building content-rich web sites. It makes the unrivalled power and flexibility of eZ Publish accessible to all developers. The book is organized around technical topics, which are handled in depth, with a general progression that follows the learning experience of the reader, and features a single magazine web site project from installation to completion and deployment. This hands-on guide helps the reader to understand the Content Management System to create a web 2.0-ready web site by creating new extensions or overriding the existing ones. In turn, it helps you to become confident when working in the eZ Publish administration area and offers an environment in which you can practice while working through the chapters.
Table of Contents (20 chapters)
eZ Publish 4: Enterprise Web Sites Step-by-Step
Credits
About the Authors
About the Reviewer
Preface
Advance Debugging

Multilingual extensions


We saw how to create a new locale file and how to compile a translations file. Now we will see how to upgrade our extension to i18n.

The extension folder structure

To enable multilingual support in our extension, we have to create a new folder structure for the translation files. We have to open a shell, go to the extension folder, and then create a directory named translations.

# cd /var/www/packtmediaproject/extension/packtmedia
# mkdir translations
# mkdir translations/ita-IT
# mkdir translations/fra-FR
# mkdir translations/de-DE

For all of the folders, we have to create the translation.ts file named according to the string that we will use in the templates.

The extension siteaccess

As for the main siteaccess that we configured in Chapter 2, we have to notify the system to also enable the internationalization system for our extension. To do this, we need to open the site.ini.append.php file located in the extension settings/ directory.

# cd /var/www/packtmediaproject...