CMSB v3.76 Released - Performance Optimizations

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

By Dave - May 2

Hi All, 

Note the following additional information about plugin changes: 

  • Plugin Compatibility: Most plugins will continue to function without modification. However, some may require updates to work with the new .schema.php files (replacing the previous .ini.php format).
  • Potential Issues: If you're seeing numerous notices from a specific plugin, it likely needs updating. This typically happens with older or custom plugins that run setup code on every page load, which we're now optimizing against for performance reasons.

Plugin Updates: We have updates for the following plugins to work with v3.76

If you run into any issues or need assistance, please feel free to let us know.

Dave Edis - Senior Developer
interactivetools.com

You have the wrong date for the release date of the permalinks plugin. s/b May 2, 2025

Jeff Shields
yaadev.com

I am wondering if, since this is such a major breaking change, it would be worth considering bumping CMSB to version 4.x.x and following semver principles. It is so different from the v3 stream that trying to figure out where things change will be confusing.

Jeff Shields
yaadev.com

By Dave - May 5

Hi Jeff,

Thanks for the heads up! Just fixed the Permalinks plugin date to May 5th, 2025.

About going to 4.x.x, that's on our radar, but we want to get more of the internals updated first.  This update shouldn't introduce any major breaking issues, as we've got fallback code that still handles the old .ini.php schema files, and I've upgraded a number of sites without any issue.  

The main thing you might notice is if you have plugins running setup code on every page load (which we're now flagging since it kills performance). You'll see a notice at the top of the page when our createMissingSchemaTablesAndFields() function runs - like when you hit "Database Editor" and it says "Checking for database schema updates...".  It's always done this, but we're just making it more clear.

The same is true for older plugins that recreate schema files on every load—you'll get a heads-up when logged in as admin so you can spot what needs optimization.

Thanks for the feedback and let me know if you run into any issues or have any further questions!

Dave Edis - Senior Developer
interactivetools.com

Hey,

Really like the introduction of the .env.php files.

Can columnEncryptionKey (mysql) be added to the fuction getSettingsToEnvMap, so that all sensitive data is removed from the settings.dat.php files?

Ideally, also smtp_hostname and adminUrl

Cheers

Rob

By KennyH - May 30 - edited: May 30

Just a small bug here for 3.76, but the FontAwesome Icon for 'menuType' => 'link', doesn't like the newer class names like fa-duotone or fa-solid like the other schema types do. It still wants fad fa-

so 'menuPrefixIcon' => 'fa-duotone fa-solid fa-eye', doesn't show up right

but 'menuPrefixIcon' => 'fad fa-eye', shows up right

By Dave - June 2

Hi All, 

Thanks for the feature suggestions.  We just released an urgent maintenance release (v3.77), but I've made a note of these and will review these for possible inclusion in the next release.

Dave Edis - Senior Developer
interactivetools.com