Aissac Blog

The Globalize2 extension for Radiant CMS allows you to easily translate the content of your site into any number of languages.

It uses the Globalize2 Rails plugin based on the I18N API available in Rails since version 2.2

Features:

• Provides the ability to translate your pages (title, slug, breadcrumb, description, keywords) using the Radiant admin interface.
• Provides the ability to translate your snippets and layouts using the Radiant admin interface.
• Radius tags for accessing the locales and translations.
• Possibility to completely delete the translation for a page.

Check out the source code on github.

For installation and configuration details visit the Radiant Globalize2 Extension documentation page.

To translate your Paperclipped assets, you can use Radiant Globalize2 Paperclipped Extension:

Features:

• Provides the ability to translate Paperclipped assets (title and caption) using the Radiant admin interface.
• Altered Paperclipped Radius Tags which take into account the locale

Check out the source code on github.

For installation and configuration details visit the Radiant Globalize2 Paperclipped Extension documentation page.

The new Blade interface from Radiant is awesome, but you need to modify a little your extensions. We did that and here’s what we got:

Radiant Custom Fields extension (github repository):

An extension that allows you to add custom fields to pages.

Radiant Database Mailer extension (github repository):

An extension that adds database persistence to emailed forms. It works on top of the Radiant Mailer extension and the fields recorded to the database are user defined.

Radiant Member Extension (github repository):

An extension that adds members support to Radiant CMS. Using this extension you can restrict access to pages on your public site to be accessible only to members that have an account. It is based on Restful Authentication System, so the member model has almost the same attributes. The members can be added or edited only from Radiant Admin.

Radiant Paginate extension (github repository):

An extension that provides pagination support using Will Paginate.

Radiant Sitemap XML extension (github repository):

This extension automatically creates a XML sitemap for your site.

Radiant Stereotype extension (github repository):

An extension that adds templating support.

Radiant Super Export extension (github repository):

An extension that provides portability to your project by allowing you to export and import the records in the database and making it easy to manage them with a source control tool like Git or Subversion.

Radiant Tiny Paper extension (github repository):

An extension that adds Paperclipped based Tiny MCE support to Radiant CMS. Provides a Rich Text Editor filter and allows you to edit the content using the TinyMCE editor. It also provides an Image and File browser to help you manage the Paperclipped assets.

Announcing the Radiant Sitemap XML Extension.

Features

• Allows you to specify in Radiant admin which pages appear in the sitemap;
• Gives you the possibility to set the change_frequency and priority per page.

Check out the source code on github.

For installation and configuration details visit the Radiant Sitemap XML Extension documentation page.

Radiant Database Mailer Extension is used to add database persistency to emailed forms, and it just got fresh features.

Besides the possibility to save posted form fields and entire email messages to the database and export data to CSV and XLS, now it saves e-mail attachments using paperclip. Any attachments that the email might have will be saved on the file system. They can be downloaded from the details page of every record.

Also, the extension got thoroughly tested using Cucumber and webrat/email_spec.

Check out the source code on github.

For installation and configuration details visit the Radiant Database Mailer Extension documentation page.

Radiant Paginate Extension update:

Features

• Specify number children per page
• Ordering by a specific page attribute and order direction
• Conditionally render content for first page
• Render pagination links customizable from the Radius tag (specify next/prev label, DOM class, inner and outer window etc.)

Check out the source code on github.

For installation and configuration details visit the Radiant Paginate Extension documentation page.

Radiant Super Export Extension update:

Features

• All records are exported to individual YAML files;
• A directory is created for each model in the default import/export path which is db/export;
• The individual YAML files are saved with the record ID as their filename.

Check out the source code on github.

For installation and configuration details visit the Radiant Super Export Extension documentation page.

Radiant Member Extension, used for restricting site content to registered members, got some new features. Also, the configuring got a little easier.

So, what’s new? One small but important feature is the possbility of deleting members.

The next feature is the improved control you have over members with activate/deactivate actions. When you deactivate a member, his password will be copied in a new field making him unable to access his acount. Activating him will copy back his old password.

If before you needed to modify the environment.rb or initializers/member.rb files in order to get the extension up and running, now all this settings are kept in Radiant::Config. You only need to and key/value pairs to this table to get the extension running.

Radiant’s caching prevents us from using Rails’ flash to notify the user of failed login attempts. To work around this, Member Extension uses cookies to store flash messages and Javascript to display them in the view. Now the flash messages can be easily customized from Radiant::Config.

Check out the source code on github.

For installation and configuration details visit the Radiant Member Extension documentation page.

Seeing that Radiant Tiny-Paper Extension got some attention we decided to improve the UI and usability.

As a learning experience and following a notice I read a couple of days ago that said something like “if the erb is too hard to pull in haml, it is likely a code smell” I decided to re-write all the views using HAML.

The Image Browser, has basically the same actions as before but a different layout. The list of images uses the vertical alignment facility I wrote about some time ago. There are two types of views (text-list and thumbnails), you have filtering, sorting and paginating facilities and an upload form to directly upload image assets. The major difference is the way you choose the image size. When you click an image a context menu popup will appear with all the image sizes. The popup also presents the image dimensions in pixels for each size.

The File Browser also has a new layout. There are two sections, one for adding a link to a Radiant Page, and one for adding a link to an uploaded file. The Files Tab has filtering, sorting and paginating facilities and an upload form to directly upload assets. The Pages Tab presents a tree structure of the Radiant pages, excluding the ones that are not published.

Check out the source code on github.

For installation and configuration details visit the Radiant Tiny-Paper Extension documentation page.

Announcing the Radiant Stereotype Extension.

Features:

• Define named templates (stereotypes) for Pages;
• Templates are assigned per-parent Page, making all children have the defined ’stereotype’ by their parent;
• You can specify the new page’s parts, filters, layout and page type.

Check out the source code on github.

For installation and configuration details visit the Radiant Stereotype Extension documentation page.

Announcing the Radiant Custom-Fields Extension.

Features:

• Provides the ability to add custom fields to a Page;
• The Page model is not changed: custom_fields are added as a belongs_to association;
• Admin interface for managing assigned custom fields;
• Radius tags for accessing custom fields.

Check out the source code on github.

For installation and configuration details visit the Custom Fields Extension documentation page.