Saurus 4.1 technical notes
Article Editor
Version 3: The editor used Microsoft ActiveX component that limited the browser support to Internet Explorer only.
Version 4: We now fully support Mozilla Firefox and therefore use a new component. In versions 4.0.0 to 4.0.14 we used HTML Area (www.htmlarea.com) but changed to FCKeditor (www.fckeditor.net) in 4.0.15. This fixed most of the bugs related to the text editing functions in prior Saurus 4 versions. The new features include search & replace within an article, new lead/body separator, insert anchor, insert special character, right-click context menu, paste-from Word, context-sensitive style dropdown.
The new article editor does not use the Saurus CMS glossary anymore, but JavaScript files instead. The language files are stored in js/fckeditor/editor/plugins/scms_actions/lang/ and js/fckeditor/editor/lang/ folders.
File Manager
Version 3: All public files were stored in failid/ folder in site root.
Version 4: There are now two folders in site root - public/ for files with public HTTP access and shared/ where the user Read-access can be set. The old failid/ folder is deprecated.
Users
Version 3: Registered users module used MySQL ENCODE() function and custom registration key for encrypting users passwords, which made possible to decrypt registered user’s password when needed. The editor’s passwords were using different algorithm and passwords were not decryptable.
Version 4: Since registered users and editors now use the same password encryption algorithm, the passwords cannot be decrypted anymore.
CSS Styles
The "Admin > Visual Design > CSS Styles" page now has three text areas:
- "Site CSS styles" is the only one of these that is included in styles.php output. The styles defined in "Visual Design > Site Styles" and "Visual Design > Text Styles" in prior Saurus versions are converted here and these pages are now deprecated.
- "Styles in article editor dropdown" are available for content editor to choose from. Both HTML tags and classes or combination of these can be defined here. For example: H1 {}, PRE {}, .greentext {}, IMG.noborder {}, TD.title {}. Note that the dropdown in Article Editor is context sensitive so IMG.noborder style would be listed only when an image is selected.
These styles are not included in styles.php so you have to redefine appropriate styles there. The purpose for doing this is that you can separately define H1 which is used in Article Editor and different styles in site areas, for example #header H1 {} and #content H1 {}.
The installation script converts styles defined by Visual Styles> Fonts page in previous Saurus versions here. - "Styles used only by article editor" is available only in Article Editor and changes the format of the article's content area. Here you can set the background color and default font. For example: body { color: white; font-size: 11px; }
Extensions
Check the extensions/sample/ directory for a sample, also look inside the extension.config.php file. The extension can define templates and also administrator tools.
HTML
For proper functioning, the edit mode and action-buttons need that the following should be included in the page template HTML code:
The HTML namespace should be extended with xmlns:editor:
<html xmlns:editor="http://www.saurus.info/">
JavaScript library:
<script type="text/javascript" src="{$wwwroot}/js/yld.js"></script>
Style definitions:
<link rel="stylesheet" type="text/css" href="{$wwwroot}/styles.php">
Site encoding
In version 3, the default site encoding that shipped with the installation package was ISO-8859-1. In version 4, the default encoding is UTF-8 for wider compatibility.
Config.php
Until version 4.0.15, this text file containing the database connection parameters had to be in site root, /admin and /editor folders. Now the file in site root is exclusively used and the other two are deprecated.
Default templates
Saurus 4 ships with new content templates that are open-source and base on Saurus API. These templates are packaged as an extension and are overwritten by product version upgrade. If you wish to modify them, make a copy of extension to create a custom version.
The PHP built-in content templates from Saurus 3 are only available for those who upgrade from previous versions prior 4.
PHP template “ATP”
For version 2 compatibility, the version 3 included built-in PHP template named “ATP”. This template is now deprecated and removed from the product. If you need to upgrade a site that uses this template, contact Saurus support for equivalent Saurus API template.
RSS