Ariadne 8.0 released

This release is actually 2.8.0, but as announced last year we will skip the 2 and name it 8.0. New versions of Ariadne will always be backwards compatible or have an automated upgrade script.

This release removes a lot of ancient templates. This means that if you still have code that relies on old widgets or ancient user interface templates, your code may break. You can either update the code to use the new templates or install the seperate compatibility pack ( ftp://ftp.muze.nl/pub/ariadne/2.7-compat.zip ) to get all your old templates back.

Ariadne 8.0 has removed all of the deprecated functions in php 5.3 so you should be able to use the default PHP error settings. The XSS protection introduced in 2.7.7 is improved, we fixed a number of vulnerabilities in Ariadne itself as well as added a few potential XSS attack vectors.

As promised this release adds Workspaces. If you install Ariadne 8.0 from scratch all you need to do to enable it is to check the workspaces support checkbox in the installer or run the upgrade.to-workspaces.php script in the ariadne/www/install/upgrade/ directory. This is a very experimental feature, expect bugs and surprises if you enable it, do not use it in a production environment yet.

This version of Workspaces is limited to a single staging environment. To use it you'll need to add a seperate virtual host in your apache config. This virtual host is the only way to access the staging workspace. Ariadne itself has no knowledge of the workspace unless you start Ariadne through this virtual host. If you work in a workspace, Ariadne switches to a green background instead of the default blue one to show this. For now you can read more about configuring workspaces in docs\workspaces, we'll add a manual online at http://ariadne-cms.org/ soon.

Other changes include a simpler way to re-use the dialogs in Ariadne in your own applications - see www/js/muze/dialog.js for more information. Templates are now compiled more efficiently to get the maximum benefit from opcode caching. You can tag templates as private - which prevents them from being called directly - you must first call another template. Sites can have multiple URL's - the URL used will be kept when browsing through the site. When logged in as Administrator you can switch to a new user and view a webpage with the new View As feature. Finally you can add 'order by none' to a search query and skip the default ordering - this can dramatically increase the performance of some queries.