Thats not going to work. If im understanding correctly you have
/skins/jrAudioPro/
and your adding extra .tpl files to
/skins/jrAudioPro/custom/fileone.tpl
/skins/jrAudioPro/custom/filetwo.tpl
/skins/jrAudioPro/custom/filethree.tpl
and you're wanting them to show up at:
yoursite.com/fileone
yoursite.com/filetwo
yoursite.com/filethree
... wont work.
Before making changes to a skin, you should be cloining it to xxAudioPro or other name
/skins/xxAudioPro
so your changes dont get lost when updates come in.
I can understand the concept, wanting to just add in over-rides for the skin. We talked about a similar idea a while back where a skin could be a sub-skin of an existing skin.
eg:
/skins/jrAudioPro/(all the files)
then have a sub-skin of that
/skins/xxAudioProSubSkin/index.tpl
Where if the sub skin had a .tpl that matched the one in the master, and the sub skin was active, then the subskins version would be used.
The idea has been put in the backburner as it seams like a developer feature that would be used very rarely.
You
may be able to use a folder in an include.
NORMAL:
{jrCore_include template="header.tpl"}
TRY:
{jrCore_include template="custom/header.tpl"}