Alex Kirk

Hi, sorry for the trouble! I can reach that page fine, I suppose you are talking about that page when you are logged in?

Could you share some details about how your site is set up? Do the WordPress files reside in the /blog/ folder or have you configured WordPress with a Home URL like that?

The Friends plugin just creates a page with the title Friends, so you can just edit it by navigating to the Pages section in wp-admin and edit the page there.

I’ve contributed a Parser for the Friends Plugin to the ActivityPub plugin.

So if you install the ActivityPub plugin also (there is a section in the Friends plugin “Plugins” that lists other plugins that extend its functionality), you can use Friends to follow people on Mastodon:

The ActivityPub plugin provide the protocol support to extend the Friends plugin.

Apart from that, you are right. The goal of the Friends plugin itself is to befriend other blogs that also have “Friends protocol support” which currently means just WordPress blogs with the Friends plugin.

• This reply was modified 1 year, 11 months ago by Alex Kirk.

Hi DJM,

thank you for reporting and catching this! I released version 2.1.2 to fix this bug.

Alex

Hi DJM,

thank you for reporting this!

If I try to refresh the page, get a 430 Forbidden “You don’t have permission to access this resource

Do you possibly still have the URL of that page that gave you the 403? Were you on WordPress’s users page?

Alex

Hi DJM,

thank you for your remarks, this is helpful!

* there’s no way (button, link…) to go back to the admin interface (if not opened in a new tab). Had to activate the “Show Toolbar when viewing site” user option.

Oh, I didn’t consider someone would hide the toolbar on the site. We’ll improve this, you can track the progress here: https://github.com/akirk/friends/issues/126

* on the Friends page, the “older posts” button doesn’t seem to work : doesn’t go to “/page/2/” although the page feed shows “20 posts”.

Actually it should load the next page in the background and add it to the bottom to provide endless scrolling. Maybe this didn’t work for you? Could you try again and see if you encounter a JavaScript error when scrolling all to the bottom?

Tracking this in https://github.com/akirk/friends/issues/127.

* Although I do have “image” and “video” type posts, they don’t seem to appear

By default, your own posts are not shown on the friends front page except on the status page. We’ll figure out a way to improve this inconsistency that probably confused you, tracking this here: https://github.com/akirk/friends/issues/128

* when using Yoast SEO, 2 new taxonomies are created: Reactions & Feed URL.

These should not be exposed, tracking this here: https://github.com/akirk/friends/issues/129

Thank you for reporting these and sorry for the trouble! I’ll look into solutions for the above soon.

Alex

Hi DJM,

thank you very much for reporting this. It looks like we forget to delete some taxonomy entries when uninstalling. We’ll improve this. You can follow the progress in this Github issue: https://github.com/akirk/friends/issues/125

Thanks,
Alex

Hi @mathse,

do you have control over the text to be pasted? Automatic embedding will only happen on links that appear at the start of a line. You could prefix it with a . and then it won’t be expanded.

Also, remember that you can easily undo an automatic embed by clicking on the embed, then the icon in the toolbar that appears above (for example the YouTube icon) and it will offer to “Transform to Paragraph”.

It might not be feasible for posts with very many embeds but maybe good enough for your use case.

Thank you for letting me know early! This API is being used by Gutenberg Everywhere which the Friends plugin uses for its messaging with Gutenberg formatting.

I saw that you already created an issue there, so I’ll be following that and will update my code as soon the fix has landed there.

Marking this as resolved for now and will post an update when I’ve updated the code.

Yes, there is a feature called “blog to blog messaging.” You can take a look at a short demo video in the pull request.

@vasch: check if you have some whitespace in line 1 of qtranslate.php, probably it says ” <?php” instead of just “<?php”. Delete the whitespace ahead of the <

Here is a better fix for qTranslate for WordPress 3.9 with a little explanation. Basically the plugin provides a second parameter that is interpreted wrong.