Help!
I have an old 5.23 site running on a web host who has just implemented an across-the-board upgrade to PHP 5.3. This has damaged - but not completely broken - the site. It still runs and I can adminster some content but a whole bunch of core and options modules cannot be administered - I get WSODs on the admin pages. Crucially, this applies to users (and quite a few other things).
I know that the site needs upgrading but there are some hand-rolled elements (a custom theme for instance) which have to be re-implemented. The site was originally commissioned from a web developer and changes of personnel are proving an obstacle to understanding the initial installation - let alone upgrading it. The host is unwilling or unable to downgrade the PHP installation.
I was getting a load of error messages relating to function ereg being deprecated. These have stopped (by dint of the web host changing the reporting settings), and now I'm getting errors like:
Parameter 2 to watchdog_user() expected to be a reference, value given in /home//public_html/includes/module.inc on line 386
So I am stuck - in the short term. Is there any short term fix I can apply which will restore admin capacity at least for the time it takes me to upgrade the site?
Thanks for any help you can offer
Paul
Comments
Unless someone else knows another way...
Unless someone else knows another way, line by line error fixing is the only way I know of to get out of this situation.
I know that's not what you wanted to hear, but I'm telling you straight so that you understand that the longer you wait the longer your site will be broken. There is no easy way to fix incompatible code except to fix it.
There is not going to be a
There is not going to be a quick band aid, there are a number of changes to PHP since Drupal 5 came out that are going to produce errors and problems.
Damn
Thanks for the comments. I was afraid that would be the case. Plan B then...
take a look
http://drupal.org/node/1016008