By redrider on
I just upgraded from Drupal 6.17 to 6.18 and then 6.19 and now the theme "Bluemarine is toast.
I have uploaded the new Bluemarine but I just get the WSOD and when I try to update the database, I get errors telling me Bluemarine isn't in the stream (whatever the heck that means)
The website, which is live by the way, will still display with Garland activated and without Bluemarine in the themes directory.
I'm sorry but Garland just doesn't do it for me - I need that theme back!
Please help as My alternative is not very appealing.
Comments
ok, I got Bluemarine back but
ok, I got Bluemarine back but I got this error updating the modules - how do I fix this?
"warning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, 'services_auth_access' was given in /home/*****/public_html/includes/menu.inc on line 452."
I really don't want to go back and reinstall 6.17 and import the old database
.:
Try running the Upgrade script, if you havnt done it yet.
------------
Volvo, Video, Velcro. (I came, I saw, I stuck around.)
And where exactly does this
And where exactly does this "Upgrade script" reside?
Have you read the upgrade
Have you read the upgrade instructions at http://drupal.org/node/390448
See stage 3, point 3.
The update script is a very
The update script is a very important part of the update process. Typically, it will make any necessary changes in the databases and clear caches. It's certainly possible (although not certain) that your original problem was caused because you hadn't run the update script.
I understand about update.php
I understand about update.php but I've never heard of an "upgrade" script
I did all that - this was a
I did all that - this was a minor upgrade - I shouldn't be having these issues
I'm sorry but stripping my
I'm sorry but stripping my server down is not an acceptable option
This has nothing to do with
This has nothing to do with the theme.
It seems that you updated/changed/removed services.module so that the menu system doesn't find it anymore. As others have said, running update.php should fix this.
Try clearing the menu cache
Sounds like it may be a bad entry in the menu router. If you've run update.php, try clearing the menu cache.
If not, you may wish to temporarily disable the services module and see if that helps.
In general, it's wise to test the upgrade on a non-live site before making it on your live one.
I ran update.php a few times
I ran update.php a few times now and still no joy.
I needed to update the services module after the upgrade.
Website crashed, database
Website crashed, database corrupt update failed - screw this, I'm going back to 6.17 until this upgrade and related modules are ready for prime time
stream
Do you still have the original error message? Sounds like the webserver is no longer able to read (include) certain files.