All Collections
Release Notes
Solodev CMS 9.6 Release Notes
Solodev CMS 9.6 Release Notes

Learn about the latest features and improvements in Version 9.6

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

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

Noteworthy upgrades include expanded honeypot capabilities for added spam protection, a more user-friendly contact support page to manage CMS issues, and several integrated features for launching Solodev CMS from Solodev Cloud.

Key Release Highlights

  • Added a new datatable property to enable or disable basic honeypot protection for spam form submissions

  • Deployed conditional license confirmation for frontend websites, so only backend functionality is disabled when a CMS license expires

  • Released a new, more user-friendly contact support page for managing license issues and troubleshooting other general CMS-related challenges


  • Updated "add actions" for websites, apps, and modules, so it now reflects a full page build out of new action screens

  • Upgraded "add actions" for users, websites, and apps to redirect to Solodev Cloud when a Solodev CMS is initially deployed from Solodev Cloud

  • Consolidated repo code bases so all Solodev source code is easier to manage

  • Incorporated new code into the build process of the CMS (via helm)

  • Updated the list of default npm packages that are installed on the server level to help speed up the package importing process

  • Started implementing a new license checking script

Bug Fixes

  • Updated MongoDB restore script for enterprise builds, enabling them to pull in the correct primary server information

  • Fixed MongoDB code so it correctly pulls in module fields when the "module_id" is included in the "$and" portion of a query

  • Improved package importer, ensuring that enhanced control variables are passed to new objects

  • Deployed general JavaScript improvements that were impacting user experience

Did this answer your question?