Hi all
I have recently upgraded a CMS install to v1.11. I was having compatibility problems with module upgrades* on versions 0.9 and 1.10, (causing the Admin pages to not load, in some cases) and manually deleted the module folders to get around this issue.
Now I have 1.11 running, but I have noticed that some modules (CGExtensions and CMSMailer) state in the Module Manager that they have dependencies on modules that are no longer even present on the system (*FrontEndUsers + SelfRegistration, incidentally). Their Active and Install buttons are also not present, presumably because of this.
I am guessing this is because CMS is still detecting these deleted modules in the database? Can anyone suggest a logical method I should take to fix the issue? Or should I be looking into dropping tables in the database? Hopefully it's not as complicated as the latter, so any help will be appreciated.
Thanks
Modules w/ visible dependencies on deleted modules [SOLVED]
Modules w/ visible dependencies on deleted modules [SOLVED]
Last edited by Tetsuo on Mon May 13, 2013 8:01 am, edited 1 time in total.
Re: Modules have visible dependencies on deleted modules
What about installing - de-installing - removing those modules through ModuleManager?
Re: Modules have visible dependencies on deleted modules
If you just delete the folders from /modules it will leave a lot of left over tables in the DB including the table that says what modules are installed, best is to always uninstall them before deleting folders...
Depending on the pre you chose on install(default is cms_) the modules are listed in the cms_modules, but removing them from there will not remove the tables for the modules themselves...
Depending on the pre you chose on install(default is cms_) the modules are listed in the cms_modules, but removing them from there will not remove the tables for the modules themselves...
Re: Modules have visible dependencies on deleted modules
Thanks, chaps.
Jos, I tried your suggestion of installing and de-installing the modules in question through ModuleManager, and thankfully this did the trick (it's no longer showing other modules as having dependencies). I'll mark the topic as fixed
I wonder though, if the ModuleManager method should be generally failsafe here, or is there something else I should do in conjunction, just to be safe? Such as using the 'Optimize/Repair tables' options in CMSMS, or their equivalent in the server control panel? Or should that not be necessary?
Thanks again guys.
Jos, I tried your suggestion of installing and de-installing the modules in question through ModuleManager, and thankfully this did the trick (it's no longer showing other modules as having dependencies). I'll mark the topic as fixed
I wonder though, if the ModuleManager method should be generally failsafe here, or is there something else I should do in conjunction, just to be safe? Such as using the 'Optimize/Repair tables' options in CMSMS, or their equivalent in the server control panel? Or should that not be necessary?
Thanks again guys.
