Greetings, I've not removed any modules in awhile, so maybe something has changed in the last few versions. However, when I disable, (possibly) uninstall, and then delete the /www/sites/all/modules/XX module folder, in 5.7, the module is not being removed from the list at /admin/build/modules. In some cases, the modules are marked "(missing)" in red, in other case not. Regardless, they're not going away, but in my memory they should be. Any thoughts on what I might do to completely remove modules? Brian
Have you tried removing all instances of the module through phpmyadmin? That's what I usually do when uninstall fails. Do a backup first though! ;) cheers Morten tir, 22 04 2008 kl. 06:58 -0600, skrev Brian Choc:
Greetings,
I've not removed any modules in awhile, so maybe something has changed in the last few versions. However, when I disable, (possibly) uninstall, and then delete the /www/sites/all/modules/XX module folder, in 5.7, the module is not being removed from the list at /admin/build/modules. In some cases, the modules are marked "(missing)" in red, in other case not. Regardless, they're not going away, but in my memory they should be.
Any thoughts on what I might do to completely remove modules?
Brian
I just noticed something a bit weird(er) that feels correlated, to me. The Update Status module is not acknowledging updates. So, even though I have updated to 2.2 of Pathauto, for instance, it is still telling me I am running the previous version and that I need to update to 2.2. Before I start yanking things out of the DB by hand, I thought I'd ask if anyone else has faced anything similar or has ideas? Changes in removals of modules are simply not registering. Brian Morten Holmstrup wrote:
Have you tried removing all instances of the module through phpmyadmin? That's what I usually do when uninstall fails.
Do a backup first though! ;)
cheers Morten
tir, 22 04 2008 kl. 06:58 -0600, skrev Brian Choc:
Greetings,
I've not removed any modules in awhile, so maybe something has changed in the last few versions. However, when I disable, (possibly) uninstall, and then delete the /www/sites/all/modules/XX module folder, in 5.7, the module is not being removed from the list at /admin/build/modules. In some cases, the modules are marked "(missing)" in red, in other case not. Regardless, they're not going away, but in my memory they should be.
Any thoughts on what I might do to completely remove modules?
Brian
Quoting Brian Choc <bchoc@t4tcolorado.org>:
I just noticed something a bit weird(er) that feels correlated, to me. The Update Status module is not acknowledging updates. So, even though I have updated to 2.2 of Pathauto, for instance, it is still telling me I am running the previous version and that I need to update to 2.2.
Before I start yanking things out of the DB by hand, I thought I'd ask if anyone else has faced anything similar or has ideas? Changes in removals of modules are simply not registering.
What does "SELECT system.schema_version FROM system WHERE name = 'pathauto';" return? Looking at the difference of pathauto.install from CVS it appears to not be in line with the documented usage of hook_install[1] and hook_update_N[2]. Open a support or bug request as appropriate with pathauto[3]. [1] http://api.drupal.org/api/function/hook_install/5 [2] http://api.drupal.org/api/function/hook_update_N/5 [3] http://drupal.org/node/add/project_issue/pathauto Earnie -- http://for-my-kids.com/ -- http://give-me-an-offer.com/
On Wed, Apr 30, 2008 at 8:35 AM, Earnie Boyd <earnie@users.sourceforge.net> wrote:
Quoting Brian Choc <bchoc@t4tcolorado.org>:
I just noticed something a bit weird(er) that feels correlated, to me. The Update Status module is not acknowledging updates. So, even though I have updated to 2.2 of Pathauto, for instance, it is still telling me I am running the previous version and that I need to update to 2.2.
I just tried download 5.x-2.2 to a site (I usually run the 5.x-2.x-dev version...) and it worked fine for me, so I'm not sure this is a Pathauto problem per se.
Before I start yanking things out of the DB by hand, I thought I'd ask if anyone else has faced anything similar or has ideas? Changes in removals of modules are simply not registering.
What does "SELECT system.schema_version FROM system WHERE name = 'pathauto';" return? Looking at the difference of pathauto.install from CVS it appears to not be in line with the documented usage of hook_install[1] and hook_update_N[2]. Open a support or bug request as appropriate with pathauto[3].
Can you state the specific practice that is "not in line" in your opinion? I (re)read the documentation you linked to and don't see any problems. Answer here or in the issue queue. Thanks, Greg -- Greg Knaddison Denver, CO | http://knaddison.com World Spanish Tour | http://wanderlusting.org/user/greg
Quoting Greg Knaddison - GVS <Greg@GrowingVentureSolutions.com>:
What does "SELECT system.schema_version FROM system WHERE name = 'pathauto';" return? Looking at the difference of pathauto.install from CVS it appears to not be in line with the documented usage of hook_install[1] and hook_update_N[2]. Open a support or bug request as appropriate with pathauto[3].
Can you state the specific practice that is "not in line" in your opinion? I (re)read the documentation you linked to and don't see any problems.
Answer here or in the issue queue.
Sorry, I must have misread the pyview cvs diff. Checking 2.2 and 2.x-dev I see that my concern isn't there at all. We still need to know what the OP has for the schema_version. Earnie -- http://for-my-kids.com/ -- http://give-me-an-offer.com/
Earnie Boyd wrote:
Quoting Brian Choc <bchoc@t4tcolorado.org>:
I just noticed something a bit weird(er) that feels correlated, to me. The Update Status module is not acknowledging updates. So, even though I have updated to 2.2 of Pathauto, for instance, it is still telling me I am running the previous version and that I need to update to 2.2.
Before I start yanking things out of the DB by hand, I thought I'd ask if anyone else has faced anything similar or has ideas? Changes in removals of modules are simply not registering.
What does "SELECT system.schema_version FROM system WHERE name = 'pathauto';" return? Looking at the difference of pathauto.install from CVS it appears to not be in line with the documented usage of hook_install[1] and hook_update_N[2]. Open a support or bug request as appropriate with pathauto[3].
[1] http://api.drupal.org/api/function/hook_install/5 [2] http://api.drupal.org/api/function/hook_update_N/5 [3] http://drupal.org/node/add/project_issue/pathauto
Earnie -- http://for-my-kids.com/ -- http://give-me-an-offer.com/
I am happy to return this value. That query returns scheme_version of 6. That said, Pathauto was meant only, really, as an example; apologies if I did not make that clear enough. For another, I just this morning updated the Token module to 1.11, and Status Update still reports it as 1.10. Brian
Quoting Brian Choc <bchoc@t4tcolorado.org>:
I am happy to return this value. That query returns scheme_version of 6.
That said, Pathauto was meant only, really, as an example; apologies if I did not make that clear enough. For another, I just this morning updated the Token module to 1.11, and Status Update still reports it as 1.10.
It must be a cached value. Try truncating the cache and cache_* tables. Earnie -- http://for-my-kids.com/ -- http://give-me-an-offer.com/
Earnie Boyd schrieb:
Quoting Brian Choc <bchoc@t4tcolorado.org>:
I am happy to return this value. That query returns scheme_version of 6.
That said, Pathauto was meant only, really, as an example; apologies if I did not make that clear enough. For another, I just this morning updated the Token module to 1.11, and Status Update still reports it as 1.10.
I do have the same problem. I use a multisite installation Drupal 5.7 on a webhoster server. The modules are in ..example.com/sites/all/modules/ After uploading and (well, mostly redundant) update.php for several but not all modules the update is not recognized, on three sites. Among the failing modules: Printer Friendly Pages Image Assist Weather Last modules *succesfully* recognized (as reference example): i18n Comment RSS The problem lasts for several weeks already, this is the first time I do really look after it. Yes, I cleared the cache tables twice. I have no idea what goes wrong. Servus Franz -- http://amazonas.the-dot.de http://www.bifa-muenchen.de http://security-conference.de
On Sat, May 3, 2008 at 5:18 PM, Franz Iberl <f.iberl@amazonas-box.de> wrote:
Earnie Boyd schrieb:
Quoting Brian Choc <bchoc@t4tcolorado.org>:
I am happy to return this value. That query returns scheme_version of 6.
That said, Pathauto was meant only, really, as an example; apologies if I did not make that clear enough. For another, I just this morning updated the Token module to 1.11, and Status Update still reports it as 1.10.
I do have the same problem.
I use a multisite installation Drupal 5.7 on a webhoster server. The modules are in ..example.com/sites/all/modules/
After uploading and (well, mostly redundant) update.php for several but not all modules the update is not recognized, on three sites. Among the failing modules: Printer Friendly Pages Image Assist Weather
For a multisite, I would double-check the following: - That I have run update.php for each site separately, even if it does not seem to do any database updates. - That I don't have another copy of the module in sites/sitename/modules or in sites/default/modules, additionally to sites/all/modules.
Last modules *succesfully* recognized (as reference example): i18n Comment RSS
The problem lasts for several weeks already, this is the first time I do really look after it. Yes, I cleared the cache tables twice.
I have no idea what goes wrong.
Servus Franz
-- http://amazonas.the-dot.de http://www.bifa-muenchen.de http://security-conference.de
-- [ Drupal support list | http://lists.drupal.org/ ]
Cog Rusty schrieb:
On Sat, May 3, 2008 at 5:18 PM, Franz Iberl <f.iberl@amazonas-box.de> wrote:
[ ... module version updates not recognized]
I do have the same problem.
...
For a multisite, I would double-check the following: - That I have run update.php for each site separately, even if it does not seem to do any database updates.
yes, always done.
- That I don't have another copy of the module in sites/sitename/modules or in sites/default/modules, additionally to sites/all/modules.
there is no other/redundant file path. Thank you, but stil uncleared ... Servzs Franz
Earnie Boyd wrote:
Quoting Brian Choc <bchoc@t4tcolorado.org>:
I just noticed something a bit weird(er) that feels correlated, to me. The Update Status module is not acknowledging updates. So, even though I have updated to 2.2 of Pathauto, for instance, it is still telling me I am running the previous version and that I need to update to 2.2.
Before I start yanking things out of the DB by hand, I thought I'd ask if anyone else has faced anything similar or has ideas? Changes in removals of modules are simply not registering.
What does "SELECT system.schema_version FROM system WHERE name = 'pathauto';" return? Looking at the difference of pathauto.install from CVS it appears to not be in line with the documented usage of hook_install[1] and hook_update_N[2]. Open a support or bug request as appropriate with pathauto[3].
[1] http://api.drupal.org/api/function/hook_install/5 [2] http://api.drupal.org/api/function/hook_update_N/5 [3] http://drupal.org/node/add/project_issue/pathauto
Earnie -- http://for-my-kids.com/ -- http://give-me-an-offer.com/
I'm happy to return this value, if you think it will help. That query returns scheme_version of 6. That said, Pathauto was meant only, really, as an example; apologies if I did not make that clear enough. For another, I just this morning updated the Token module to 1.11, and Status Update still reports it as 1.10. Brian
participants (6)
-
Brian Choc -
Cog Rusty -
Earnie Boyd -
Franz Iberl -
Greg Knaddison - GVS -
Morten Holmstrup