102jili register.REGISTER NOW GET FREE 888 PESOS REWARDS!

Error 400 when trying to Save any change

528491 — Fri, 23 Jul 2021 06:49:12 +0000

Hello,
Ever since I updated the plugin from 2.1 to 2.1.5 I keep getting POST 400 error in my Chrome console whenever I try to Save any change I make to any template, even if it’s just switching the slider from on to off. The ‘Oops…’ message pops out and the loading circle keeps spinning forever. Please see screenshot of the error:
https://photos.app.goo.gl/Dz2wTwfxWBXqmHz67

Could you please make the version 2.1 available for download in the Advanced repository of the plugin, so I can try reverting back to that version? It is at the link:
https://www.ads-software.com/plugins/yaymail/advanced/, at the bottom of the page.

At this point, only version 1.9.6 is available, and it gives me same error.

Additionally, can you please point me in the right direction as of why this error is happening when trying to save template changes?

reCAPTCHA v3 400 Error

rondo858 — Fri, 17 Jul 2020 18:56:14 +0000

I am receiving a Bad Request Error with reCAPTCHA v3 api: https://www.google.com/recaptcha/api.js?render=6Le8YLIZAAAAAJVsrHeyfTWNTIbvdCEiQLH6-2oZ

The version-2 options seem to be OK.

Any insights?

The email could not be sent: Bad Request

summerlightning — Sat, 16 Dec 2017 16:15:21 +0000

Dear Mailpoet,

Firstly, love the plugin, makes it so quick and easy to make great looking newsletters, so thank you.

Now the issue. When trying to send a preview of a finished newsletter I am receiving the error: The email could not be sent: Bad Request

It was working with the previous version, but I have today upgraded to Mailpoet 3 version 3.3.1.

Is this a known error you are dealing with?

I also use WP MAIL SMTP (v.1.0.2), but have had no issues with these plugins working together before. Other website emails are being sent via WooCommerce and contact form.

I’ve cleared my cache, tried different email addresses, exited and re-entered the form and google searched, but no luck.

Be great if you can help!
Thanks

Default show display increased to 300

Alan Petersen — Tue, 28 Nov 2017 02:40:18 +0000

I’m having issues trying to get the plugin to show all my podcast episodes versus the default 50. In order to change the default of 50 in the “Show the most recent” setting which triggered “400 Bad Request” errors so my web host had to get involved to get PowerPress to accept 300 in the “Show the most recent” field. Even now with that changed the feed is still only showing 50 episodes (cutting 8 episodes of the feed). I did a manual podcast refresh form iTunes Podcast Connect and the refresh has happened but the feed will still only show 50 even though I changed that to 300 in the PowerPress settings. Please advise. Thanks.

400 Bad Request Error

Lemnis — Mon, 05 Oct 2015 20:45:53 +0000

When I try to update a page, I’m sent to the page that says: 400 Bad Request Error.

I tryed out a lot of things: clear cache of browsers (firefox, ie and chrome), disable all plugins, ipconfig/flushdns in my command prompt (in my Windows SO), switch themes and nothing works.

I can access the site, and it’s ok. I can create a page, it’s ok also.
This problem only happens when I try to update a page.

I don’t know what I can do, please help me!

Site not responsive in Mobile mode

Leah — Thu, 18 Jun 2015 00:37:52 +0000

Can you help me figure out why this plug in is not responsive on my phone? Only partial of my pages are showing, everything is zoomed out and does not fit on the screen.

Also, when I click on my blog link I’m getting the error: Bad Request Your browser sent a request this server cannot understand.

www.leahmarieimages.com

https://www.ads-software.com/plugins/wptouch/

400 – Bad Request

Sat, 10 Apr 2010 07:37:23 +0000

Hi
Recently I and my viewers have been getting “400 – Bad Request” error messages off and on when clicking on blog post or comment links, like this:

https://www.eevblog.com/2010/04/10/eevblog-73-how-to-screw-up-your-winning-product/#comments

I’ve tried to find info on it, and a few people mention clearing the browser cookies, but that’s not a solution I can tell my viewers!

Someone mentioned the cookie length is exceeding some “large_client_header_buffers” setting?

Anyone got any clue how to fix this permanently?

Thanks
Dave.