Mike Clark
Forum Replies Created
-
Hi! Details of an example site are as follows:
Server architecture: Linux 6.0.2-x86_64-linode157 x86_64
Web server: Apache/2.4.57 (Debian)
PHP version: 7.4.33 (Supports 64bit values)Extension: mysqli
Server version: 10.4.20-MariaDB-1:10.4.20+maria~buster-log
Client version: mysqlnd 7.4.33Happy to provide further info etc by email.
I am also seeing this error on two separate sites.
I found these two entries in Simple History for one of the sites:
9/9/23 Updated plugin “Download Monitor” to 4.8.10 from 4.8.9
3/9/23 Updated plugin “Download Monitor” to 4.8.9 from 4.8.6Does that mean skipping 4.8.7 or 4.8.8 broke something? How can I fix it?
Forum: Plugins
In reply to: [Public Post Preview] Plugin not compatible with WP 6.2.2This is an issue for me too, also on 6.2.2Sorry, I was mistaken; it is a while since I used the feature and forgot one has to save the draft before the link appears. My bad!
- This reply was modified 2 years, 10 months ago by Mike Clark.
Forum: Plugins
In reply to: [Jetpack VaultPress] 2.1.3 update not coming back from maintenance modeNo problem — I’ve sent email to your automattic.com addy.
Forum: Plugins
In reply to: [Jetpack VaultPress] 2.1.3 update not coming back from maintenance modeYes, I requested the update from the updates page in the backend.
I’ve a couple more yet-to-be-updated sites hosted on the same environment. You’re welcome to take a look in if it would help…
(btw, is that REALLY your website linked from your profile? 😉 )
- This reply was modified 5 years, 9 months ago by Mike Clark.
I’m seeing this too, FWIW
Just adding my voice here — seeing a changelog is an important factor in deciding whether to update right away (risky), to wait a couple of days for any potential issues to emerge in the support forum, or if it can safely be left until the weekend maintenance window.
@zenrhe I’m seeing a proper sitemap at the link you have given — looks like it works fine.
Hmmm. That’s odd. I’ve actually got two different (private) P2 installs, both on different hosts, and they’re both showing the same problem. But yours clearly isn’t.
I’ve tried disabling that last plugin, and I’ve tried a different browser. Not sure where to look next, TBH. I think I’ll try spinning up a public P2 later to see if it happens again and so folks can take a look if necessary…
@aditya, I understand that it is much easier to troubleshoot problems with access to the site, but it just can’t be done in this case. The site contains commercially sensitive information and access is tightly restricted.
EDIT: Removed unnecessary comment 😉
@aditya – It’s a private installation, so sadly I can’t link to it. The steps to replicate given above have been tested on it, though.
@esmi – Good question. I’ve deactivated all the plugins on the site except for “Registered users only”, which we use to keep it private. The theme is plain vanilla and unaltered. The problem is still there.
There’s a screenshot showing the issue here:
That’s very responsive support, writing an entire blog post about my question moments before I even asked it 🙂 Thanks, RoamFree, for the steer.
FWIW I had to add *both* the filters shown in that thread before the Jetpack OG tags went away.
This is what I added to functions.php:
// stop Jetpack plugin from adding its own Open Graph tags -- leave it to the Yoast SEO plugin add_filter( 'jetpack_enable_opengraph', '__return_false', 99 ); add_filter( 'jetpack_enable_open_graph', '__return_false', 10, 3);I have exactly the same issue.
However, I’m seeing both Jetpack and Yoast SEO post a snippet of content as “og:description”.
To me it looks like Yoast SEO is doing a slightly better job of posting Open Graph attributes. Nonetheless, we need to turn one of these off. Has anyone got any ideas on how to do that?
Wow, thanks JowiM! The whole back end wasn’t working but this fixes it. I expect a lot of other folks will need this over the next few hours…
Not sure if it is the answer you are looking for, but I found that Google very much likes images to be served from the same domain as the HTML, particularly for Google News.
It is easy to fix; just set W3TC to not use the CDN when serving requests to Googlebot. I guess this could make Google perceive a site as being slightly slower, but I’m willing to live with that.
![https://www.sjb.co.uk/wp-content/uploads/[email protected]](https://www.sjb.co.uk/wp-content/uploads/microsoft-Search-Results-Newsdesk-@-xxx.png){kind=link}