Custom scripting vs. upgrading

4 posts by 3 authors in: Forums > CMS Builder
Last Post: September 2, 2010   (RSS)

By ILLUME-MEDIA-LABS - September 2, 2010 - edited: September 2, 2010

Hi Dave,

I've had my dev team do some custom scripting to the backend, including adding a shared asset library (tiny mce library). If I upgrade to 2.06, would I lose those addons and have to reconfigure?

Thanks.

Re: [Illume Magazine] Custom scripting vs. upgrading

By Chris - September 2, 2010

Hi Illume,

In short, yes.

You can do a diff between an original, unmodified version of CMS Builder and your customized version to see what the changes were, then attempt to apply them to the new version. That can get awfully tricky, however, especially when the upgrade includes changes to the files your dev team has changed! You may even need to do a three-way diff to merge your changes in.

Theoretically, if you can make your customizations through the plugin system, you won't need to merge. In practice, you'll probably need to merge a little too, especially if you had to add your own hooks.

My advice would be to hold off until there's a new feature you absolutely can't live without and then ask your dev team to merge your custom changes in.

Out of curiousity, what are the customizations you've had done?
All the best,
Chris

Re: [Illume Magazine] Custom scripting vs. upgrading

By Dave - September 2, 2010

The key thing is to make sure you backup your existing version before you do anything! :)
Dave Edis - Senior Developer
interactivetools.com