Authentication Cache Can Be Deactivated
The authentication cache in the Content Manager (CM) reduces the number of authentication requests sent to the user manager. Due to the master-slave architecture of the CM, if an external user manager is used (an LDAP server, for example), the authentication cache might cause a password change to not be recognized immediately because slaves are not notified of the change.
To take account of this, the authentication cache of the CM can now be switched off. To do this, set the cacheAuthentication option in the config/tuning.xml configuration file to false:
<userManProxy>
<cacheAuthentication>false</cacheAuthentication>
</userManProxy>Afterwards, restart the CM.
Generating forms for OMC activities
In Rails applications you can now have forms generated that are derived from activity types in the OMC. The form fields generated suit the fields of the respective activity type. When such a form is submitted, a corresponding activity including the filled-in fields can be created in the OMC.
Performance Optimization
The performance of the Rails Connector has been optimized. As a result, less CPU load is caused, and fewer database requests are issued.
Dedicated Controllers for File Formats
In Rails applications that include the Rails Connector, controllers can be defined that apply only to specific file formats in the CMS. Up to now, all requests were directed to the CmsController. Now, by means of dedicated controllers for file formats, Rails applications can be better structured.
Default Obj#sorted_toclist Sorting
If no sort oder has been specified for a folder in the CMS, Obj#sorted_toclist now sorts the CMS files by name in ascending order.
URL Options for cms_path and cms_url
If cms_path or cms_url is used to generate a URL for a page, additional GET parameters can now be specified by means of the second argument.
File Size Can Be Determined with Obj#body_length
In the Rails Connector, the size of a CMS file can now be determined using the body_length method. This makes it possible, for example, to specify the size of a downloadable file on web pages.
No Automatically Generated Classes for File Formats of Objects
The Rails Connector automatically assigns to a CMS file the Ruby class whose name corresponds to the name of the file’s format. Previously, up to and including version 6.7.2, if no Ruby class matching the file format existed in the Rails application, a Ruby class was generated automatically during runtime.
Some users of the Rails Connector criticized this behavior because it prevented them from getting full control of the number of classes and, especially, of the moment they were created in their application. This increased the chances of making programming errors.
Therefore, this bahavior of the Rails Connectors has been modified: If no matching class exists for a file format, always the base class, Obj, is assigned to the file. Classes are no longer generated automatically at runtime.
Independently of this, page types can be extended by creating a class whose name equals the name of the file format. The name of an object's file format should be determined using the obj_class field:
@obj.obj_class == "PressRelease"Adaptable Error Pages in Rails Applications
The error pages displayed for the HTTP status codes 403 and 410 can now be individually adapted via the controller. For further information please refer to the Rails Connector documentation and the RDoc documentation for the CmsAccessible module, which is part of the Rails Connector.
Extended Access to the Logged-in OMC Contact Person
The logged-in contact person, accessible from within views and controllers by means of the current_user method, can now be set and reloaded. For further information, please refer to the RDoc documentation for the OMC::AuthenticationSupport module, which is part of the Rails Connector.
Generating a Table of Contents from a CMS Folder
The Rails Connector now offers a convenient way to generate a table of contents from the CMS files contained in a CMS folder. The TableOfContentsHelper available for this purpose takes the live access permissions of the individual subfiles as well as their sorting into account.
For further details please refer to the RDoc documentation for the TableOfContentsHelper module.
Some Portlets Can Use the Same Templates
Portlets making use of dalogs based on the InstanceDialog class (e.g. the Gallery or the Voting portlet) can now be configured by means of the useCommonTemplates initialization parameter to use unspecific templates instead of instance-specific templates. Unspecific templates are located, for example, in WEB-INF/templates/voting instead of WEB-INF/templates/voting/InstanceName.