Upgrading Views 2.2 to 2.3 priduces a white screen when running update.php with the address bar showing update.php?op=info.
Memory has been increased to 256M with no effect. Running on XAMPP on XP. I've tried everything in http://drupal.org/node/158043 including making sure error reporting is on. Other modules update without problem (eg. calendar) when updated from exactly the same starting point, it's just the views update that's causing this. The watchdog doesn't show any errors, the apache error log doesn't show any errors, the only thing I have is the apache access log which shows:

127.0.0.1 - - [23/Feb/2009:17:19:39 +0000] "GET /update.php HTTP/1.1" 302 -
127.0.0.1 - - [23/Feb/2009:17:19:40 +0000] "GET /update.php?op=info HTTP/1.1" 500 -

which looks as though it relates but I'm not sure where to take it from there.

Comments

merlinofchaos’s picture

merlinofchaos commented

Strange. If the access_logs hows a 500,the error_log *should* show an error.

Without knowing some kind of error I'm not sure what we can do here. :/

3cwebdev’s picture

3cwebdev commented

I got the exact same problem on two sites. I've upgraded View to 2.3 on about 6 other sites without problem. However, on these two sites I get the write screen update.php?op=info. Reverting back to 2.2 allows me to run the update script.

The only similarity that I can find between the two sites is that they both use calendar and date, where my other sites do not.

Could there be some correlation to those modules causing the failure? As of right now I don't know any way to upgrade to Views 2.3.

Tony Sharpe’s picture

Tony Sharpe commented

Just confirming that I'm using Calendar and Date as well.

merlinofchaos’s picture

merlinofchaos commented
Title: White screen on upgrading views 2.2 to 2.3 » White screen on upgrading views 2.2 to 2.3 with date and/or calendar module

Updating title. May ultimately be a date/calendar issue.

karens’s picture

karens commented
Status: Active » Postponed (maintainer needs more info)

What version of Date and Calendar are being used? I think the last official release has gotten out of whack with Views. The -dev version is working well and I'm getting ready to roll a new release. If you were using rc6 instead of -dev, I think it might just be that.

3cwebdev’s picture

3cwebdev commented

I just upgraded to the newest -dev versions. Ran update.php and then tried to upgrade to Views 2.3. I had the same white screen result.

Perhaps this has nothing to do with date/calendar. It's just the only similarity between the sites that doesn't exist on all my other sites that were able to update views correctly.

I don't know if it would have any bearing, but I've been an early adopter of date/calendar and have gone through many, many dev updates.

Is it even possible that other modules would cause views to fail?

karens’s picture

karens commented

There must be some other factor here, I'm running the latest Views with no problems. There are no recent updates in Views, so what exactly was getting updated on update.php?

BAJV’s picture

BAJV commented

I've got the same error on upgrading views 2.2 to views 2.3. Now I revert back to views 2.2 for my production site.

I'm waiting for any solution to this problem.

zmove’s picture

zmove commented

I confirm the issue, I updated date module to the latest RC version. Then, views. After copying views files, I get a wsod. So I search in the issue queue and I fall to that issue.

I think I have the same problem. Latest Views + Latest Date module = WSOD

merlinofchaos’s picture

merlinofchaos commented

Does truncating the views cache prior to the upgrade affect this at all?

Tony Sharpe’s picture

Tony Sharpe commented

No, clearing all cahes including views object cache doesn't help.
I set display_errors to TRUE in update.php and got the following error:
Fatal error: Cannot redeclare date_api_views_data() (previously declared in C:\Program Files\xampp\htdocs\tr4\sites\all\modules\date\includes\date_api.views.inc:123) in C:\Program Files\xampp\htdocs\tr4\sites\all\modules\date\date_api.views.inc on line 60
I hacked in an if(!function_exists(.. to ignore the whole include file if the first function was already loaded, and this moved things on. I did the same with calendar/includes/calendar.views.inc and calendar/calendar.views.inc. At this point I realised that at least calendar had include files in 2 different locations, and having already had a problem with date having old code in it, I guessed this was an old code left behind problem.

Solution: Clear out date, calendar and views and re-copy in clean modules (of the same version). Check all is working then upgrade views. It worked for me.

karens’s picture

karens commented

Yes, if you had old date files floating around in the wrong places you would definitely get fatal errors. If others had the same problem, it is neither a Views bug nor a Date bug. It is probably a good idea any time you have fatal errors like these to at least try emptying out the folders of involved modules and upload the latest code to be sure you have nothing but the latest files in them (and also checking that you don't have more than one copy of a module in duplicate places).

wxman’s picture

wxman commented

I don't even use the calendar module, and this worked for me too. I just deleted the date and views folders, and replaced them with the same versions. Ran the db update, upgraded views to 2.3, ran it again, and it all works fine now.

3cwebdev’s picture

3cwebdev commented

Wahoo! Removing the old calendar and date module directories fixed the problem on both of my sites. Thanks!

karens’s picture

karens commented
Status: Postponed (maintainer needs more info) » Fixed

That's it then. Thanks for reporting back so we can close this issue.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.