Closed (fixed)
Project:
Views (for Drupal 7)
Version:
6.x-2.3
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
16 Feb 2009 at 14:27 UTC
Updated:
14 Jul 2009 at 22:50 UTC
After updating to 6.x-2.3 running update.php or clearing the cache causes blank page. Rolled back to 6.x-2.2. Memory limit 32M.
Comments
Comment #1
hankpalan.com commentedI updated to 6x-2.3 and came back with blank page. I'm running a server over at rackspace and have a massive amount of ram to play with. So I set the Memory Limit all the way up to 500mb and still had a blank page. I had to revert all the way back to 2.0-rc1 before views pages didn't come back blank.
Tried 2.3, 2.2, and 2.1 all with same results. For me rc1 is working.
Comment #2
merlinofchaos commentedI can't do much with just blank screen. Usually there's an error somewhere. Sometimes it's in the watchdog log, too.
Comment #3
hankpalan.com commentedI apologize for not providing more information. This is not the complete log, but the relative data minus duplicates.
Logs from server:
PHP Fatal error: Call to a member function clone_view() on a non-object in /var/www/html/sites/all/modules/views/views.module on line 343
PHP Fatal error: Call to undefined function link_views_content_field_data() in /var/www/html/sites/all/modules/link/link.module on line 148
PHP Fatal error: Class 'views_handler_field_node' not found in /var/www/html/sites/all/modules/cck/includes/content.views.inc on line 262
PHP Fatal error: Cannot redeclare class views_join in /var/www/html/sites/all/modules/views/includes/join.handlers.inc on line 56
Logs from Drupal:
The specialized Panels menu router rebuild failed. Some paths may not work correctly. (I'm assuming this is because views wasn't working in the panels that I had active)
These of course were repeated numerous times in the log just at different times.
The site as a whole wasn't affected by blank pages, just anything that had to do with views, so views pages, the views settings page, panel pages with views embedded, etc...
Comment #4
merlinofchaos commentedThat looks like you've got a broken install. This can happen if you install Views into a directory with an older Views without deleting what was already there. In particular this:
really suggests that there are files being mixed up.
Comment #5
hankpalan.com commentedI deleted the folder and re-uploaded version 2.3 still same blank page.
Here are the error logs for the event:
PHP Fatal error: view::destroy() [view.destroy]: The script tried to execute a method or access a property of an incomplete object. Please ensure that the class definition "views_plugin_display_default" of the object you are trying to operate on was loaded _before_ unserialize() gets called or provide a __autoload() function to load the class definition in /var/www/html/sites/all/modules/views/includes/view.inc on line 1460
PHP Fatal error: Call to undefined function link_views_content_field_data() in /var/www/html/sites/all/modules/link/link.module on line 148, referer: http://www.thebattalion.tv/update.php?op=results
PHP Fatal error: Call to a member function clone_view() on a non-object in /var/www/html/sites/all/modules/views/views.module on line 343
Comment #6
_shane_ commentedMaybe something with the way PHP handles classes?
The update worked fine for me on my test server which is running PHP version 5.2.8.
It fails on two different Drupal installs on a server running PHP version 5.1.2.
Comment #7
merlinofchaos commentedTry flushing the cache_views table as well.
Comment #8
merlinofchaos commentedAlso, your copy of link.module may need to be updated.
Comment #9
nerkn commentedI moved my site to production server and face the same problem.
[error] [client 85.104.138.208] PHP Fatal error: Call to a member function clone_view() on a non-object in /var/clients/client1/web1/web/sites/all/modules/views_2/views.module on line 343
I moved my all contributed modules to sites/all/modules, which were (plenty of them) was residing at modules of drupal.
The problem is big for me because I'd used the vies on the whole site, and cant access anywhere.
Comment #10
merlinofchaos commentedHmm. Try truncating cache_views?
Comment #11
nerkn commentedI upgraded my php version 5.1.6 to 5.2.6 every thing is ok/working now. God damn centos!I need to remove erroneous modules (traced from error.log) and installed one by one :'(
Comment #12
_shane_ commentedClearing the views cache from the views->tools prior to the upgrade solved my problem.
Comment #13
cbeny commentedI had the same error and I cleared the views cache after install and it wroked.
views->tools
Comment #14
sylvaticus commentedSame problem here.. blank update.php script after upgrading to 2.3.. I tried both disable/cleaning cache and removing all sites/all/modules/views/ files before extracting the new ones, but still failing.
Rolled back to v.2.2
FreeBSD, php5.2.9, php limit 64MB, mysql 5.0.77, no access on system log files.
Comment #15
shane birley commentedOne trigger of the blank screen seems to be very specific for me: changing the row style settings. Click on the change button and - boom - it just blanks and then reloads.
Comment #16
wadechristy commentedSame issue here. Going back to 2.2
Comment #17
ryan_courtnage commentedAfter updating to views 2.3, whenever I hit the admin/build/block page, the following error is generated:
Fatal error: view::destroy() [view.destroy]: The script tried to execute a method or access a property of an incomplete object. Please ensure that the class definition "views_plugin_display_default" of the object you are trying to operate on was loaded _before_ unserialize() gets called or provide a __autoload() function to load the class definition in /sites/all/modules/views/includes/view.inc on line 1414
If I clear truncate cache_views, i can visit the blocks admin once. Subsequent visits result in the same error.
Comment #18
merlinofchaos commentedryan_courtnage, I admonish you for putting an unrelated post in an issue that is clearly not about that. Thank you for wasting my time and the time of every submitter and the time of every future person who reads this issue and gets confused.
Please understand how to use an issue queue before you do. Thanks.
In fact, this issue seems to be polluted with people going "Hey I can post kind of similar issues" here, making it really difficult to follow the original poster's issue. I believe the original poster's issue is fixed, though other posters look to have some random probably unrelated issue that is causing problems. Unfortunately, this method of posting random crap on an issue doesn't do a thing for me in terms of being able to figure out what's wrong, so there's not much I can do. Original poster's issue fixed.
Comment #19
ryan_courtnage commented@merlinofchaos
I'm quite familiar with the issue queue, thank you.
AFAICT, my post is not "random crap". After experiencing a "Blank page after update to 6.x-2.3", I discover my error_log contained an error that is identical to the error in comment #5 (who's author you appeared to be having dialog with). I was only trying to help you determine what's wrong.
ok, I'm ready to admit my post was not helpful (and yes, can be considered random crap). I had similar symptoms to those reported here, but likely a completely different problem. Was corrupt/incomplete views files (I use a CVS checkout of Views, and 'cvs up' to 2.3 missed some changes).
Comment #20
merlinofchaos commentedThe blank page you experienced was only on admin/build/block (which actually is its own issue tho I think you've figured that out). That was the big difference.
Comment #21
ehr commentedsame issue here. update.php produce blank page still after upgrade from 6.x-2.2 to views version 6.x-2.5 and after clearing views-cache.
Comment #22
merlinofchaos commentedehr: The original issue was marked fixed. Please do not re-open the issue and provide no information. There's nothing I can do with that, and if you'd read the issue you'd know exactly what information is needed.