Tribiq CMS 6.0.5

We're delighted to announce that Tribiq CMS  6.0.5 has been released.

This is scheduled to be the penultimate version of Tribiq CMS in the 6.0 range, as we are already working on our major upgrade to version 6.1 (details to be released soon).

6.0.5 boasts some significant new features in the areas of image management, extranet users and administrator permissions, plus a wide range of other improvements and bug fixes.

Image management

Images can now be edited after being uploaded; administrators can now set a default alt tag, title attribute and change the image filename for better internal organisation.

On multilingual sites an administrator may wish to set these names on the image itself in the administrator's working language for easier management, while for display to visitors, a suitable setting on wireframe Banners allows the names to be overridden such that they appear in the correct visitor language. 

When viewing an image in the admin back-end using a floating box, you can now see quickly see the image dimensions in pixels.

When displaying images using Banners or Content Summary Lists (i.e. whether defined manually, or as "Sticky" images attached to Content Items) you can now resize the image and (for Banners) crop the image and apply an offset.  This gives you more control over the display galleries and lists with thumbnail images.

Image storage: Images are now stored in silos; for example, images used in content items are now stored separately from images used in emails. When modules are installed, they can declare their images to be stored in new image silos. The result is less clutter for administrators when choosing an image.

There is a "shared" flag available for images, so that when you upload an image you can specify that it is Shared and thereby easy to locate when finding images for Content Items, Email Newsletters or other kinds of content.

We have also improved the visitor-facing image processing speed by introducing "working image" versions of the original image. If you upload images of 2,000 or 3,000-pixel dimensions, yet only usually display them at thumbnail size, the CMS will store various working images at less than the large original size, and use these when generating the thumbnail, thus improving performance as the thumbnail-generation routine can be made from an intermediate sized image.

There are now site-wide settings (in Administration->Site Settings) that control the compression quality for JPEG images.

Extranet functionality and user data 

We now support many more ways in which you can extend User-related data. Tribiq's User Characteristics system now supports the storing of multiple values for a User (akin to checkboxes with pre-defined values); and also a text area. You can now store Yes/No, radio-style, checkbox-style, single-line text and multi-line text data against each User.

Alongside this, there is a powerful new Advanced Search feature to assist searching User data. This allows you to use Groups and Characteristics as inclusion and as exclusion criteria. The presence of Advanced Search will also underpin many more types of User search to be implemented in future.

There are now more options for EU privacy law compliance, including the handling of "implied consent", and new settings on the extranet login and registration modules.

There is now better handling for suspended extranet users when they attempt to log in.

Administrator permissions

The whole range of administrator permissions has been updated, so that they are now better aligned with Author, Menu Editor, Publisher, Designer, Supervisor and Extranet User Manager. (The Sysadmin permission set has been removed and its granular permissions merged into other permissions.) This makes the CMS more intuitive when setting up websites to be run by several administrators, while still allowing granular permission control on Pro.

Tribiq CMS now supports module-based permissions too: when you install a module, it can declare new permissions for administrators for the use of that module.

There is now better handling of password recovery. When an admin asks for a password reset, the CMS now sets a temporary password, which expires after 24 hours, but in the mean time if the administrator logs in again with the original password then the temporary one is destroyed. This deals with the situation of an administrator having to change his password because of an unauthorised person attempted a password reset.

When an administrator creates a Draft to edit a Content Item, the Item is no longer checked-out by default. There is now a Site Setting to determine whether Items are checked-out automatically. 

Changes when working with the menu 

We have added an admin toolbar function to allow a Content Item to be attached to the menu hierarchy, and to detach from the hierarchy. Attaching the Content Item to the menu can be helpful even if the Item is already attached, so as to create a Secondary Menu Node, i.e. so that more than one Menu Node links to that Content Item. Detaching can be helpful to make a Content Item become an orphan, or when moving it to a different part of the menu.

When adding a Content Item to the menu hierarchy, you can now "quick-add" the Item to the menu; its Title will be used to populate the menu node text.

You can now select multiple Content Items at once in the admin back-end and add them en masse to the menu, rather than one at a time.

Orphaned Content Items (i.e. Items not in the menu) are now more clearly identified in the admin back-end.

General improvemnets

In the admin back-end, the default view of Content Items has been modified to make them more appropriate to the Content Type (for example, News items now show Release Date by default). 

While editing, the admin toolbar now faithfully shows when edits have been made, now showing changes that have been saved which have not caused the page to reload.

When working within Plugin Nests and Slideshows, the settings box of nested Plugins now has both a Save & Continue and a Save & Close button. With Save & Continue you can more conveniently try out new settings and see the result in the upper half of the page, before closing the floating admin boxes.

The quick admin view (i.e. a view of the admin back-end is shown hovering over the lower part of the web page) now has a switch to flick it instantly to a full-page window size. This is handy when working with slideshows and plugin nests, which may contain many Banners (as in the case of an image gallery). Going to the full-size view makes it far easier to sort nested Plugins using drag and drop.

The admin back-end main navigation now has Email instead of Email Templates. Under Email you will now find Email Templates, and Email Log, which maintains the log of all sent mail from the CMS. We have added the ability to define an SMTP server so that if you are unable to have your system send email directly (e.g. using the PHP mail() function) then you can define a separate SMTP server, with password and other security settings defined if needed. There is a "test" button with which you can easily have the CMS send an email through the chosen method.

When opening floating admin boxes, there is now a more intuitive experience, with the cursor being auto-focussed on the first field by default.

There is now a sample site installation facility. When performing a first install, it is now possible, instead of installing an empty site, you can choose from a sample site.

Templates are now universally identified with a code number such as "T01", rather than only the descriptive name, to reduce ambiguity on sites with many templates.

A problem has been fixed when doing a quick-create of a Content Item; where its title contained accented characters it had the potential to set the suggested Alias incorrectly. 

Whenever an administrator sees the name of a language, the English name of the language can be seen along with the language code, rather than just the local name of the language.

When the CMS performs browser-based language detection on a multi-language site, it is now possible to specify a range of matching language codes for each language.

Extracted text from CMS Documents is now held in a new table that exists just for that purpose. Microsoft Word documents are scanned using antiword (provided it is present on the server) and PDFs are scanned using pdftotext. In both cases a plain text extract is stored so that Documents can be searched using a full-text search. (Note that all of this functionality is OS-dependent, we recommend Linux for best compatibility in this respect).

Changes to specific modules

Forum Search - minor improvement to show the forum and thread that a result comes from.

Organisation Manager - now supports the definition of Roles, such that any User can be related with any Location using a given Role. This permits easy modelling of people who have given positions in organisations. 

The Multi-Stage Flexible Form has been migrated to Tribiq 6.

The Event Booking module has been migrated to Tribiq 6.

Meta Data module can now display the language name and language code of the current Content Item.

Location Manager: in Business Sectors, when working with hierarchies, you can now define a maximum depth of hierarchy. Location Manager now supports CSV export.

For module developers

Sample modules: these have been updated to make them easier to use and understand, with better documentation within the modules.

CSS file wrappers are no longer on by default. With this setting on, you can optimise the speed of a site as the CMS wraps together CSS files for Plugin Swatches and Skins. You can now turn the setting off, which makes it easier to debug CSS while developing the site, as the source of the CSS can be seen in the page source.