critara

@davidanderson excellent, thank you for the clarification

Thank you @mstuyts , that did the trick.
The following two lines added to the wpconfig file solved the problem:
define(‘WP_DEBUG’, false);
@ini_set( ‘display_errors’, 0 );

Hope this helps others too.

Thank you Nicola and @zamson, I have rolled back to php 7.2 and that solved the problem.
Thank you again, Nicola, this is a great plugin, by the way. Same for your support ??

P.S. By the way, I was having the opposite problem @zamson had: my dashboard was broken but the website was otherwise working just fine.

• This reply was modified 5 years, 10 months ago by critara.

I’m having the same problem. Was working fine up until this weekend and after the latest WP upgrade it now gives me a 400 bad request.

I have exactly the same problem and from what I gathered online, the only solution so far is to pass the forms without javascript (which is not an option in my case for a number or reasons) or uninstall the plugin… I hope the author will reply to this thread, but in the meantime I shall find another solution.

I would like to add to this discussion, that as well as excluding Smart Cookie Kit scripts from Autoptimize (I still had to do it despite the update), you also need to do the same for Async Javascript, in case you are using both plugins.

Until I did that the Cookie alert would not even show up.

Thanks for this amazing plugin, by the way. I am using it on almost all my websites ??

Cristina

OK, I looked at your screenshots and found out that I did miss out a configuration in which I can set the message myself.

I am still finding it difficult to fix the styling of that span, though. It leaves an enormous white space at the top that I do not seem to be able to eliminate via CSS.
My fault again, I am sure ??
In case I do not manage to solve this, I will open another thread, meanwhile you can mark this one as resolved.

Thank you again and sorry to bother you for nothing !

Thank you, Gioni, I figured out what the problem was. It’s only relevant to the analytics view settings, as I mentioned above. Thanks for your time and assistance.

OK, I believe it is a mere problem of Analytics settings: I added “index.php” to the end of the URI as the “default page” in the View configuration, in order to merge results for */ and */index.php of any given page.

I will keep it as is for the time being. Unless someone has can help me out with this.

Thank you for replying, anyway.

They should not exist: it is a WP install configured with pretty urls.

I mean that I do not know if it is better to change the htaccess directive or to whitelist index.php files (non existant files)…

The script is blocking all index.php of subfolders. How can I allow all index.php files to be accessed?

Indeed, this is a very powerful plugin that needs a little more than just guessing your way through its various interfaces… Which is what I usually do! But the documentation covers it all, once you decide to plunge into it ??

PLEASE IGNORE THIS! I just find a similar thread elsewhere and the solution works.

In case it might be of use to others, here is the solution:

The PHP constant WPLANG should be used in the wp-config.php file, on the root of the WordPress directory. Have a look on the wp-config-sample.php file, you will notice there is such a constant.
Add this line on your wp-config.php file :
define(‘WPLANG’, ”);
or
define(‘WPLANG’, ‘en_GB’);

And this is the link to the thread: https://www.ads-software.com/support/topic/notice-use-of-undefined-constant-wplang/

Thanks and sorry to have bothered you!

I agree with you, backups are very important. And unfortunately I am 2 days late to being able to recover the db backup of my wp install previous to mailpoet’s update…

However, it is peculiar that after the march 30th update, two months later I found a complete new install of mailpoet, with sample newsletter, all lists gone, and no history of past newsletters.

This looks like an erase-all install.

My fault that I did not check the plugin after the update, of course. But how can an update result in a clean install instead?