In-depth insights on content, code, and creativity
2009 was a busy year at Mugo, and we were actually a bit surprised to find that we had worked on over 40 different websites and web applications. eZ Publish has enabled us to provide a wide variety of powerful and flexible web solutions. Before 2010 speeds by, we'd like to take a moment to look back at a sampling of the types of solutions we've built (and continue to build), as well as a few other successes from the past year.
eZ Publish is well-known as a Content Management System with built-in multi-language features. To present different translations of pages, eZ Publish uses 3 major components: content translation, content class translation, and template / script translation. In this post, we will explain these 3 components and introduce a script to help translate strings in templates.
It is a reasonably common use case to fetch a list of content objects based on a common attribute implemented across multiple content classes. For example, to fetch all articles, blog posts and comments published by a given author. Certainly one could do multiple fetches and then massage the result sets together, but that's a lot of work. In this post I'll create a custom template operator (which is not the same as a custom fetch function, although the latter might be a better extension if one were a fan of doing things 'semantically') The operator will do the fetch with one SQL query. And I hope to shine some light on the eZ Publish db schema around objects, along the way.
Many products -- PDF books, songs, and online games, among others, are well suited for a pay-per-download workflow. In such a case, customers buy products online and receive immediate access, without requiring any action from the seller. Mugo Web has written an article outlining how eZ Publish provides a framework to quickly set up pay-per-download products.
The Ibexa DXP excels at multi-site installations. For example, on the same installation, you can create multiple sites that share the same database, or that share the same code but use independent databases. Different sites can share the same base design and templates, but make use of site-specific overrides where relevant. For sites with user logins, you might need Single Sign-On (SSO) behavior, so that whenever a user logs in to one site, they are automatically logged in to all sites without having to re-enter their credentials. In this post, we'll review how to implement SSO logins on an Ibexa DXP website, specifically one where some of the sites are still using eZ Publish legacy siteaccesses.