Release 0.8.0 RC1 of the eZ Lightbox extension has just been released. The new release is available as a new package in the download area of the project. This release should not be used in productive environments yet. It is supposed to be used for testing the new lightbox permissions and the changes made in the permission system of the lightbox module.

Lots of new features and 2 bug fixes in this new release:

• added support for calling external services that require simple POST (a.k.a. html forms) to the template fetch function / ggeZWebservicesClient class
• added a view to invoke webservices without the need of a specific controller file: /webservices/execute/$protocol (supported protocols are currently xmlrpc and jsonrpc)
• permissions to execute - with limitation on single webservices - can be granted on that view
• add support of exposing ezjscore webservices to xmlrpc/jsonrpc calls via that view
• added the Y.io.jsonrpc javascript function for Yui 3 (in module 'io-jsonrpc') to ease execution of jsonrpc calls from the browser
• moved javascript libraries to 'standard' design, so that they can be used for front-end interfaces too
• added a cronjob to rotate logs of executed ws calls. By default added to infrequent set
• upgrade the included phpxmlrpc lib to 3.0.0 beta, fixing all warnings with php 5.3
• webservice server classes now catch exceptions raised by user-provided functions while handling invocation calls; use the server's $exception_handling member to finetune this behaviour
• allow module view (and custom controllers too) to load all functions in soap/jsonrpc/xmlrpc dirs regardless of the incoming call's protocol. Set RegisterAllProtocolsFunctions=enabled to activate
• fix: give a debuggable error message if soap extension is not enabled and user tries to create a ggPhpSOAPClient
• fix: bad php constants where used by ggXMLRPCServer if invalid params where received

There have veen a couple of incompatible changes too - please read carefully the changelog before upgrade.

A community project for creating a community extension.This can be a co-operation project like cosmosui.org (read more about it). Where we have a extension who connects to ez where every plugin can communicate with this extension.Plugins:* Easier blogging system - users could create blogs theyre self, choosing if blog in subdomain or in folder and wich folder.* Profile system - give users theyre own channels with private messaging, information, latest activity.... They could also choose style if administrator set "yes"* Bookmarking - Give users a option to easy get acess to pages. Example: Interesting article about dogs. The user an save it as a bookmark and choose if he want to publish it to profile or have it private.* User groups - A portal pages for groups including: Forums, News, Members, Files, Mailing list ...*Mailing list and Newsletter - Let users signup for a mailing list created by editors advanced functionality is the hting here. And Mailing list improving the social thing more!* Forums - adding bbcodes, profil boxes and changing layout* Youtube like function

Allow a page to be created 'on the fly' when that page doesn't exist.When creating a link to an ezobject (e.g. when using OE), if the object does not exist, allow user to create it via a dialogue which allows them to specify content class, the minimum required attributes of that class and the main location of new node. Each of these values should carry defaults. Could default to a class which only requires a title and carries a default location to be a sub-item of the current item.Much of the UI is already in place (as per search or browse when ezobject link type is selected) but would need a 'Create here' button added and a cut-down version of the content creation form to only include the minimum required attributes. Dialogue could also be manually opened or could be triggered by for example detection of CamelCase text in content.