Apologies for bringing this back to the top with a new post, but I hoped an updated subject might throw some more light. I'm desperate to jump on the 4.6 bandwagon, but I really need a leg up! I'm proper stuck at the moment - my back-up database is not being recognised by phpmyadmin - 1and1 (hosting support) think it has been corrupted ... so unless that can be sorted out, I cannot get back to square one and try the upgrade again!
The problem:
upgraded from 4.5.2 (fully working) to 4.6.0 as per http://drupal.org/node/20650 instructions. I chose the 'upgrade from 4.5.0' option and it logged OK. I saw the admin page - or rather just the admin log table - there were no top or side bar menus, and therefore no way to get into the site admin pages. The breadcrumb link to Homepage worked, but the same absense of menus left me with only the two node-teasers as content. Htmlsource shows reference to misc/drupal.css but no theme formatting. The content is enclosed within a table, but there's only one table cell on the whole page. The links from node teasers - to taxonomy/term/201, read more, etc - caused error 500.
You can see for yourself at http://www.driffieldnavigation.com
1: htaccess: changed to "rewriteEngine off". I'm no longer receiving errors 500, 404 and 403, but still not seeing the top or side bar menus. links seem to default back to the home page - I'm getting no error msgs from the browser (Firefox). The '1 comment' link returns the following from drupal (I think):
300 Multiple Choices: The document name you requested (/index.html) could not be found on this server. However, we found documents with names similar to the one you requested.
Available documents:
* /index.php (common basename)
Please consider informing the owner of the referring page about the broken link.
2: file permissions are all still set to 644 -rw-r--r-- ie none have executable permissions. This is normal I think. I did have trouble with file access permissions when uploading to the server: the FTP client couldn't open the unzipped drupal 4.6.0 folder, so I just uploaded it as was and renamed it on the server. I the discovered that .htaccess is sensitive to binary uploads so I refreshed all the drupal files with an ASCII upload. That went smoothly, though didn't help. Could this still be affecting the permissions system?
3: I didn't switch off 3rd party modules before the upgrade, and this has been mentioned by some installers ... if this could be the problem I will have to edit the db by hand :( - does anyone know where I can find a list of the 'required' modules for 4.6.0 so I can check off the right ones? As I said, my back-up db isn't working so I don't want to mess up the nearly-working db any more!
please help!
Comments
ohh I feel so stupid! ... custom theme!
It took me a week to figure this out, and I think I've aged about 6 months!
The db was still looking for a custom theme for the 4.5.2 version. Of course it couldn't find it in the 4.6.0 themes folder, so rather than defaulting to bluemarine, or something, it just showed no theme! - no sidebars, no menus, no admin links ...
the moral is very simple:
before upgrading, when you're switching off your 3rd party modules, etc, switch your theme to a default theme such as bluemarine.
I hope someone else finds this useful. I'll feel very very stupid if I'm the only one who made this mistake!
Thanks. That help me avoid
Thanks. That help me avoid the same problem.
you are most welcome
thank you for giving meaning to my suffering :)
check this
I had an outline already, but I made sure to add your experiances and just added this to the handbook. Let me know if I missed anything.
http://drupal.org/node/29161
-sp
---------
Drupal Best Practices Guide - My stuff Black Mountain
-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide
upgrade guidlines
great stuff.
If I remember right, the 'theme settings' are actually stored on the database, as are the module settings ...
It might be helpful to switch theme & module etc settings to 'default' BEFORE you create the back-up. That way, it saves you forgetting/ having to go through all the settings should you have to restore the DB and re-try the upgrade.