markpack

Ah, I missed that – thanks!

Yup, it looks to be just that one setting which resets.

Hi – this bug is still there I’m afraid. I just updated to v7.9.7 on WordPress 5.0.3 and the same thing happened with the setting resetting itself.

I clicked the update option from the plugins admin page (i.e. I didn’t download the zip file and then manually update the plugin).

In case it’s useful to know: this problem happened again when updating to the new 7.8.5 (i.e. the fixes in there didn’t resolve this for me). Thanks.

Yup, the embed code from the website does work – thanks. Be great if the plugin could too as that’s so much more convenient!

Thanks for that speedy reply. I’m on plugin v3.0.9 and WordPress 4.9.8.

Thanks for checking.

I found the problem in the end. The wp-admin end was protected via an SSL certificate, and so as some of the content the search pulls in isn’t over SSL, the browser was blocking its display.

Thanks for that speedy response – and at a weekend!

I’ve tested changing the language and it looks like the change isn’t even being made behind the scenes. Also no joy with uninstall/reinstall, so will ping you a support request from the settings in a moment.

Thanks again.

Apologies, I thought I had that covered already. Now sorted and error message banished. Thank you.

Hi Niall,

Here’s an example:

https://www.markpack.org.uk/36861/romneys-polling-day-technology-meltdown-orca/ was published on 12 November and has 1 Facebook comment on it.

However, according to https://developers.facebook.com/tools/comments?id=XXXXXXXXXX&view=queue (I’ve substituted the actual id number with XXXXXXXXXX) there have been no Facebook comments posted on my site since 30 September. This comment (and others posted since 30 Sept) don’t appear at all in the moderation tool.

Thanks for taking a look.

Hi,

This is a problem with the latest version of the plugin too (v1.1). Any news of a fix or possible work-around?

Hi Joe: I tried the latest version of the plugin again (with WordPress 3.2 this time) and again syndicated posts didn’t trigger tweets. Reverting back to version 2.2.12 and all is working ok once again.

Thanks for that quick response Joe. I’ve downgraded to the previous version and all works fine. (I guess it’s possible the timings are a coincidence and some third factor is at work rather than it having been a problem with the latest version of this plugin.)

Re. custom post types – I did double check my settings, but is there a particular user mistake that happens with these which I should watch out for?