What is the best way to handle custom module updates without breaking core CMSMS functionality?

[lylybrown]

Hi everyone,

I’m currently working on a custom module for a client project, and I want to make sure future updates to CMS Made Simple won’t break the functionality of this module.

What’s the best practice for handling updates? Should I rely mainly on hooks/events, or is it safer to extend core classes where needed? Also, do you typically set up a version compatibility check within your modules?

I’d really appreciate insights from developers who have maintained custom modules across multiple CMSMS versions.

Thanks!