I got a weird problem when i am upgrading core from 6.8 to 6.9. I am following the following procedure:
1> Created a backup of the entrie "/" drupal install
2> Put the site into offline mode
3> Selected one of the generic themes
4> Disabled all the modules
5> backed up "sites" and "files"
6> Deleted the old files in "/" Drupal installation
7> Uploaded the new 6.9 and change file /sites/default/settings.php with mysql connection and allow to run update.
8> Restored the old "sites" and "files" folders into the new 6.9 folder "/sites/all" and "/sites/default"
9> Restored the old .htaccess
10> Ran Update.php
the site is running good, but it is still showing me i am runing under core 6.8, nor 6.9. I tried it couple of time, actually it's happening after i restore "modules" back into /sites/all/modules.
Guys, any idea?
Thanks
Comments
Comment #1
ainigma32 commentedAre you still experiencing this issue?
- Arie
Comment #2
khawkc commentedthe problem did not fix, but i rebuilt the site with new version anyway.
Comment #3
ainigma32 commentedYou could look at the .info files of the modules under /sites/all/modules/
If there are any core modules that are from version 6.8 then Drupal will claim it's still 6.8 in total.
Please post back if that is the case here.
- Arie
Comment #4
ainigma32 commentedLooks like khawkc won't be posting any feedback so I'm setting this to fixed.
Feel free to reopen if you think that is wrong.
- Arie
Comment #6
jonwiz commentedI have the same issue, upgrading from 6.8.
In fact I hadn't upgraded in a while and now I have an upgrade path from 6.8 - 6.12
I tried going directly to 6.12, but the available updates still still reported that I had 6.8 drupal core.
Now I'm trying to go step by step...6.9...6.11...etc
I keep getting strange errors when running update.php too
exampe:
Fatal error: Call to a member function get_access_callback() on a non-object in drupal/path/sites/all/modules/views/plugins/views_plugin_display_page.inc on line 78
Also my drupal frontpage is a blank white page, same with the modules administration section...white page
I was using a custom theme, but I reset to garland during updates
It may be because I recently put all contributed modules into sites/all/modules to make upgrading core easier...
Apparently drupal is still looking to include the modules in the modules/ directory, but I've moved them to sites/all/modules
before doing a drupal update
ahh help this upgrade process is painful
Comment #7
jonwiz commentedSince views was the module throwing the error, I disabled it through the database and now I can administer my modules properly.
When I enable views, I get the blank pages again. I'm making it through the upgrade process little by little.
Comment #8
walker2238 commentedexperiencing the same thing. ugh... manual labor, that sounds bad.