Since you mistakenly double installed the MOD, you could have Restored the EM Backups to get it back to the single install. Then you could have created a Template Only version of the MOD and install it into the alternative templates...
Restoring EM Backups
If a MOD that you installed with EM hosed your board or you decide that you just don't want it, simply go into EM History in your ACP MOD Center and click on the Details button next to the MOD entry..
On the bottom of the next page, select Restore Backups and press the Go button. Make sure you DON'T select the Remove Record option or you will be forced to manually rolll back the EM backups that were created for you. I will have to walk you through that if need be...
Next you will see a page to confirm eht operation. You would choose Yes:
MODs can only be uninstalled in reverse order that they were installed: FILO (First In, Last Out). So if you installed a MOD, then several others, then decided to remove the first one, you would have to Restore the backups of the other MODs before you could Restore the backups on the first MOD...
Restoring EM Backups (Manual Instructions)
Download the backups folder that EM created for you in the MOD sub-folder found in admin/mods. Strip the .txt extension from each file in every folder in the backups folder. So the resulting file extensions will be php, tpl, css, and cfg. Upload the files back to their proper locations on your board; i.e.
- copy backups/admin/*.* to phpBB/admin/*.*
- copy backups/includes/*.* to phpBB/includes/*.*
- copy backups/language/lang_english/*.* to phpBB/language/lang_english/*.*
- copy backups/templates/subSilver/*.* to phpBB/templates/subSilver/*.*
- copy backups/*.* to phpBB/*.*
Of course if you have alternate templates and language folders, you will need to copy the files for them as well. I'm referring to phpBB as your forum's root folder in the above copy commands. If your root folder has any other name, just substitute phpBB with the name of your forum's root folder name...
Creating Template Only MODs
All you need to do is create Template Only versions of the MODs that you have installed.
- First create a duplicate of the MOD script in a new text file. To make it easier to remember, just use the same MOD filename that the MOD author used, but add _template_only to the name. So if you are using the TopicCalender.txt file, the new Template only version would be named TopicCalender_template_only.txt.
- Then save the new Template Only MOD and store it in it's own separate templates only folder...
- If there are any files included with the MOD that are supposed to be uploaded to template folders, store them in the new Template only MOD folder maintaining the same folder structure that the original MOD used...
- Next add the name of the new Template to the end of the MOD Title using your favorite Text editor. So the MOD Title could look something like this if Aeolus is your new template name:
Code: Select all
## MOD Title: Topic calendar - Part 1 (common to all setup) Aoelus
EM will recognize this as a new MOD if the MOD Title is different from what it has previously installed...
- Next strip out all NON-Template related modifications. All you want in this new Template Only version of the MOD are alterations for template files only. If there are any copy commands, only keep those that copy included files into template folders too..
- Then rename all instances of subSilver with your new Template name using the Replace All function that you can find in most text editors.
- Now you can upload the new Template Only MOD folder to the admin/mods and run it like you would any other MOD using EM.
If you have added more than one new template, you would want to repeat Steps 6 & 7 for each Template except instead of using subSilver, you would use the name of the last template that you installed using this Template Only version of the MOD. So if the last template you modified with this was Aeolus and you want to apply the changes to Helius next, do a Replace All on Aoelus to Helius...
It really isn't that difficult to update each new template after the fact...
