Page 2 of 2

Re: Error code: 400

PostPosted: December 9th, 2011, 1:16 am
by drbyte
No luck Jason

1.jpg

2.jpg
2.jpg (99.54 KiB) Viewed 1910 times

3.jpg

4.jpg


That's all what is happening


Sam

Re: Error code: 400

PostPosted: December 9th, 2011, 1:21 am
by Jason Caldwell
Thanks for the follow-up Sam.
I'll check with beta testers on this issue and post updates as details become available.

Re: Error code: 400

PostPosted: December 9th, 2011, 1:33 am
by drbyte
OK Thank you

Re: Error code: 400

PostPosted: December 9th, 2011, 1:53 am
by Jason Caldwell
I have two others that were able to reproduce this. We'll have this corrected soon.

Re: Error code: 400

PostPosted: December 9th, 2011, 9:44 am
by Jason Caldwell
Looking for confirmation please.

I believe this issue has finally been corrected in the development copy of the s2Member Framework.
You can grab the latest development copy here: http://downloads.wordpress.org/plugin/s2member.zip

Changelog in this regard ...

1. Propagation issues with Origin Access Identities ( resolved, accounted for by s2Member ).

2. WordPress® function wp_remote_request() does NOT support HTTP method "DELETE" when using the cURL transport layer. Your server MUST have a php.ini file with allow_url_fopen=on in order for this to work as expected inside WordPress. cURL is fine for everything but "DELETE" operations. s2Member auto-resolves this issue, so long as allow_url_fopen=on in your php.ini file.

See also: viewtopic.php?f=36&t=2636
See also: viewtopic.php?f=36&t=247

@TODO: Create ticket at WordPress.org regarding the absence of support for "DELETE" in the cURL transport layer of the WP_Http_Curl{} class. This is really a WordPress® issue.

100% resolved in development copy

Re: Error code: 400

PostPosted: December 9th, 2011, 10:33 am
by drbyte
Jason......

"Amazon® CloudFront Distributions auto-configured successfully. Please allow 30 minutes for propagation"

Perfect :D

Created the ClodFront distribution (streaming/downloading), Bucket policy and the crossdomain.xml file

I tested it twice. It works

Thank you so much for spending time on this. Awesome Job

Sam

Re: Error code: 400

PostPosted: December 9th, 2011, 10:51 am
by Jason Caldwell
Thanks for the confirmation Sam. You're very welcome.
~ Sorry it took us so long to come to this conclusion.

100% resolved in development copy

Re: Error code: 400

PostPosted: December 21st, 2011, 9:58 am
by govpatel
I have been having same same problem getting 400
Unable to auto-configure Amazon® CloudFront Distributions.
Error code: 400. Error Message: Unable to delete existing Amazon® CloudFront Downloads Distro. Unable to delete existing Amazon® CloudFront Distro. Bad Request

I have download the from link that Jason Caldwell posted and replaced S2member plugin files in plugins folder and am still getting same error.

I have multisite setup but I only using parent site ( main website) for now there are no child sites setup.

I would appreciate your help

Govindji Patel

Re: Error code: 400

PostPosted: December 21st, 2011, 10:03 am
by Jason Caldwell
A fix for this was released in s2Member v111216. The latest version of s2Member now is v111220, so I would start there. If this problem continues for you, please let us know.

Re: Error code: 400

PostPosted: December 21st, 2011, 10:32 am
by govpatel
How do I get s2Member v111216 as I have this Version 111220 i wordpress admin panel yet.

I manage to get s2Member v111216 and replace Version 111220 to see if I can get it work and I am still getting same error and ask me to update to Version 111220

Re: Error code: 400

PostPosted: December 21st, 2011, 11:08 am
by Jason Caldwell
govpatel wrote:How do I get s2Member v111216 as I have this Version 111220 i wordpress admin panel yet.
That's fine. Our versions match the date of release. So v111220 is higher than v111216. You're good there. I'll see what I can do to reproduce this specific error and update this thread asap.
Error code: 400. Error Message: Unable to delete existing Amazon® CloudFront Downloads Distro. Unable to delete existing Amazon® CloudFront Distro. Bad Request
In the mean time, you can log into your Amazon CloudFront Console and disable/delete your previous Distros manually, as a workaround. Once deleted, run s2Member's auto-configuration routines again.

Re: Error code: 400

PostPosted: December 21st, 2011, 12:37 pm
by govpatel
I have tried and create new keys in Amazon S3 and am still having the same problem

Re: Error code: 400

PostPosted: December 21st, 2011, 12:57 pm
by govpatel
Ok I managed to get it to work as this was fresh install on plugin I deleted everything by clicking on No to safegaurd in Deactivation Safeguard and deactivate and delete the plugin.
Reinstall the plugin and then add the keys and it worked and gave message to wait 30 mins to propagate.

Thank you for your help Jason Caldwell

Re: Error code: 400

PostPosted: December 24th, 2011, 2:00 pm
by Jason Caldwell
Thanks for reporting back on this.
Have a great holiday!