All Collections
CMS
Release Notes
Solodev CMS 9.7 Release Notes
Solodev CMS 9.7 Release Notes

Learn about the latest features and improvements in Version 9.7

Matthew Garrepy avatar
Written by Matthew Garrepy
Updated over a week ago

Solodev CMS 9.7 contains new features, updates, bug fixes, and user interface (UI) enhancements to the Solodev content management system. Version 9.7 further optimizes the performance of the platform and modernizes code to reflect current technologies and practices.

Upgrades include both Okta SSO and Salesforce API integrations, as well as improved spam prevention for Solodev forms. New features include enhanced search capabilities for webfiles in STMLs, updates to dynamic div styling, and more.

Key Release Highlights

  • Enhanced spam prevention for form submissions

  • Improved cleaning of user-submitted data

  • Updated SSL certificate for solodev.net

  • Added new OKTA SSO integration

  • Added Salesforce API integration to access documents/files hosted on SFDC

New Features

  • Added new search capability for locating webfiles files in STMLs (audit file)

  • Added config settings for Salesforce and composer library for SFDC connection

  • Updated highlighted dynamic div styling

Improvements

  • Removed outdated PHP code to enhance overall security

  • Enhanced customization capabilities when adding a packaged website

  • Added permission for contacts to generate their own API token

  • Added "useragent" settings for basic cURL calls

  • Removed outdated Slim include from the codebase

  • Updated REST API to OpenAPI version 3.0

  • Improved local development with webpack

Bug Fixes

  • Reworked navigation to clarify user flow back to Solodev Cloud

  • Removed frontend reference to webpack JavaScript references in shortcodes

  • Moved up HTML email generation, so it correctly passes to workflow processing

  • Changed conditions for rank to be “display_rank”

  • Updated “get data” call on datatables, enabling legacy detail templates from inserted datatables to still function

  • Updated Zencoder with “content-type” header check

Did this answer your question?