Closed (cannot reproduce)
Project:
Twitter
Version:
7.x-3.x-dev
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
4 Dec 2011 at 23:09 UTC
Updated:
21 Mar 2013 at 08:32 UTC
Jump to comment: Most recent file
Comments
Comment #1
JGO commentedUnfortunately experiencing the same error with beta 4 :(
Anyone knows a solution for this ?
Comment #2
Bartox commentedHaving the same issue with beta 4.
Comment #3
walthy commentedFirst Drupal post for me! :-)
Quick and dirty fix that seem to work for me: In file "twitter_views_field_handlers.inc", right after the first line "<?php" enter a new line "module_load_include('lib.php', 'twitter');"
Maybe the problem was somewhere in patch: http://drupal.org/files/twitter_remove_includes.patch
Regards,
Walter
Comment #4
Bartox commentedIt worked. Thanks
Comment #5
Millibit commentedThis worked for me as well... guess we wait 'til the next update for the fix?
Comment #6
johnalbinA fatal PHP error is a critical bug.
Here's the issue that caused the bug: #1346780: Code clean up: remove unneeded includes
Comment #7
babbage commentedI encountered this same issue in upgrading to 6.x-3.0-beta9 from 6.x-2.6 of this module. It was particularly nasty because in my dev/staging site, on the same server, I ran the update and everything was still working fine. I therefore pushed the update to my bare git repo, which automatically checks it out to the live site. I ran the database updates on the live site but wham! WSOD. Definitely running the same code. Checked again and the staging site ticking over fine still, but live site WSOD. Not sure what made the difference between the update on one vs. migration then update for the other, but there it is.
Turning on errors in the index.php, got the error message above. Disabling the Twitter module fixed the problem.
Edit: Sidegrading to the much newer 6.x-dev fixed the issue. It would be good to have a new 6.x official release, as I prefer not to be on the -dev branch for sites where I can avoid it.
Comment #8
juampynr commentedCan anybody provide steps to reproduce this issue?
Comment #9
13rac1 commentedPlease reopen to provide steps to reproduce.
Comment #10
alexgreyhead commentedThis just happened to me in the upgrade from 7.x-5.4 to 7.x-5.6. Steps to reproduce:
1) Update the code (see the diff attached)
2) Don't clear caches/run "drush cc all"
3) Try to visit a page which uses Twitter
4) The fatal PHP error "class 'TwitterUser' not found" should occur.
Alex