blog documentation FAQ forum marketplace youtube

Merging Module and Skin Updates

The Jamroom Network » Documentation » Customizing Your Skin » Merging Module and Skin Updates
Applies to: Jamroom 7.0+ Last verified: 2026-10-24

Table of Contents:


Two ways to customize
How the Marketplace stores updates
Rebase tools
Your own skin

  • Two ways to customize

    How you bring updates into your changes depends on where you make them:

    1. In the ACP: the Template Editor and a cloned skin. Use Compare, as in Keeping a Cloned Skin Up to Date.
    2. In files, with your own editor and version control such as Git. Read on.

  • How the Marketplace stores updates

    The Marketplace installs each version of a module or skin in its own folder, such as skins/jrElastic2-release-2.1.2. The normal folder name, skins/jrElastic2, is a symlink to the newest version. So the server can hold several versions, but only one is used.

    That makes it hard to see what changed in version control: each update is a new folder.

  • Rebase tools

    Developer Tools has Rebase Skins and Rebase Modules tools. They move the newest version back into the normal folder and remove the symlink, and can delete the old versions. In version control, an update then shows as changes to the same files.

    To show these tools, turn on Enable Reset Tools in Developer Tools' Global Config. They're then under Tools.

  • Rebasing changes folders on the server. Back up your site first, and don't run it on a live site you can't restore.

  • Your own skin

    If you build in files, clone the skin first (Cloning a Skin) and keep the clone in version control. Then compare it with each new version of the original, with Compare or your own diff tool.

Tags