You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Old syndication targets not cleared when logging out.
I was disabling the obsolete WordPress plugin Bridgy Publish, since the functionality is now in Syndication Links. The github target name was bridgy-publish_github and now is github-bridgy. After disabling the plugin I logged out/in with Omnibear to https://dougbeal.com. The log shows just the new syndication targets:
Old syndication targets not cleared when logging out.
I was disabling the obsolete WordPress plugin Bridgy Publish, since the functionality is now in Syndication Links. The github target name was bridgy-publish_github and now is github-bridgy. After disabling the plugin I logged out/in with Omnibear to https://dougbeal.com. The log shows just the new syndication targets:
> [
> {
> uid: bridgy-publish_twitter
> name: Twitter via Bridgy Publish
> },
> {
> uid: bridgy-publish_flickr
> name: Flickr via Bridgy Publish
> },
> {
> uid: bridgy-publish_github
> name: Github via Bridgy Publish
> },
> ]
Sending a reply gives a Status 400 error:
> {
> message: Error sending request
> status: 400
> data: h=entry&in-reply-to=https%3A%2F%2Fgithub.com%2Fdougbeal%2Fdocker-dougbeal.com%2Fissues%2F7&content=Fixed%20by%20https%3A%2F%2Fgithub.com%2Findieweb%2Findiewebify-me%2Fissues%2F75%0A%F0%9F%8E%89&category%5B%5D=docker-dougbeal.com&category%5B%5D=github&category%5B%5D=h-card&mp-slug=fixed-by-https-githubcom-indieweb-indiewebify&mp-syndicate-to%5B%5D=bridgy-publish_github&mp-syndicate-to%5B%5D=github-bridgy
> method: post
> url: https://dougbeal.com/wp-json/micropub/1.0/endpoint
> headers: {
> Accept: application/json, text/plain, /
> Content-Type: application/x-www-form-urlencoded;charset=UTF-8
> }
> }
due to Omnibear sending both the old and new targets.
(Originally published at: https://crw.moe/t/1ga)
The text was updated successfully, but these errors were encountered: