cybeardjm

Oh, thx, that’s what I’ve been telling you from the start: no, it’s not!

Although I disabled Readability Analysis, the tab or panel is still there on the right column as shown in the image I sent…

Thx,

One blog seems to be working, after I removed many AIOWPS options, to the bare minimum (score is 260).

Only change today: updated to the latest version of the AP plugin, but review of the changelog didn’t show anything special.

The second one (both are subdomains on the same domain and host), still not working, although it has been working for a few years (since 2019)… Will review all options one by one…

Oh, you’re right, restrictive options from my FireWall…
Sorry about that. Here it is: https://pasteboard.co/OEPfyyXmGsj4.png

Yes, latest versions for everything…

See image here: PB Yoast SEO

As said earlier, this appears in the Settings column, on the right when editing a post (for those who know WordPress…)

Oh thx @pfefferle – been playing with “Mastodon via Bridgy” a lot and globally it works fine, when Webmention is properly configured + a minimal set of Microformats2 (via the Indieblocks plugin)…

Have likes & reposts populating the comments section of the posts I test with… that’s fun (check here https://www.didiermary.fr/rss-feeds-mastodon-fediverse/ ) – still a few glitches with the theme (2023) as posted in a separate request here.

Sincerely
DJM

Oh interesting… I don’t have it for both admin and editor roles…

As stated earlier, on have 2 options:

• Do not allow search engines to show this author’s archives in search results.
• Disable SEO analysis

OK – found why…

=> in Yoast SEO settings, I have to ENABLE readability analysis to be able to DISABLE it at the user level. (?????!!!!!!!!!!!!!!!!!!!!!!!)

BUT, the problem’s the same: the YOAST SEO panel when editing posts is still there, with a red icon ?? for Readability analysis in the left column.

Tried to close it multiple times, but it reopens automatically when opening a post…

As I said bad UI/UX design…

Where?

The Yoast section on my user profiles doesn’t have an option to disable this.
Only options I have are:

• Do not allow search engines to show this author’s archives in search results.
• Disable SEO analysis

Yoast SEO – Settings – Readability Analysis (feature not enabled)

@maybellyne Your reply is kinda insulting to me… “You stoopid user, why don’t you read the small lines”. [I do & did read the small lines…]

OK, I understand your point: you don’t care… it’s all my fault…

PS: when posting, I knew the answer would be this one. Less insulting though…

OK, just added the line in both wp-config files (2 blogs).
RSS-Club Posts & Pages all have:

<link rel="webmention" href="https://amf.didiermary.fr/wp-json/webmention/1.0/endpoint" />
<link rel="https://webmention.org/" href="https://amf.didiermary.fr/wp-json/webmention/1.0/endpoint" />

in the source code.

Updated errors on bridgy:

• old “normal” posts went through properly
• RSS-Club Posts & Pages now all appear as “Failed” (multiple likes, comments & shares in the queue)

Tested the endpoint, by sending a webmention manually to one of the RSS-Club test posts: message “Pings are disabled for this post”. Same for a page.

As I stated earlier, when editing individual posts or pages, the option to allow Pings/Trackbacks is not available in the “discussion” panel under comments, as it is with “normal” posts.

Pages & RSS-Club are enabled in the settings both for Webmention & Syndication Links.

Thx, I’ll try this suggestion, as I just noticed it’s exactly the same for pages, although activated in the Webmention settings page (and the Syndication Links one).

Sincerely
DJM

More info:

Bridgy says for the post used as example: “No webmention support”
Webmention panel under this post when in edit mode says there is no endpoint.

DJM

• This reply was modified 1 year, 1 month ago by cybeardjm.

Yes, that’s what I added in an edit…

But the Webfinger testing tool doesn’t agree “Error getting JRD: 403 Forbidden”

“JSON Resource Descriptor (JRD) null”

Or the testing tool is broken?

Will report, just to see how they react… ??

Probably with WordPress themes not fully “transitioned”, yes, there was a “legacy widget block” – not with Twenty Twenty-Three anymore, it’s gone (or I can’t find it…)