WordPress

Experimental. Integrations are still being tested. They may not run, or may give incomplete or wrong results — check anything important yourself, and tell us what goes wrong.

Connect a WordPress site and its posts appear in a calendar called WordPress:

• Scheduled: Autumn launch at the time it's set to go out, for the next three months.
• Published: … for posts from the last two weeks.

The calendar never counts as busy, so it doesn't block your booking page. Rescheduled posts move; a post taken off the schedule disappears. Each event links to the post in the WordPress editor.

#Connect

WordPress uses application passwords — a separate password made just for Daykite, which you can revoke at any time without changing your own.

1. In WordPress, go to Users → Profile, scroll to Application Passwords, type Daykite and click Add New Application Password. Copy the password it shows (24 letters, in groups of four).
2. In Daykite, Integrations → Publishing → WordPress: enter the site address (it must start with https://), your WordPress username and the application password, then Connect.

Use an account that can write posts (author, editor or administrator) — others can't see scheduled posts. The password is stored encrypted and only used to read posts; Daykite never publishes or edits anything.

#If it won't connect

• "didn't accept that username and application password" — check the username (not your email), and that the password is the application password. Some hosts and security plugins strip the login header WordPress needs; ask your host to allow the Authorization header.
• "doesn't look like a WordPress site with its REST API switched on" — the site's REST API is turned off by a plugin.
• WordPress.com sites need a plan that supports plugins; self-hosted WordPress 5.6 or later works as is.

To stop, Disconnect on the card, and revoke the application password in WordPress.