Matt Wiebe

Hi @slow007 !

We have early support for this, but you have to be able to edit a constant in your wp-config.php file to enable it. You will find this file in the root of your WP install. Add the following to it:

define( 'ACTIVITYPUB_DISABLE_REACTIONS', false );

A few notes:

1. There is no way to display these on the frontend of your blog, yet (this is a main reason why it’s not yet enabled by default)
2. Likes and Reposts will appear as a type of comment. You can at least see these in wp-admin.
3. We already have this enabled for WordPress.com users ??

Once we’ve addressed the first issue, and generally cleaned things up a bit more, we’ll enable this by default.

We did add a very slight delay recently in this PR (to ensure that we don’t send posts marked as private):

https://github.com/Automattic/wordpress-activitypub/pull/959

But it’s only 10 seconds into the future of the current time.

Note that it may also take a while for a remote service to process and display the post even after it’s been sent, depending on the remote server’s software and load.

I’ll also add that editing a post will send an updated version of it to remote servers, which will then respect the new template.

Marking resolved due to no response, but do let us know if you’re still having problems @patricus

So that you can continue editing in Markdown, even after you’ve saved a draft or published a post.

> Is there a way to bulk update all the posts?

Probably unnecessary, since anything you save in the future with the Jetpack module active will just be auto-flagged as Markdown.

> Or tell WP to use the markdown version of the post even when the plugin is deactivated? There’s two versions of a post saved in the db, right?

The plugin needs to be active in order for WP to use the right version in the right context. Both MoSI and Jetpack Markdown operate in the same way – edit Markdown, show HTML. Deactivating leaves WP ignorant of the Markdown version, otherwise your visitors would just see plain Markdown.

Did you use the conversion step in MoSI first?

If something is broken on WordPress.com, please report it there. ??

Hi Li-An – you’ll only need to modify old posts once you go back and edit them.

Otherwise, this is actually how Markdown is supposed to behave: https://daringfireball.net/projects/markdown/syntax#header – any conversion systems that allow for no space in a heading are actually in violation of the spec.

@miki: You can have a slim Jetpack by just only activating the modules you want. ??

@preshit: great, glad it worked.

Can you publish the original text and converted text on pastebin? Is this on a Multisite blog?

The current plugin will continue to work just like it does. I’ll fix security issues if they arise, but otherwise development will cease on MoSI once I make a converter to migrate your posts for the Jetpack plugin, which should be soon-ish.

Jetpack’s not so bad. ?? Just enable what you what, use a “no-auto-activation” plugin if you dislike that behaviour. Or keep using this plugin as-is if you’re happy with it.

> From the looks of it, if I am not wrong, Markdown on Save Improved will soon make its way into Jetpack. It’s probably the one being used on WordPress.com as well.

Well yeah, I wrote the WP.com version, so there are definite similarities between that and MoSI. One of the differences is that WP.com Markdown is per-site rather than per-post, which in that case should eliminate the bug you’re describing.

If you have any other bugs where the Markdown content is deleted, please describe in detail. I can’t guarantee that I’ll fix anything, since this plugin will be deprecated in favour of Jetpack Markdown. I’ll put a migration plan in place as well.

Supporting on revision was a decent idea, but you really only want to support a revision if the post_type it is recording a revision of supports mosi. I’ve gone about things this way in v2.4.4, which I just published.

navarroj, thanks for finding where the bug was happening, and apologies for taking a long time. This is fixed in MoSI 2.4.4, which is now live.