Updates not sticking
Sat, 27/03/2010 - 10:53
I've tried upgrading from version 0.25 to 0.31, but after I run update.php, it's not recognizing the updates to Drupal (6.14), Pathauto (6x-1.2), and Views (6.x-2.6). Every other module seems to be upgraded fine.
I did get the error message that happens regarding the Locale module, but it's not enabled on our site.
If there's any other information anyone needs, just let me know. Thanks.
Mon, 29/03/2010 - 21:42
#2
Sorry. When I go to the
Sorry. When I go to the status report, it shows that I have updates to Drupal, Pathauto, and Views, even though I have done a full replace of the source code from 0.25 to 0.31.
It's saying that the current version of Drupal is 6.14, Pathauto is 6x-1.2, and Views is 6x-2.6.
Tue, 30/03/2010 - 12:09
#3
...
Hi,
> When I go to the status report, it shows that I have updates to
I presume you mean .../admin/reports/updates on your site.
Can you tell me what the reported version number for ProsePoint is?
Can you post me the first 10 lines of the file .../CHANGELOG.txt on your site?
My suspicion at the moment is that something wasn't quite correct when you did the upgrade ie. maybe some files didn't get copied/moved over correctly or something.
Can you also see if you have a .../sites/default/modules directory, and inform me of the contents?
You might have old modules lying around in there ... although that wouldn't explain why drupal is being reported at 6.14 since drupal isn't a module.
Wed, 31/03/2010 - 05:02
#4
The reported version of
The reported version of ProsePoint is 0.31
Here are the first few lines of CHANGELOG.txt:
// $Id: CHANGELOG.txt,v 1.253.2.37 2010/03/04 00:15:28 goba Exp $
Drupal 6.16, 2010-03-03
----------------------
- Fixed security issues (Installation cross site scripting, Open redirection,
Locale module cross site scripting, Blocked user session regeneration),
see SA-CORE-2010-001.
- Better support for updated jQuery versions.
- Reduced resource usage of update.module.
- Fixed several issues relating to support of install profiles and
distributions.
- Added a locking framework to avoid data corruption on long operations.
- Fixed a variety of other bugs.
There are a bunch of folders in my sites/all/modules directory, but I do not have a sites/default/modules directory. Here's what's in my sites/all/modules directory:
admin_menu, cck, composite, content_taxonomy, date, drupal-6.14, filefield, filefield 2, imagecache, imagecache 2, imagefield, insert_view, submitagain, token, views, workflow
Thu, 01/04/2010 - 12:03
#5
...
Some of the extra modules in your sites/all/modules directory are definitely a problem. Whether it's the only cause of your problem is not yet clear.
Firstly, you definitely should not have a drupal-6.14 directory in there. This will cause ProsePoint to auto-discover it and think it's a module.
Secondly, you shouldn't have old versions of modules in that directory. ProsePoint auto-scans the entire tree from sites/all/modules and sites/default/modules downwards and if there is more than one version of a module in those locations, it may pick the wrong or older one.
So please go through sites/all/modules and prune out stuff that you don't need, and see whether your issue still persists.
Fri, 02/04/2010 - 00:55
#6
Thanks for your help, beng.
Thanks for your help, beng. I realize the problem now, but there's not much I can do about it, I fear.
The update script did pick up the Drupal 6.14 installation, and when I tried deleting it the site crashed for obvious reasons. I don't have a good database backup, so things are uncertain at this point. Mucking around in the database is beyond my abilities.
Thanks again.
Tue, 06/04/2010 - 09:33
#7
...
Hi,
Hmmm ... setting aside how your site got to this state ...
If you don't get this fixed, I think you will run into more problems sooner or later. It is quite important that update.php works correctly, and if it sees incorrect versions, then important updates may be missed.
Depending on what you're using the site for, and how important it is, you may be interested in getting me to have a deep look and untangle it for you. Please send a message through the Contact form if so.
Thank you.
Thu, 17/06/2010 - 02:59
#8
Was this issue solved? I have
Was this issue solved? I have the same problem on my site.
Mine first showed up two updates ago. I've done a full upgrade since then and it didn't help.
Thu, 17/06/2010 - 03:07
#9
Yes, this issue was solved.
Yes, this issue was solved. One of the other maintainers of the site untangled the Drupal installation from the ProsePoint one. Not much else I can tell you, I'm afraid.
Hi,
Sorry, I don't quite understand what you mean by 'not recognizing the updates'. Do you mean when you view .../admin/build/modules on your site, there are incorrect versions? Or do you mean update.php is still reporting that updates are available? Or something else?