Stuff and Content

For those who haven't heard of "Micro-blogging" wikipedia defines it as: Micro-blogging is a form of blogging that allows users to write brief text updates (usually less than 200 characters ) and publish them, either to be viewed by anyone or by a restricted group which can be chosen by the user. These messages can be submitted by a variety of means, including text messaging , instant messaging , email , MP3 or the web . Twitter is currently the most popular micro-blogging service but can have reliability issues (these have been addressed recently). I've been using it for a couple of months now . It can be a bit of a time suck especially if you follow frequent tweaters . I've found it a good way to keep track of what friends, the web industry & eZ people are up to, pose questions and actually get answers. One of the things that has always frustrated my about not attending the eZ conference in the past is that it takes about a week for news and coverag

In case you haven't seen the comments generated out of my last couple of posts, this is intended to be a summary. Thanks to all the fine eZ crew that jumped on and clarified things. It appears that jagels missed the middle '0' in 4.0.1 in his initial comment , making it seem (to me at least) like eZ were recommending that 4.0 should not be used and to hold off until 4.1. The advice was actually to wait for 4.0.1. Version 4.1 will come with the new TinyMCE based OE instead of (as well as?) the existing OE. The new TinyMCE OE can can also be used in eZ 4.0.x sites (Will the old OE work in 4.1 ?) eZ 4.1 will also include the following enhancements: http://issues.ez.no/12423 : add seconds input to date time and time datatypes http://issues.ez.no/12539 : share compiled templates between site accesses http://issues.ez.no/13009 : custom validation methos in edit handlers ( based on ideas in http://projects.ez.no/objectvalidation ) The microkernel changes will not be in

After my comment about following subversion commit comments to get an idea of what is happening with eZ Publish in my previous post , I realised it wasn't such a bad idea and added the RSS feed to my reader. This morning I'm happy to report that the release trees for 4.0.1 & 3.10.1 & 3.9.5 have been created. Nothing in the svn commits comments regarding 4.1. However this comment on my previous post has disturbed me: I have been to a couple of seminars where we were recommended to wait for 4.1 before we upgrade to eZ4 (by eZ employees). Anyone have details of why this is the case? With the launch of a 4.0 eZ site in the coming weeks I find this quite worrying.

No no he's not dead, he's, he's restin'! Remarkable bird, the Norwegian Blue, idn'it, ay? Beautiful plumage! from Monty Pythons "Dead Parrot" sketch. Given that there hasn't been a release for the eZ publish 3 series since October 2007 and December 2007 for the initial eZ publish 4.0 release, coupled by the lack of any concrete information regarding new releases, one may be forgiven in thinking that eZ Publish had been consigned to the great bit bucket in the ether. Fortunately it appears that unlike the Norwegian Blue, eZ was actually restin'! (Actually I suspect they have been working very hard, just not telling us) I'm not sure how many people are downloading and reading eZ's SHARE! magazine PDF but if you're not then you would have missed this news regarding eZ Publish 4.1 from the June issue : eZ Publish 4.1 - what’s new? The next version of our flagship product eZ Publish 4.1 will be released with an improved kernel and severa