Page 1 of 1
Removing a CMSms module
Posted: Sun Mar 18, 2012 10:19 pm
by bryanhiggs
We're running CMSms 1.8.2.
I just tried to install the CGBlog (1.8.1) module using an XML install. However, it tells me:
"Minimum CMSMS Version Required: 1.9.4.1
Not Installed"
So, I tried doing an XML install on an earlier version number (CGBlog 1.6.3), not checking the "Overwrite existing modules" checkbox, but it told me:
"Module already installed"
even though it says in the list of modules that it's not installed.
I tried the XML install again, while checking the "Overwrite existing modules" checkbox.. This time, it gives me:
"Installing this module would result in a downgrade. Operation aborted"
I've even tried using FTP to delete the CGBlog sub-directory in the modules directory for our site, but it didn't help.
Can anyone help me get out of this apparently Catch-22 situation, and install the appropriate version of CGBlog?
It would be much appreciated!
Thanks!
Re: Removing a CMSms module
Posted: Mon Mar 19, 2012 1:15 am
by applejack
Try installing the next version up of CGBlog from the one you have then the next ones up to the latest version which your version of CMS can take. You may have to upgrade any dependencies before.
If that fails upgrade CMS to 1.9 and try again for each version of CGBlog.
After that upgrade to 1.9.4.3 one version at a time then update all modules.
There was an issue with missing out some version of CGBlog in that if you missed one it would fail to update all the table columns.
Re: Removing a CMSms module
Posted: Mon Mar 19, 2012 1:36 pm
by bryanhiggs
Thanks for your advice.
Unfortunately, I don't think it makes sense regarding the versions of CGBlog. As I said in the post, the version of CGBlog that is present in the list (but 'not installed') is already beyond what our version of CMSms supports. The problem is installing a lower version of CGBlog that it does support.
Upgrading to CMSms 1.9+ is too much on the risky side at this point. We have to be very careful not to mess up our (live) web site. That would have to be agreed upon by others in our Web site committee, and this probably wouldn't constitute sufficient cause.
Any other suggestions would be very much welcomed.
Re: Removing a CMSms module
Posted: Mon Mar 19, 2012 2:29 pm
by applejack
In module manager you can set the preferences to show either just the latest compatible version or all versions.
Check the folder permissions and ownership of the modules directory.
Re: Removing a CMSms module
Posted: Mon Mar 19, 2012 2:53 pm
by bryanhiggs
Well, I wasn't using Module Manager, but I went into Module Manager, and took a look. It showed me, in the Available Modules tab, CGBlog 1.6.3, so I clicked the "Download and Install" link for it, and here's what I received in response:
Code: Select all
Fatal error: Uncaught exception 'Exception' with message 'Instance of cms_filecache_driver already exists' in /home/uucm_admin/uucm.org/modules/CGExtensions/lib/class.cms_filecache_driver.php:18 Stack trace: #0 /home/uucm_admin/uucm.org/modules/CGExtensions/CGExtensions.module.php(77): cms_filecache_driver->__construct(Array) #1 /home/uucm_admin/uucm.org/lib/classes/class.moduleloader.inc.php(83): CGExtensions->__construct() #2 /home/uucm_admin/uucm.org/modules/ModuleManager/ModuleManager.module.php(1538): ModuleLoader->LoadModules(true) #3 /home/uucm_admin/uucm.org/modules/ModuleManager/ModuleManager.module.php(1124): ModuleManager->_GetInstalledModules(true, true) #4 /home/uucm_admin/uucm.org/modules/ModuleManager/ModuleManager.module.php(1181): ModuleManager->_DetermineUnfulfilledDependencies(Array) #5 /home/uucm_admin/uucm.org/modules/ModuleManager/ModuleManager.module.php(316): ModuleManager->_DoRecursiveInstall('m1_', Array, '') #6 /home/uucm_admin/uucm.org/lib/classes/class.module.inc.php(2069): ModuleManager->DoAc in /home/uucm_admin/uucm.org/modules/CGExtensions/lib/class.cms_filecache_driver.php on line 18
Any idea what this might indicate? (I taught Computer Science and worked in the computer industry for 30 years or so, so this stack trace doesn't scare me; it just doesn't shed much light, at least to me.)
RE: modules folder ownership and permissions, I have managed to install other modules using the XML installation process. It's not clear to me why this would be any different for CGBlog.
Re: Removing a CMSms module
Posted: Mon Mar 19, 2012 3:01 pm
by bryanhiggs
FWIW, here are the entries for the modules directory:
rights: rwxr-xr-x
owner: uucm_admin (the owner of all the directories, as far as I can see)
Incidentally, the CGBlog subdirectory is back within the modules directory. I suspect that my attempt to install via Module Manager may have done this.
Re: Removing a CMSms module
Posted: Mon Mar 19, 2012 3:08 pm
by bryanhiggs
Also, I checked that our system satisfies the dependencies for CGBlog (CGExtensions and CGSimpleSmarty). The versions we have are later than the ones listed under the CGBlog 1.6.3 entry in Module Manager.
The Module Manager stack dump suggests to me that we may have some kind of configuration problem, but I have no clue what it might be, nor how to find it from the available evidence.
Re: Removing a CMSms module
Posted: Mon Mar 19, 2012 3:24 pm
by Jo Morg
bryanhiggs wrote:So, I tried doing an XML install on an earlier version number (CGBlog 1.6.3), not checking the "Overwrite existing modules" checkbox, but it told me:
"Module already installed"
This means that CGBlog has a few entries in the DB.
You won't be able to solve this without finding and deleting these entries manually.
If you have access and are comfortable using PHPMyAdmin:
- backup db (of course);
- find every cms_module_cgblog entry and delete it (cms_module_cgblog*);
- find cms_modules table and delete the CGBlog entry;
Delete the CGBlog folder from the modules directory.
Install the CGBlog version you know will work with your cmsms version.
(Remember you don't usually get any support while using old cmsms versions, so upgrading is a MUST!)
Hope this helps.
Re: Removing a CMSms module
Posted: Mon Mar 19, 2012 3:41 pm
by bryanhiggs
Thanks, Jo.
I'll see what I can get done. Our lead CMSms person is not me, and he knows a lot more about CMSms than I do. I, knowing less, don't want to do anything destructive, of course.
He and I can probably figure out when we should move to the latest CMSms version -- without negatively impacting our site, of course!
Re: Removing a CMSms module
Posted: Mon Mar 19, 2012 6:28 pm
by Dr.CSS
Set up a site.com/subfolder copy site folders/files to it, export DB, make new DB, import DB, point subfolder site config.php to new DB, add /subfolder to the paths in config.php and you should have a duplicate of original site where you can do upgrades etc. to see if anything goes sideways then fix them till you get what you need then reverse copy folders/files and import new DB to old, make sure you change paths back...