Step Two: Override the default module templates
So getting back to the template we want to customize, we are going to create a new file in the skin directory we just cloned.
For this example let's pretend we named our cloned skin "Clone". When I log in via FTP and go to the skins directory, I will now see something like this:
So "Clone" is now the active skin - it's a copy of the jrElastic skin, and is where I'm going to do my modifications.
Earlier we want to customize the following template:
so to do that, I'm going to create the following new file
and customize it to suit my needs. When Jamroom "sees" there is a module override template
located in the active skin directory, it will use that template in place of the default template that is provided by the module.
So once we've done that, we are good to go:
- our changes to the jrAudio item_detail.tpl cannot be made inactive by upgrading the Audio module
- since we are making our changes to the "Clone" skin, it cannot be made inactive by upgrading the jrElastic skin.