kshade

I’ve solved the issue by editing bp-disable-activation.php. Add this to line 8 (BEFORE $wpdb->query( $wpdb->prepare( “UPDATE $wpdb->users SET user_status = 0 WHERE ID = %d”, $user_id ) );):

$activation_key = get_user_meta($user_id, 'activation_key', true);
$activate = apply_filters('bp_core_activate_account', bp_core_activate_signup($activation_key));

I just want to say that I’ve got the same problem after updating to WordPress 3.9.1 (from 3.8.something). Guess WordPress changed the way activation works? The original plug-in has the same issue, all new users

Yes, we’ve got a lot of users, and disabling that seems to have done the trick. Thanks for the help!

I’ve enabled slowlog in php-fpm (because it is slow… before it runs out of memory, also I couldn’t get xdebug to work). Maybe this helps:

[07-Nov-2013 00:26:00]  [pool www] pid 11168
script_filename = /srv/www/wordpress/index.php
[0x0000033ce6a33448] mysql_query() /srv/www/wordpress/wp-includes/wp-db.php:1205
[0x0000033ce6a332d8] query() /srv/www/wordpress/wp-includes/wp-db.php:1530
[0x0000033ce6a330a0] get_results() /srv/www/wordpress/wp-includes/meta.php:563
[0x0000033ce6a32f08] update_meta_cache() /srv/www/wordpress/wp-includes/meta.php:287
[0x0000033ce6a32dd0] get_metadata() /srv/www/wordpress/wp-includes/user.php:859
[0x0000033ce6a32cd0] get_user_meta() /srv/www/wordpress/wp-includes/capabilities.php:719
[0x0000033ce6a32bb0] _init_caps() /srv/www/wordpress/wp-includes/capabilities.php:984
[0x0000033ce6a32aa0] for_blog() /srv/www/wordpress/wp-includes/capabilities.php:521
[0x0000033ce6a32948] init() /srv/www/wordpress/wp-includes/capabilities.php:493
[0x0000033ce6a32798] __construct() /srv/www/wordpress/wp-includes/user.php:587
[0x0000033ce6a32660] query() /srv/www/wordpress/wp-includes/user.php:385
[0x0000033ce6a32550] __construct() /srv/www/wordpress/wp-includes/user.php:689
[0x0000033ce6a323b8] get_users() /srv/www/wordpress/wp-content/plugins/amazon-link/amazon.php:896
[0x0000033ce6a321f0] get_channels() /srv/www/wordpress/wp-content/plugins/amazon-link/amazon.php:983
[0x0000033ce6a320b0] get_channel() /srv/www/wordpress/wp-content/plugins/amazon-link/amazon.php:1235
[0x0000033ce6a31e90] get_local_info() /srv/www/wordpress/wp-content/plugins/amazon-link/amazon.php:1791
[0x0000033ce6a31cd8] make_links() /srv/www/wordpress/wp-content/plugins/amazon-link/amazon.php:1310
[0x000003e9c88379c0] shortcode_expand() unknown:0
[0x0000033ce6a31b28] preg_replace_callback() /srv/www/wordpress/wp-content/plugins/amazon-link/amazon.php:1270
[0x000003e9c8838050] content_filter() unknown:0

Just to check, enabling the plugin but _not_ putting an ASIN in the page will display fine, but as soon as one simple shortcode is added it fails?

Yup!

Disabling these does not solve the issue, sadly. We are running a bunch of plug-ins, including WangGuard, Quick Cache, s2member, buddypress and bbpress.

Installing the database takes a long time and ultimately times out (white settings page). Going to the templates menu also takes a lot longer than it should. I can’t see any more specific errors about these things though.

I “fixed” it by installing Really Simple Twitter Feed Widget instead. It’s not quite as nice though.

The plug-in uses version 1.0 of the Twitter API, which Twitter killed off a couple days ago.