Mailpoet not saving

Thank you. Do you have a quick fix / beta to get able to send an important email now?

When will be released this update?

Update to the latest version 2.6.17, the Prototype issue is now fixed!

If you are still facing a 404 or 403 on duplicate/delete newsletters you’ll have to ask your host support to disable mod_security for your website: https://support.mailpoet.com/error-403-on-admin-ajax-php/

The plugin update did NOT work any better for me. (V. 2.6.17) The “prototype.js” issue was still there.

But I can confirm that setting mod_security to OFF did the trick. Now the latest version of Mail Poet works.

I did not see duplicate problems, but I had issues with editing newsletters that was still not sent.

Again, I can confirm setting mod_security = Off, did the trick.

Thank you.

I can now edit, save and send newsletters ??

but i can not insert my wordpress posts into the newsletter. I have to make the newsletter from scratch

and i can not edit forms for putting in widgets. Using the standrd form gives error message if you try to add an email address on the website.

Adding the code described above to htaccess does not help, and turing off all other plugins does not help

Whoever still have any issues left, please get in touch with us over here so that we can properly help you: https://support.mailpoet.com/wordpress-forums/

I am having the same problem. I am using 2.6.18 version. I also set that code in my htaccess. Tried all plugin inactive etc etc. Nothing works. I can’t save changes in signup form.

@vikerfjell got in touch with their host support and they fixed it.

Tell your host that you get a 404 Not Found Error when MailPoet tries to post data to your wp-admin/admin-ajax.php file

My host made som changes, and now everything is working again

Hi Guys
Yes I have contacted my hosting guys and they fixed it. And now all works fine. so this topic is resolved I think

I am having this problem now. We use a plugin called All In One WP Security that allows us to rename our login page from /wp-admin to a cookie-based “secret word”. For example, websitename.com/?SeCrEtWoRd=1 could be a variation of our login URL. Once that is triggered, a cookie is put on the computer and the user is allowed to proceed to /wp-admin.

I found this comment on the internet:
“In the cases where your WordPress installation has a theme or plugins which “
“use AJAX, a few extra lines of directives and exceptions need to be added to “
“your .htacces file to prevent AJAX requests from being automatically blocked “
“by the brute force prevention feature.

Here is the part of our HTAccess file when this is enabled:

#AIOWPS_ENABLE_BRUTE_FORCE_PREVENTION_START
RewriteEngine On
RewriteCond %{REQUEST_URI} (wp-admin|wp-login)
RewriteCond %{HTTP_COOKIE} !*********= [NC]
RewriteCond %{HTTP_COOKIE} !aiowps_cookie_test_c4sdgc81am= [NC]
RewriteRule .* https://127.0.0.1 [L]
#AIOWPS_ENABLE_BRUTE_FORCE_PREVENTION_END

(The ******** is our secret word for this particular site)

As a quick follow-up, there is another option to just rename the login page (instead of the secret word redirect above). When enabled, it works fine.

websitename.com/renamedURL, for example

I would prefer the cookie based method. Its worth nothing that this method doesn’t add anything to the HTAccess file, but apparently does this in a database table instead.