Posts filed under 'eZ Publish'
The 31st of March, the pubsvn community Subversion repository will be made read-only and rest in peace. This Subversion repository has served the community for several years, as a central repository where all community contributed extensions could live their life. However, with the growing amount of users and extensions, “one repository to serve them all” is not the preferred way to go anymore. Therefore projects.ez.no saw the daylight, further referred to as “eZ Projects”.
If you want to move the source code of your current projects currently living in http://pubsvn.ez.no/community, then please register these projects on eZ Projects. Once they are approved there, send me an e-mail (preferably with the subject: “pubsvn community migration”) with the full path to the project in the community repository as well as the Unix name of the matching project registered at eZ Projects. I will load the Subversion history from the community repository in your new dedicated repository on eZ Projects and reply you when it’s done.
February 27th, 2008
eZ Labs Belgium, the Belgian office of eZ systems, is recruiting core / system developers. If you’re interested, then take a look at the job description!
August 8th, 2007
On Saturday the 9th of June, the day after the eZ conference, there will be a rather small (compared to the eZ conference) eZ publish developers event. You can find more general information in a summary at eZpedia, a summary at ez.no and Paul’s announcement at the ez.no forums.
I’m not 100% sure yet what I will talk about, because there are a lot of interesting topics showing up lately. One of them could be the reuse of the database of 3rd party applications by using persistent objects. We recently integrated data from a custom made, basic ERP system in an eZ publish intranet this way. The open source MS SQL database plugin I made was also part of this solution.
Another area that’s bothering me for a long time is the inability of the current eZ publish package management system to find and retrieve updated packages from remote repositories in a more automated way. Last week I did some experiments based on existing code of the setup wizard and I’m sure that with a little more work this package update manager could become pretty cool. Some client code will be released right before the developer workshop. A package repository server extension is in it’s child shoes too. It would be great if this could be a part of the eZ projects site.
With that remark I come to my next possible subject, the status of eZ projects and a little insight in the tools used to get this framework up and running.
Finally, there’s also the existing PHP 5 port which runs pretty smooth most of the time.
C ya next Saturday!
June 2nd, 2007
Xavier Dutoit once pointed me to a nice unobtrusive table sort script written by Frequency Decoder. I will explain you how you can use it with the tables inserted in an XML block attribute.
Continue Reading April 13th, 2007
I’d like to give you a short overview of what is planned for the new projects section of ez.no, which will replace the current contributions section and the pubsvn community Subversion repository.
Project registration – After publishing a project, a workflow event will setup the project structure based upon a skeleton. The skeleton is in fact an existing subtree on your site. This makes the workflow event very flexible. All descendants of the skeleton root node will be copied under the new project. The workflow also automatically assigns roles to specific user group nodes copied from the skeleton. These role assignments are limited to the project subtree. The workflow will also add the project creator to a specific user group node copied from the skeleton.
Project source code repository – Another workflow event will make a private Subversion repository for the project, either on the same host the eZ publish site is running on or on another host trough SSH. Authentication to the Subversion repositories is controlled with an Apache htpasswd file. A cronjob will regularly recreate the htpasswd file based on the account data in the eZ publish users table, so new users are added and passwords are synchronized. Another cronjob will regularly recreate an authz SVN access file, which is used to control the access rights (read / write) to the different Subversion repositories. If you place the Subversion repositories on another host, then the htpasswd and authz SVN access files need to be moved to this host with a utily like rsync.
Project membership – Users can request to become member of a specific project user group. The membership extension will accomplish this. In a next phase sending out invitations by e-mail will be implemented.
The PHP coding has finished. Now it’s just a matter of modifying templates, testing and setting it all up on projects.ez.no …
February 17th, 2007
Next Posts
Previous Posts
