gh0zt

I have no idea which part of the system is responsible for failed payments but I am using the subscription plugin and the stripe plugin and it’s a subscription payment that failed.

I don’t understand why there isn’t a super simple “retry” button so when payments fail they can be retried quickly and easily without bothering the customer and without delays.

So not only is there no way to retry the payment but when the next payment is processed the system fails to add the previously failed payment.

This is unbelievable, you people need to get your act together, this is peoples livelihood’s you’re messing with and apparently you don’t care if it all goes wrong.

Get your act together, get a retry button for failed payments and make sure if there’s a failed payment you keep track of it because right now you don’t.

I fixed it by running the script below from:

/wp-content/uploads/group-avatars

find . -type f -name ‘*.jpg’ -print0 | while IFS= read -r -d ” f; do
mv — “$f” “${f%.jpg}.png”
done

Found a way to fix it but I don’t know how to quickly regenerate all the existing thumbnails. Does anyone know a quick way to regenerate all the thumbnails after fixing the php script below?

1. Locate this file
/wp-content/plugins/buddypress/bp-core/bp-core-avatars.php

2. Locate this code in the file

// Set the full and thumb filenames
$full_filename = wp_hash( $original_file . time() ) . ‘-bpfull.jpg’;
$thumb_filename = wp_hash( $original_file . time() ) . ‘-bpthumb.jpg’;

3. Change the code to:

// Set the full and thumb filenames
$full_filename = wp_hash( $original_file . time() ) . ‘-bpfull.png’;
$thumb_filename = wp_hash( $original_file . time() ) . ‘-bpthumb.png’;

4. Uploading a new avatar and cropping it will now create a .png version, the images will now work properly in IE8/9

5. How can I recreate all the existing thumbnails quickly?

Activated successfully, no errors reported.

Thats great thank you Steven, Ill be testing it further over the next few hours and will let you know if any problems.

Thanks again for resolving this quickly, looking forward to implementing it.

After some more testing it seems the CPU issue is a generic Amazon EC2 “feature” called CPU steal, it happens when a process is consuming more than the allocated CPU cycles.

Anyway, happy to help and I look forward to the update and will test it once again once available.

[Wed Dec 28 01:37:32 2011] [error] [client 127.0.0.1] PHP Warning: readdir() expects parameter 1 to be resource, boolean given in /var/www/web/web.com/wp-content/plugins/connections/includes/class.template.php on line 113, referer: https://web.com/wp-admin/plugins.php

I just checked my Apache logs, as soon as I click activate plugin the logs are flooded continuously with this error message.

I uploaded the plugin, clicked activate and got this exact error after about 2-3 minutes:

“Plugin could not be activated because it triggered a fatal error.”

I ran the top command on my linux server and when I try to activate the plugin the CPU is sitting at 99%,

I checked the database and it looks like a whole load of tables have been created, so something is happening but the install never completes.

Hmm I just did same thing as karl19. Might be worth actually mentioning BP needs to be installed.

I jumped ahead to this plugin before installing BP because I wanted to see if my theme would be compatible.

Seems to be a problem with a lot of other membership plugins too.

Jeff do you think this is something that can be fixed / made to work or is it just impossible given the way multisite works?

Fastest way to do this is edit the database directly, it’s really quite simple. Make a backup first.

It redirects them to a login. Doesn’t behave like primary domain.

It also has a login but there is still a widget for that, why not include registration and make it look good instead of using the built in ugliness.

Did you find an alternative?

I spent ages trying to get the specific “Google XML Sitemaps” plugin working with multisite and failed miserably.

This XML sitemap feature of this plugin however worked without any fuss at all.

Thank you Yoast!