Back in early 2022 I covered an Obsidian plugin that let you publish to WordPress and at the time I wasn’t all that impressed. It felt hard to use, didn’t remember your password, and really didn’t save any time. Since then I had it on my list to write a better plugin that took advantage of WordPress Application Passwords.

Well, I started building that plugin on Friday, March 16th and in the process of a bit of research into how to do it, I found that the plugin I reviewed has been getting updates and I didn’t even need to bother writing an Obsidian plugin.

Obsidian WordPress now supports 3 different types of authentication for a self-hosted WordPress site, and one more method for a site hosted on WordPress.com.

I’d recommend you use REST API Authentication by application passwords. You set this up under your WordPress user Profile, and if you need more directions check out the video above or see the developer’s documentation.

The plugin provides some basic yaml formatting you can add to the top of your document which will define the title and tags that you want to have in your post. You choose your category when you publish the post.

Once your content gets to your WordPress site it’s in a classic block which is fine. It’s a simple click to convert a classic block to a set of standard WordPress blocks.

Issues

While I love lots of what this plugin has to offer, if you have more than one WordPress site you want to publish to, this plugin won’t easily let you do that. You’ll need to change out the URL Username and Password each time you want to switch sites. There is already an issue relating to this on Github. According to the issue, this is on the feature list.

I’d also love to see the plugin send the content directly into the WordPress block format without needing to send it into a classic block first and require users to convert it themselves.

The final issue has to do with how the plugin stores your Application Password. At this moment it stores it in plain text in the data.json file inside the plugin. Yes, a password in plain text is right. I’d recommend you don’t save any passwords in the plugin at this time. I do have an email thread going with the author and we’re working on a method that will encrypt the password at rest.