Description
Desk-Net has changed its name to Kordiam. A new version of this plugin is available under the name Kordiam: download the Kordiam plugin. You can keep using the Desk-Net plugin, but it will no longer be updated.
How to switch from Desk-Net to Kordiam
When you activate Kordiam, it copies all your Desk-Net settings: your API credentials, your status, category, custom field and task mappings, and the links between posts and stories. You don’t need to set anything up again. The Desk-Net data is copied, not moved, so you can always switch back.
- Back up your database. This is a standard precaution.
- Install the Kordiam plugin. Don’t delete Desk-Net yet.
- Deactivate Desk-Net. Deactivate it only; don’t delete it.
- Activate Kordiam. Your settings and post links are copied across automatically. If both plugins are active at the same time, Kordiam pauses and shows a warning, so that stories are not sent to Kordiam twice. Once Desk-Net is deactivated, Kordiam takes over and picks up any changes made in the meantime.
- Check your settings. A new Kordiam item appears in the admin menu below Posts. Go through its sub-pages and confirm your mappings are there.
- Test the sync. Create or edit a post in WordPress and check that it appears in Kordiam. Then edit a story in Kordiam and check that the changes reach WordPress.
What to change in Kordiam
Nothing. The site keeps its existing API credentials. The old REST namespace wp-desk-net/v1 keeps working alongside the new kordiam/v1, so requests from Kordiam continue without any reconfiguration.
Rolling back
Deactivate Kordiam and activate Desk-Net again. Kordiam never changes the Desk-Net data, so everything works as it did before the switch.
When to delete Desk-Net
Only after you have confirmed that everything works.
- Don’t delete Desk-Net before activating Kordiam. Deleting Desk-Net erases its settings, and then only the post links would be left to copy.
- After you delete Desk-Net, you can no longer go back to it with your old settings.
About the Desk-Net plugin
Are you using the editorial calendar software Desk-Net to plan your stories and to manage your editorial department?
This plugin connects your Desk-Net account to one or multiple WordPress sites. Your story lists and related meta-data such as statuses are synced both ways between the two systems.
Two main use-cases are supported:
- Planned content: A post is planned and enriched with meta-data in Desk-Net. Based on this Desk-Net automatically creates a post in WordPress. Subsequent changes in either system are synced instantly.
- Breaking news: A story originates as a post in WordPress. The plugin sends relevant data to Desk-Net ensuring the story lists are complete.
The following meta-data is synced:
- Slug and description
- Publishing date and time
- Statuses
- Categories
- Author emails
- URLs of either system
- The plugin supports the Gutenberg editor.
Please note that you need to have an account in Desk-Net to make use of the plugin.
You are working for an editorial or content marketing team of 15 or more users? Learn more about Desk-Net and request your free test account on the Desk-Net website.
Installation
Please note that you need to have an active account in Desk-Net and the Desk-Net API credentials to use this plugin. Once you have a Desk-Net account you can request the API credentials from support@desk-net.com
Installing from your WordPress Dashboard:
- Upload the plugin files to the
/wp-content/plugins/plugin-namedirectory, or install the plugin through the WordPress plugins screen directly. - Activate the plugin through the ‘Plugins’ screen in WordPress
- The plugin label “Desk-Net” appears below the navigation item Posts.
- Navigate to that Desk-Net plugin and its sub-pages to connect Desk-Net with WordPress and to adjust the settings
- We strongly recommend you check out this support post before adjusting the settings.
FAQ
What types of users should use the Desk-Net plugin?
The plugin is directed at customers of the editorial management software Desk-Net. This tool helps medium to large editorial and content marketing teams plan and coordinate content across multiple platforms.
Do I need to be a Desk-Net customer in order to use this plugin
You do not need to be a customer to test Desk-Net and the plugin. However, after the free test phase you would need to be a paying Desk-Net customer.
Screenshots




Changelog
1.0.1
- Bi-directional connection between WordPress and Desk-Net
- Post description transferred between both systems
- Status matching
- Publishing date and time matching
- Category matching
- Matching of authors based on email addresses
- Content (text, video files, picture files, etc.) transfer from Desk-Net to WordPress
- Exchange of URLs between both systems
1.1.5
- Synchronization with the Slug feature in Desk-Net
- Updated logic for category and status synchronization between WordPress and Desk-Net
- Update help text
1.1.11
- Updated functionality for system messages in the plugin (some messages were not displayed correctly)
- Nginx support
1.1.12
- Synchronization of the optional header field in Desk-Net
1.1.16
- Filters to control Desk-Net post/story data
- Only allow initial slug syncing
1.2.6
- Support for the Gutenberg editor added
1.2.8
- Real-time support of data updates for the Gutenberg editor
- Store credentials in case of Desk-Net plugin re-activation
- Updated WordPress statuses list on the Status Matching page
- Updated logic for dates synchronization between WordPress and Desk-Net
1.2.9
- Updated logic in Classic Editor for posts synchronization between WordPress and Desk-Net
1.2.10
- Draft post date and time syncing
1.3.3
- Task matching
- Updated Notice message list
- New logic: Category matching with custom post meta fields
- New logic: Slug matching with custom post meta fields
- Updated logic: Category synchronization between WordPress and Desk-Net
1.3.6
- Support for the Custom post statuses
1.3.7
- Improved Desk-Net block loading logic on Post Editor page
1.4.15
- Global Export
- Custom Fields matching
- Only allow initial status syncing
1.4.18
- Publication Custom Fields matching
1.4.19
- Fixed error in logs when uploading files with long names or invalid EXIF data
1.4.21
- Fixed duplicate Desk-Net story created during story import
- Fixed block editor critical error on posts with an empty Desk-Net notice id
- Fixed block editor crash on custom post types
- WordPress 7.0 compatibility
1.4.22
- Fixed wrong post date (1970 or far future) when a story without a publication date is updated
- Fixed publication time one hour off across daylight saving changes
- Fixed date set in WordPress not sent to Desk-Net for scheduled and published posts
- Fixed date of stories without a time moving one day forward for sites west of UTC
- Headlines and custom fields mapped to the title are no longer cut to 77 characters; only a story description used as the title is shortened
