In-depth insights on content, code, and creativity
Many hosting companies will take care of file system and database backups for you. We have a few clients where we have file system backups configured, but database backups have to be handled manually, since the database is "live data". Often we can just configure a cronjob that runs mysqldump so that a database snapshot is stored to a file and thus regularly backed up when the file system backup is run. However, sometimes you have a perfect storm where mysqldump is too heavy for the server (causing severe slowdowns or even crashing some services), even if run in the least intensive way (such as with the --quick flag) and at a low traffic time: partially due to lack of system resources and a large database.
If you're relatively new to eZ Publish, you might know about siteaccesses, design, extensions, and overrides. You can build a basic extension, edit a template file, and write a simple full view override rule. However, you might have trouble putting this all together. You might struggle with whether to put your template in the "standard" design or a custom site design folder. You might be confused as to whether to put your template in the "override/templates" folder or the "templates" folder, and/or the overall template path in the first place. This article will take a step back for a high-level look at how eZ Publish loads extensions, particularly design extensions, as well as how to find out which templates are being used and how to properly override them.
Mugo Web is not a large company that offers perks such as an indoor gym, a company hockey pool, a big travel budget, or a fridge stocked with fresh fruit and snacks every day (although we do our best on an individual basis to share good food with each other!). That said, we love working at Mugo, for reasons that might not be so obviously communicable on our website. Here are our raw responses to an internal e-mail thread that asked "What are 3 things you like about working at Mugo?"
Mugo Web is jointly hosting the first eZ Publish event of the year in North America with Granite Horizon. We are currently accepting talk proposals and training topic requests.
The open source content management system eZ Publish moved its code repository to GitHub near the end of 2010. Although eZ Publish's code base has been open source since its first version in 1999, before the move to GitHub, it was not an easy process for the community to contribute to the code. Mugo Web has enjoyed contributing to the eZ Publish code by making pull requests and hopes to make more in the future!
eZ Publish comes with a useful set of image settings, and has a powerful framework within which you can define custom filters to be executed by the image handler. In this article, we'll show you how to make use of a custom ImageMagick filter to achieve exact image sizes.
When you are setting up a mobile website separate from the main website, one of the elements that tends to be an after-thought is main-to-mobile site redirection. This article goes through some of the considerations regarding creating a mobile setting, and main-to-mobile site redirection specifically. It explains how to use Apache Mobile Filter as one option to facilitate mobile device detection and redirection.
Mugo has an internal wiki to share and store various information for all team members. Previously we used mostly text files saved in Dropbox, which actually worked quite well. However, we are now using a more powerful solution that combines eZ Publish, a custom static cache handler, and Dropbox.
eZ Publish comes standard with the Star Rating extension, which adds the ability for users to rate content on your website. It works well out of the box. By default, the interface to rate an article is combined with the aggregate rating on an article. Here's a quick example on how to tweak that functionality so that "your rating" is separate from the aggregate rating.
This blog post is about how eZ Publish serves content images -- also called image aliases -- in a DFS cluster setup. The eZ DFS setup is the recommended and most common solution for high traffic eZ Publish sites that are run off multiple servers. However, it still has some room for improvement when it comes to serving images. In this post, we describe how eZ Publish currently serves image aliases, along with its downsides and some alternative approaches. At the end, we describe a possible implementation with some example performance gains.