CMSB v3.15 Released - Maintenance Release - September 17, 2018

4 posts by 2 authors in: Forums > CMS Builder
Last Post: November 8, 2018   (RSS)

By daniel - September 17, 2018

Hey All,

We've just released v3.15 (and we're running it live on our website!).

This release focuses mainly on bug fixes and minor improvements, which include:

  • Section Editors:
    • Added a new section editor field "Section Description" for HTML to be displayed below section titles.
    • Fixed a Javascript error when using advanced filter list fields.
    • Fixed broken links on Searching and Sorting tabs.
    • Fixed a bug on "view" pages for multi-record sections that use upload fields.
  • File Uploading:
    • Uploaded jpegs are now automatically rotated as needed while being saved based on the photo's Exif data.
    • Updated the image resizing code to use less memory to help prevent out-of-memory errors when uploading images with large dimensions. This may be slightly slower in some cases, but the overall performance impact should be small.
    • Improvements to file upload error reporting.
  • CMSB Upgrading: Fixed a bug in certain cases with multiple CMSB databases, and improved error reporting.

Here's the complete changelog for v3.15:

*** September 17, 2018 - Version 3.15 (Maintenance Release)

SERVER REQUIREMENTS
- This software version REQUIRES: PHP 5.6+ and MySQL 5.5+
- NOTE: Some plugins may need to be updated when upgrading from v2.xx

NEW FEATURES
- Section Editors: Added new field "Section Description" for HTML to be displayed below section titles.
- Usability: Uploaded jpegs are now automatically rotated as needed while being saved.

BUG FIXES & MINOR CHANGES
- Image Resizing: Updated resizing code to use less memory (resizing might be slightly slower).
- File Uploading: Updated error reporting to show more descriptive errors.
- File Uploading: Fixed bug when uploading file with no extension.
- utf8mb4 upgrading: Improved error reporting, misc improvements.
- utf8mb4 upgrading: Fixed bug when using multiple CMSB databases with same table prefix.
- Fixed javascript error on advanced filter list fields.
- Fixed broken link on Searching and Sorting tabs for multi-record sections.
- Fixed "view" pages in multi-record sections that use upload fields.
- Misc Code and other minor improvements.

You can download the latest version from our upgrade by donation page: http://www.interactivetools.com/upgrade/

Please post any feedback, questions, or bugs you find!

Thanks!

Daniel
Technical Lead
interactivetools.com

By gkornbluth - October 29, 2018 - edited: October 29, 2018

Thanks for all your hard work in updating this great CMS platform....

I've got a possible minor bug and feature request

Minor bug.

When creating blank line separators I've been using the save and copy facility. This inserts "Copy of" at the beginning of the blank line title replacing the default "---blank line---" field label. These build up so that the label reads "Copy Of, Copy of, Copy of" etc. in bold type. Any chance that a condition to not change the default field label that for blank lines could be added to a future update?

Feature Request.

Any way a 'create field here' functionality could be added to CMSB (core code or plug in) so that we could reduce the need to drag fields up and down one by one?

Thanks,

Jerry Kornbluth

The first CMS Builder reference book is now available on-line!







Take advantage of a free 3 month trial subscription, only for CMSB users, at: http://www.thecmsbcookbook.com/trial.php

By daniel - November 8, 2018

Hi Jerry,

Thanks for the feedback.

Regarding the separator labels, there's a quick fix you can do to prevent "Copy of" from being added. In /cmsb/lib/menus/database/editField_functions.js look for the following line (line 74 of the latest CMSB):

$('#label').val("Copy of " + $('#label').val());

This can be replaced with:

if ($('#fieldType').val() != 'separator') {
  $('#label').val("Copy of " + $('#label').val());
}

This change will also find its way into the next version of CMSB.

Being able to insert fields at a specific point does sound like a helpful feature, and we'll keep it in mind for potential future UI improvements.

Thanks!

Daniel
Technical Lead
interactivetools.com