Jump to content
Charles

Pages Improvements

Our Pages CMS is one of our most popular applications as we are continuing to improve it based on feedback. New in 4.1.13 includes:

Designer’s Mode HTML Editing

This update allows you to edit your HTML mode pages inside the designer's mode file system. Any edits you make, once saved in your text editor are instantly available which makes it much faster to build HTML pages with Pages.

designers_mode.jpg

 

Database Template Improvements

We listened to a lot of feedback about templating within the AdminCP for Pages and one common request was for a way to delete a group of database templates and to rename those groups. When you import databases, the template group names are created unique but you may want to change this to something more memorable. You will see here that the dialog also shows you which databases this template is used.

cms_template_options.jpg

 

Page titles when using databases

Currently, when you add a database to a page, the page title is replaced with the database name. This may not always be desirable, and you may want the page title to remain in all database URLs (such as record view). There is now an option for this per database.

page_title.jpg

Relational Field Improvements

Now when you create a relational link between databases, you can opt to show which records link to the relational record. To give you an example, say you had a database for actors, and a database for movies, and you created a link on the actors record to show which movies they star in; now when viewing the movie, it will show you a list of the actors.

reciprocal_linking.jpg

 

More Filterable Fields

We added both "Date" and "YesNo" field types to be filterable when viewing a list of records. When you use the Date type, you can select a date range for listing articles.

YesNo_and_date_filters.jpg

We also added the ability to use any custom field set as filterable to be used when creating a database feed widget.

custom_fields_in_recordFeed.jpg

 

Unique Fields

Another popular request was to allow a way to force unique entries for custom fields. This means that when enabled, only one record per database can have the same value. This is enabled when creating or editing a field.

unique_fields.jpg

 

Other improvements

You can now quickly delete an entire media folder via the AdminCP.

Media.jpg

You can now quickly see which databases are used on which pages via the AdminCP page list.

badges_on_pages.jpg

 

And we added a way to programatically fetch a custom field value via the $record object. Currently, you need to use something like $record->field_12 which works well until you import that database to another installation. The fields are renumbered so this syntax no longer works. We made it possible to use the field key like so $record->field_{my_key_name_here}. Not only does this solve the issue when importing databases, it is also much more readable and easier to remember!

field_consistency.jpg


×
×
  • Create New...