After installing Twitter 6.x-3.0-beta9, whenever a page is saved with the 'Announce this post on Twitter' checkbox selected, Drupal presents a completely blank white screen. The page is saved properly, but there is no tweet posted. There are no error messages in the Drupal log file or on the server logs. I have the current versions Drupal (6.25) Oauth (6.x-3.0-beta4) and all other installed modules.

I tried uninstalling and reinstalling the Twitter module, to no effect. Reinstalling 6.x-3.0-beta8 fixed the problem. I couldn't find any similar issue, so perhaps I'm the only person to experience this -- or just the first to write up an issue.

Comments

juampynr’s picture

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

There may be a PHP error and you have display_errors=Off on your php.ini.

Please see if you can find the error by activating this setting or see if you find it in the Apache error log.

dwhutton’s picture

dwhutton commented
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

Reinstalled beta9 with no problems.
No idea what the cause was. False alarm!

dwhutton’s picture

dwhutton commented
Status: Closed (cannot reproduce) » Active

Problem recurred, this time with an on-screen error message:
Fatal error: Cannot redeclare class OAuthConsumer in /mysite/public_html/sites/all/modules/oauth/oauth.lib.php on line 19

I don't know for sure that this is related but cron also began to fail with a timeout message in the error log.

After falling back to beta9 both problems disappeared again.

steinmb’s picture

steinmb commented

What version of oauth are you running? Make sure that you don't have old oauth lib. located in /mysite/public_html/sites/all/library

juampynr’s picture

juampynr commented
Status: Active » Closed (cannot reproduce)

Closing. There was no further feedback.

dwhutton’s picture

dwhutton commented

For anyone experiencing this problem, in my case I traced it to intermingling of files from different versions of Oauth. The problem was fixed by starting with a new Oauth directory -- instead of copying the files from the new version of Oauth into the existing directory, which is how I had performed the update previously.