By zuessh on

hello, i just upgraded a test site to 5.3 and when i check the status report for the site it still shows the site at the 5.2 version. How can i verify that the 5.3 upgrade was successful? Thanks in advance.

⋅ Categories: Drupal 5.x

Comments

vm’s picture

vm commented

did you run update.php ?

if so it may just be a cache situation, you can clear cache tables in DB manuallly.
_____________________________________________________________________
My posts & comments are usually dripping with sarcasm.
If you ask nicely I'll give you a towel : )

zuessh’s picture

zuessh commented

Yes, I ran the update.php and it completed successfully. I'm not familiar with clearing cache tables. Can you provide assistance with that? Thanks

vm’s picture

vm commented

go into your DB using PHPmyadmin
check mark all cache tables
click the empty tab at the top of right pane (note: empty NOT drop)

or install the devel.module and use the clear cache buttons

or just wait until the cache regenerates on its own.

one can also try running cron.php

_____________________________________________________________________
My posts & comments are usually dripping with sarcasm.
If you ask nicely I'll give you a towel : )

zuessh’s picture

zuessh commented

I don't use phpmyadmin so option 1 is out. I don't have devel.module installed so that is out (for now). I ran cron.php and the site is still not showing an upgraded version. I don't mind waiting for cache to regenerate, as long as it doesn't take a very long time. Any idea how long it will take? Thanks again.

vm’s picture

vm commented

you must have some form of DB tool available to you.

no , I don't know how long it will take. is page cacheing set in your admin panel ? if so how long is it set for.

_____________________________________________________________________
My posts & comments are usually dripping with sarcasm.
If you ask nicely I'll give you a towel : )

zuessh’s picture

zuessh commented

I have direct access to the DB, but am not very good with mysql so i don't do much with the db directly. Can i clear the cache from the command line? Also from the performance section of administer --> site configuration cache is set to none.

vm’s picture

vm commented

I believe you can do it from the command line, however I am not command line savvy.

_____________________________________________________________________
My posts & comments are usually dripping with sarcasm.
If you ask nicely I'll give you a towel : )

zuessh’s picture

zuessh commented

maybe a quick download and install of an admin tool would be best. do you recommend myphpadmin or webmin?

vm’s picture

vm commented

I've only used phpmyadmin. I can't comment on the other option.

_____________________________________________________________________
My posts & comments are usually dripping with sarcasm.
If you ask nicely I'll give you a towel : )

gpk’s picture

gpk commented

Should you need to empty tables in the future, from the mysql prompt:

TRUNCATE TABLE cache

Repeat for the other cache tables. (The keyword TABLE is actually optional.)

However, I doubt the status report is cached since you must be logged in anyway to see it...

Did you check the VERSION near the top of system.module?

gpk
----
www.alexoria.co.uk

gpk
----
www.alexoria.co.uk

xmacinfo’s picture

xmacinfo
he/him
Primary language French
Location Canada
commented

The Drupal version values displayed in the Status Report screen is read from the system.module file.

Open the system.module file with a text editor. Near the top you should see the line:

define('VERSION', '5.3');

You might also consider installing the System Info module.

/*_*/
http://www.xmacinfo.com

dgraver’s picture

dgraver commented

I'm not sure if this is along the same lines, but I upgraded a couple modules, ran update.php, and they still show up as the older version. Would emptying the cache tables help this also?

gpk’s picture

gpk commented

Again the modules page shouldn't be cached.

A module's version is defined in its .info file and this is what is reported by the modules page.

gpk
----
www.alexoria.co.uk

gpk
----
www.alexoria.co.uk

dgraver’s picture

dgraver commented

When upgrading the module, I would create a copy of the original folder and name it module_name.sf for "safe". However, since if you do a 'ls' this comes after the original module name, drupal was overwriting the new version number with what was in the safe folder, hence why I was seeing the wrong version. Once I moved this 'safe' folder outside of the modules directory, everything was fine.

gpk’s picture

gpk commented

Glad to hear you solved the problem.

gpk
----
www.alexoria.co.uk

gpk
----
www.alexoria.co.uk

aviceda’s picture

aviceda commented

Wish I could solve mine, I upgraded from 5.3 to 5.5 and my Status Report says I'm using Drupal 5.5..... however the "Drupal core update status" claims "Not secure! (version 5.5 available)"

Ran "Update.php", replaced the "System" module and cleared Caches in DB.. still gives the same message.

Any ideas? All help appreciated.

www.aviceda.org

xmacinfo’s picture

xmacinfo
he/him
Primary language French
Location Canada
commented

Did you run cron? The update status script needs to run to fetch out version numbers. You can also manually start the Update Status Script.

/*_*/
http://www.xmacinfo.com