eZ publish 3.6.6 is the latest update of the 3.6 branch of the eZ publish content management system. This update beside normal bugfixes contains a fix for the security problem related to the 'notification rules' (for more details see http://ez.no/bugs/view/7929).

eZ publish 3.5.9 is the latest update of the 3.5 branch of the eZ publish content management system. This update beside normal bugfixes contains a fix for the security problem related to the 'notification rules' (for more details see http://ez.no/bugs/view/7929).

In this post on Bitacle.org, they look at a 5 minute approach to finding some of the more common issues with PHP web applications.

Detecting and correcting problems with applications at early stages is an important role of the server manager. Unfortunately, not all errors are detected at the testing stages. Even more unfortunate is the fact that most errors go undetected because they are usually triggered when a certain set of criteria is met.

Since all you have is 5 minutes (which is one of the tenets of this Server management series, and quite possibly the only simple truth in your case), in this installment, we'll unlock the secret of server log foraging.

They mainly make use of grep, a very handly unix command-line tool, to parse through the server logs for answers. Combine that with upping the error reporting level inside of PHP itself, and you should be able to track down most of the problems you'd have. They also include a sample situation or two to watch out for specifically.

Kore Nordmann has written up some graphics manipulation functionality in PHP that can draw two different types of images automatically - those based on the Lindenmayer system and ones using bezier curves and BSplines. He describes them in this new blog post.

The last days I was busy learning for a lecture for computer science which covers a lot of algorithms in graphics manipulation. For personal education I tried to implement some of them in the language I know best ... PHP.

This implements the Lindenmayer system in PHP. This is a system to draw images based on simple grammars. Most used for fractals or to simulate natural growth of plants.

Another thing I needed to understand - and imho the easiest way is just to implement it - are bezier curves and BSplines. This class offers a simple way to draw lines, bezier curves or BSplines from an array with points.

You can see examples (and get the code) for these libraries from:

• Image_Turtle
• Image_Curve

PHPit.net has posted another new tutorial, this time they look at the command-line, providing the basics to those that have only used PHP in the web-based world.

PHP is traditionally only used on the internet to power our websites, but it's also capable of doing more. Since version 4.3 PHP ships with a special version which can be used to execute scripts on the command line, and do certain system tasks. If you're a Linux user, you probably know what the command line is, but if you're a Windows user you might not.

They show the code/commands in the examples they give in the context of it running on a Windows machine, but it's not a far leap to work with it on a unix-based system as well. They start with the basics - how to get to it, how to use it - before moving on to other features, like taking in arguments. They wrap it up with a sample application, a calculator, that can do the four basic operations on the two numbers entered.

Sandro Groganz talks in this post on his blog about templating and why it really matters all that much (and a mention of the new template system for eZ publish).

Those with some years of experience in the software business know: the implementation or decision upon a template engine is always good for flame wars.

Why? Templates are such a basic technology of a CMS, a must-have and not really something sexy. Those who hoped to make templates sexy, invented XSLT.

So why? Because it is a basic technology!

He lists a few of the reasons there is such a "flame war" going on about templates - the love/hate relationship of developers that have had to work with templating systems already in place, the difference in thinking between developers and designers about what the template should be. He gives the eZ publish template system as an example of this dicotimy, noting that, when it all really comes down to it, the facts are what should speak, not opinions/emotions.

As I already announced before, I will be giving a talk about eZ components at the PHP Usergroup FFM meeting upcoming Thursday. I will first present some background information on our architecture, the goals, the design and the possibilities with eZ components. After that, I plan to show a little example application which is build upon the library to let people see how it works. Finally I will be available for questions, feedback and possibly to show examples for specific components.

Looking forward to being in Frankfurt! :)

As I already announced before, I will be giving a talk about eZ components at the PHP Usergroup FFM meeting upcoming Thursday. I will first present some background information on our architecture, the goals, the design and the possibilities with eZ components. After that, I plan to show a little example application which is build upon the library to let people see how it works. Finally I will be available for questions, feedback and possibly to show examples for specific components.

Looking forward to being in Frankfurt! :)

I just read about OLAP4ALL's Materialized Views for MySQL software that "offers the functionality of Materialized Views in MySQL that are not natively supported in the MySQL database.".

What nags me about this is the fact that it is "implemented as a separate Java program running on the server where MySQL is installed".

The server-side of this should be doable using Stored Procedures and/or Triggers. For the client-side a bit of convenience functionality for query rewriting would be needed.

Sounds like an interesting project that I would like to pursue when I find the time.

Update: Marcel Oelke has ported this Materialized Views for PostgreSQL implementation to MySQL (see here and here).

... everyone, it seems!

Those with some years of experience in the software business know: the implementation or decision upon a template engine is always good for flame wars.

Why? Templates are such a basic technology of a CMS, a must-have and not really something sexy. Those who hoped to make templates sexy, invented XSLT.

So why? Because it is a basic technology!

These are the flame war factors:

You can't get Tempates out of Your Way

Every developer or Web designer building a Web site on top of a CMS, has to cope with the integrated template system, sooner or later. You will have a love-and-hate-relationship, because on the one side they help you, on the other side, every implementation has its pros and cons.

Love-and-hate-relationships are not really something that makes the involved parties calm and relaxed.

Who Takes Over the Bridge?

Templates are supposed to build a bridge between the programmers, who care about the business logic of a solution, and the designers who care about the user experience aka GUI. Thus, there are two groups with diverging interests affected by templates: programmers and Web designers. Every experienced how different their thinking can be? OK, then you clearly see the potential for conflict.

Love, Peace - and Common Sense

The discussion about the new template language for eZ publish, implemented as a library in the realm of the eZ components, has of course been long, and is still ongoing - but there's light.

It was interesting to observe, how the eZ components team will fight the fight and I must say, they did a good job.

So, what was it that created love and peace in eZ templates land? It was pragmatism: whenever a discussion becomes lengthy and and unfocused, bring it down to the facts, for example with a summary of past input and suggestions for solutions.

Doesn't sound sexy? No, it doesn't. Tempates are not sexy, they are basic technology, so let's be pragmatic and treat it like that, so let's cool down discussions and go back to work.

Sounds simple? It does, but is hard work, because you need to focus on the result!

You love such discussions? Jump in, you got time until Monday, 12:00.

PS: Did you find any irony in this text? Let me know :)