I'm using Drupal 6.22, PHP 5.2.17 and MySQL 5.0.91 hosted on a 1&1 server. I previously had installed version 6.x-3.0-beta4 of the Twitter module and today I attempted to update it to version 6.x-3.0-beta5.

Here's what I did (in detail):
1. Took site offline.
2. Deleted sites/all/modules/twitter directory, containing version 6.x-3.0-beta4.
3. Unpacked version 6.x-3.0-beta5 tarball to create new sites/all/modules/twitter directory.
4. Executed update.php script on site.

At step 4, I received two warnings:

1. array_merge() [function.array-merge]: Argument #2 is not an array in [my site's home directory]/update.php on line 173.
2. Invalid argument supplied for foreach() in [my site's home directory]/update.php on line 337.

I'm guessing that this update might have left my twitter module in an unstable state. Suggestions?

Comments

HindsightConsulting’s picture

Whoops! Forgot that the HTML tags in the first warning would be treated specially - it should read:

1. array_merge() [<a href='function.array-merge'>function.array-merge</a>]: Argument #2 is not an array in [my site's home directory]/htdocs/update.php on line 173.

evelien’s picture

+subscribe

nemsis’s picture

Same problem on install and site is no longer posting to Twitter.
I really don't want to step back to beta4 but I don't know what else to do.

michaek’s picture

I think the thing to do is to step back to beta4 if beta5 isn't working. It could be that the patch that claims to support the OAuth module version 3 doesn't do so in an appropriate manner. I tested it on PHP 5.3, but there seem to be other concerns about PHP 5.2.

stg11’s picture

My site started malfunctioning when I installed beta5. Main menu and node content on pages disappeared. Returned to normal when I disabled the module. May be due to insufficient memory, not sure.

sgrifenhagen’s picture

sorry. posted in wrong place.

juampynr’s picture

Status: Active » Fixed

Fixed: http://drupalcode.org/project/twitter.git/commitdiff/7ec6234bf3693f7df9d...

Beta 5 upgraded to Oauth 6.x-3.x, but the implementation has bugs so I reverted it. For the moment it will keep on using Oauth 6.x-2.02 (as described in the project's homepage).

Please download since tomorrow the dev release or wait until next week for the next beta (it will be 6.x-3.0-beta-8).

Cheers

PD: HindsightConsulting: your module was not in an unstable state, but there were just bugs on beta-5.

Status: Fixed » Closed (fixed)

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