Option 1: Let our developers do it for you
We'll upgrade your store to the latest version whilst preserving your customisations, as part of our technical support service. We have the experience and tools to do this safely and always take a full backup first. Find out more at cubecart.com/technical-support.
Option 2: Do it yourself (Advanced)
CubeCart has an extensive hooks system that allows modifications to be made outside of the core files. However, occasionally core files do need to be changed directly, which can make upgrading more complex.
The recommended approach is to fork CubeCart on GitHub and merge in updates as they are released. This keeps your customisations separate from the core code and makes future upgrades straightforward.
If you haven't forked the code and already have a modified store, upgrading is still possible. Start by identifying the version your store is currently running — this can be found in the Overview tab of your admin dashboard, or in the ini.inc.php file in the root of your store.
Once you know your current version, download that version's original package from our website. Extract it and use a file comparison tool to identify any changes you have made to the core files. A user-friendly option is Beyond Compare, though command-line tools such as diff on Linux work just as well.
If you use Beyond Compare, perform a folder comparison between your store and the original package. Click Diffs No Orphans at the top to filter to changed files only, then use Expand to show all differences. From the Edit menu choose Select All Files, then use the Actions menu to generate a File Compare Report. Choose a side-by-side HTML report with the option set to Differences.
This will give you a clear record of every customisation made to your store. You can then upgrade to the latest version and use the report to reapply your changes.