After skin or module updates by the original developer, what happens to customizations?
Design and Skin Customization
researchcooperative:
Things like the colour of the menu background, the layout of profile pages, or the automatic capitalisation of headings.
Just wondering if you saw my response on how you can easily change your capitalization settings, via your ACP-> Style (css files) TAB:
https://www.jamroom.net/the-jamroom-network/forum/new_posts/36881/do-private-notes-have-an-outbox#last
Changing colors and font styles and spacing issues can all be changed the same way. It took me a little trial and error (and taking down notes when i hit on the right location in the Stle CSS settings for each item, so I wouldn't forget). After a while I began to get a sense of where to find some of these settings in the Style Css TAB and the .css files.
You'll want your own custom SKIN that you keep backed up. That will normally be your site's ACTIVE skin. You start with a pristine Jamroom skin (like Elastic or Ningja) and make a CLONE of it and name it with your custom skin name. When you style your site, you make your custom changes to your custom skin, not to the parent JR skin. It's the parent JR skin that will get the updates from JR periodically. After each update, you can use the skin COMPARE tool to compare the prior JR skin template in question to the new updated JR skin template, to see exactly what the change was and the code will show as newly added. Then you can decide whether you want that new updated change added to your CUSTOM skin...and you add it or not, yourself. Sometimes the change is only a little snippet in the code. If it's hard to find you can ask the JR Team where the new code update is located- in WHICH template in the updated JR skin. Knowing which template has been updated is very helpful when using the Compare tool.
In short, keep an original non-customized JR 'parent' skin and the skin updates from Jamroom will update THAT one. Also create your own custom skin as a clone of the parent skin- your ACTIVE custom skin will have your own skin name and you'll be backing it up periodically for safekeeping. When JR releases updates to the JR skin, you look to see if it's an update that you want to apply to your custom skin- then you locate the new code changes and apply them to your custom skin. (make a backup of your custom skin always before making any changes, in case things get screwed up!)
By the way, this is a handy backup module to have and USE:
https://www.jamroom.net/the-jamroom-network/networkmarket/22/db-and-system-backup
But also learn how to use the ACP-> Developer's Tools-> "Clone Skin" function so you can back up your custom skin to keep it safe, as a habit, before making changes and possibly messing things up.
Learn how to use the "Compare" feature in ACP skin and module templates- at first just look at the differences in the old and new versions of module templates. Being able to do this will be incredibly useful going forward, even if you don't learn how to write code. You don't always need to understand code to see where a word or number has changed, and you can then change a menu link wording or add a row to some picture grid yourself, for example.
Hope some of this helps
updated by @strumelia: 01/08/16 04:55:23PM