papaya CMS 5.3

Changes for papaya CMS from version 5.3.4 to 5.3.5:

New abstraction in PapayaUtilStringUtf8 for string operations length, position and copy

Because of changes to the base tables those need to be synchronized in the module manager (or installer).

Some APIs were deprecated: PapayaUiDialogInput ( functionality is now in
PapayaUiDialog ) and PapayaObject::getApplication() ( use
PapayaObject::papaya() instead ). For now backward compatiblity is in place.

Because of changes to the table papaya_modulegroups the installer needs to be rerun (using the module manager is not sufficient).
Popup links now have the additional options scrollbar, toolbar and resize.
The rich text editor in the back end now leaves anchors alone.

It is now possible to specify a class prefix in modules.xml files to use the papaya autoloader for classes in custom modules. An example for this can be found in papaya-lib/modules/free/Tasks/modules.xml with the prefix PapayaModuleTasks .
The TinyMCE used in the back end was updated to version 3.4.2 .
A selectable content css file for the richt ext editor in the back end is now supported. TinyMCE will extract the defined classes and use them for a dropdown.

The classes starting with PapayaInterface were renamed to start with PapayaUi instead.
Images that are inserted with the rich text editor (papaya:media tag) that have a subtitle now use span elements as containers to avoid invalid HTML, thus custom xsl templates and css themes may need to be adapted.
PapayaObject is now an abstract class and thus can't be instanciated on its own.