jramerman

Hi Sorry but we decided to give up on this.
Thanks for your time trying to solve it.
Kind regards,
Jolanda

Any suggestion how to solve this?

hi Luke,

for us it’s:
PHP memory limit 256M

number of users is: 80

Hope this helps!
Kind regards,
Jolanda

We’re experiencing this conflict, too. Looking forward to the update. Thanks for a great plugin!

Hi,

it’s about the posts (not pages) that are presented with the posts widget from Elementor (like a post archive) on a certain page.

Not every post will be translated. If a post is not translated, than it shouldn’t be shown on the French newspage. Only posts that were translated in French should appear on the French version of the newspage.

So there are posts that can be shown in the French translation, but certain posts won’t be translated in French and in that case we don’t want them to be presented on this news page when people choose the French translation. On the other hand, when choosing Dutch, we still want those post to be there.

So the switch of showing or not showing up in a certain language is depending on the post if this has been translated. Not translated means, only show up on the Dutch newspage. Translated means show up on the French site (translated in French) and on the Dutch site. This counts for every post seperately.

Hope this makes it more clear.

Kind regards,
Jolanda

Hi @treibalen
have you seen my screenshots/info?
The provider has checked the DNS settings again and can’t find anything, so if anything is still not ok, please provide me with the proper info to hand over to the provider.
Hope this can be solved!
Kind regards,
Jolanda

Hi,
could you please take a look at my screenshots and problem?
Kind regards,
Jolanda

Hi,
sorry for late reply, I was hopeful waiting would solve the problem.
But it’s still there, the provider has taken care of the DKIM DNS settings.
The domain is verified in my Mailpoet panel.

In response on your question above:
https://snipboard.io/sHV47e.jpg
https://snipboard.io/Fg8p21.jpg

Hope you have a solution.
Kind regards,
Jolanda

Hi Elvira,
yes I had an error box above the list with newsletters and clicked the resume button. Now I don’t have that error box any more and again have clicked the resume button, once from within an opened newsletter, just as if you would do with a newly made one and once from the list of all newsletters.
After clicking the button it shortly gives a message saying that the system will resume to send the newsletter. But it’s not sending, after about 10 minutes I get the same error again. This is when I send with MailPoet sending service.

If I use the other sending method (from the server itself) it’s sending sometimes (sometimes also the same error), but it takes very long time.

For the previous sent newsletters I can’t see which mailaddress was used.

So we can’t use it this way. I hope you have some more suggestions for me!?
Is there a bypass way to test this method of sending and have a log of the problem?

This has worked very well before (last newsletter was July 26 2021)

Kind regards,
Jolanda

Hi,
Sorry but I read too many bad reviews for the Health Check plugin. I rather not take the risk. I have now downgraded to Yoast 14.4 and set debug in config.php back to false.
With that setting, I don’t have no problems any more. Hopefully it will be fixed with one of the next updates. Sorry I can’t offer you more input about the problem, I simply can’t afford having this site going down again.
You can close the ticket.
Kind regards,
Jolanda

Hi,
Sorry, I forgot to mention that I have downloaded the plugin manually and after deleting the old files I uploaded the new ones.
That didn’t help.

It’s not that WP_DEBUG setting is causing the error. I saw in another thread that someone changed this WP_DEBUG from false to true and that it helped with the problem with this update.

That has nothing to do with caching etc. I agree having this set to TRUE in a production environment is a no go.
So it would be helpful if there was another thing I could do to avoid the error.

The error I have says:
There has been a critical error on your website.
I am sure it’s only from Yoast SEO, not from other plugins or themes, I have tested that.

Kind regards,
Jolanda

Sorry I move over to that thread.

Same to me, when plugin folder is renamed, there is no problem. When wp-config’s WP_DEBUG is set to true, there is no problem. Otherwise I have a WordPress critical error notice.
It’s got nothing to do with other plugins or theme, I have tested that.

Hi Jeroen,
if I set
define(‘WP_DEBUG’, true); instead of false,
the problem is gone.
I saw this mentioned on this thread: https://www.ads-software.com/support/topic/14-5-breaks-the-head/
Kind regards,
Jolanda

I also have a problem after update to 14.5. It’s a notice from WordPress (critical error). The problem is gone when I rename only the wordpress-seo folder.
I have replaced the current plugin folder with a new fresh downloaded one, but the problem still exists. Unfortunately, I’m not able to look at log files at the server of this site. What else can I do (except deactivating the plugin) to solve this?