rudyodo

Yep, same here!

I rolled back to version 4.16.0

Installed version 2.6.0 and the issue is solved indeed.

I’m marking this topic as resolved.

Tnx for the update, Judith

Looking forward to it!

No problem, thanks for the update.

Try ‘0’ as space between. Your example uses the standard space, and that’s just what it gives in all cases.

I changed the cronjob to ‘WordPress built-in cron (recommended)’, but then my VPS got stuck, so I had to return it to ‘Visitors to your website’. My website has thousands of visitors a dat, so it should do the job.

I think ‘direct’ stopped working after updating to 3.95.1.

I’m having the same issue.
Notifications (direct) stopped sending on aug 23 without any logical reason.
Weekly newsletter still went out.

Today I got this message on my Facebook development kit: “The oEmbed product has been replaced with the oEmbed Read feature”.

If you implemented the oEmbed product before June 8, 2021, you have until September 7, 2021 to complete App Review for the oEmbed Read feature. If you have not been approved for the oEmbed Read feature by September 7, 2021, your oEmbed implementations will fail to load.

https://developers.facebook.com/docs/plugins/oembed/

Your problem may be related to this.

Hi Scott,

Tnx for the update!
It is exactly what I suggested.
Much appreciated!

It’s bizarre. On my website the manual post-selection keeps appearing in the main window, not in the sidebar. No change when deleting cache or deactivating cache. “post_in” was always selected, that is not the issue.
Meanwhile, I tested the plugin in a test environmont (same theme, mostly the same plugins) and it works perfect there (with de selection tool in the sidebar and also in Chrome). So there’s probably some (small) conflict with another plugin. For now I’m giving you the benefit of the doubt ??

Version 2.0.13:
– same Chrome issue
– manual added posts do not appear
– descending works again normal
I rolled back to 2.0.10.

It’s not a cache issue, I’ve double checked on different pc’s. It’s a Chrome-conflict.

Version 2.0.12 has another (much bigger) issue: it’s giving only the same oldest articles on all posts, no matter how the query is configured, no matter the taxonomies. I had to roll back tot 2.0.10.

• This reply was modified 4 years, 9 months ago by rudyodo.

Thanks for the update. Works like a charm again!

Ok! Works perfect (again).
Thank you for your effort. Much appreciated!