Description
Multiposter lets you manage and display job vacancies on your WordPress site. Use it as a standalone job board or connect it to the Multiposter platform for automatic vacancy synchronisation.
Features:
- Custom post type for vacancies with detailed meta fields
- Archive page with filters (keyword, position, city, salary range)
- Responsive vacancy cards with thumbnail support
- Built-in application form (API or email submission)
- Favourites system (cookie-based)
- Related vacancies with configurable matching criteria
- Share buttons (LinkedIn, Facebook, X, WhatsApp, Email)
- SEO options with customisable title and description templates
- Open Graph and Twitter Card meta tags
- Configurable pagination and column layouts
- Image gallery with lightbox
- Performance caching with transients
- Gutenberg blocks (archive, latest vacancies, single vacancy, search)
- Full internationalisation support (Dutch translation included)
Standalone Mode:
Without an API key the plugin works fully standalone. Create vacancies manually in the WordPress admin, and applications are delivered via email.
Multiposter Integration:
Enter your Multiposter API key to enable automatic vacancy synchronisation. Vacancies are imported on a configurable schedule and applications can be sent directly to the Multiposter API.
Source code
The full, non-minified source code for this plugin (including the un-compiled JavaScript for the Gutenberg blocks) is publicly available at:
https://github.com/mooxnl/multiposter-wp-plugin
The compiled block scripts shipped under assets/js/blocks/ are generated from the matching files in src/blocks/ using @wordpress/scripts.
To build the block assets locally:
- Clone the repository.
- Install dependencies:
npm install - Build the production bundles:
npm run build - For development with file watching:
npm run start
The build writes the compiled JavaScript and *.asset.php files to assets/js/blocks/.
External services
This plugin connects to external services under specific conditions. The plugin is fully functional in standalone mode without contacting any of these services.
Multiposter API (app.jobit.nl)
Used to synchronize vacancies and, optionally, to submit job applications and candidate registrations. Only contacted when a Multiposter API key is configured in the plugin settings.
- What is sent — vacancy synchronisation: the configured API key and vacancy fetch parameters (channel ID, page, limit). No visitor data.
- What is sent — application form submissions (when “API” or “API and email” is selected for the application form): the configured API key and the form fields the visitor provides (name, email, phone, message, uploaded CV, vacancy ID), plus the attribution value described below.
- What is sent — registration form submissions (when “API” or “API and email” is selected for the registration form): the configured API key and the form fields the visitor provides (first name, last name, email, phone, motivation, optional uploaded CV), plus the attribution value described below.
- When it is sent: on the scheduled vacancy sync interval, on manual re-sync from the admin screen, when a visitor submits the application form, and when a visitor submits the registration form.
- Endpoints contacted:
https://app.jobit.nl/api/vacancies/channel/{channel_id}(vacancy sync) andhttps://app.jobit.nl/api/candidates(job applications and candidate registrations, distinguished by atypefield in the request body). - What is sent — attribution value: both form submissions include a
sourcevalue recording where the visit originated: theutm_sourceparameter of the campaign link the visitor arrived through, or the referring domain when no campaign parameter is present, orwordpressfor direct traffic. To survive the journey from landing page to form it is kept in the visitor’s own browser (localStorage, keymultiposter_source) for 30 days; it never leaves the browser except as part of a form the visitor submits. - Service: operated by Multiposter.
- Terms of service: https://multiposter.nl/informatie/voorwaarden
- Privacy policy: https://multiposter.nl/informatie/privacy-policy
Social share endpoints
The share buttons rendered on single vacancy pages link to external share URLs provided by LinkedIn, Facebook, X (Twitter), WhatsApp and the visitor’s own mail client. No data is transmitted automatically; data is only sent if a visitor clicks a share button and uses the resulting page.
- LinkedIn: https://www.linkedin.com/legal/user-agreement / https://www.linkedin.com/legal/privacy-policy
- Facebook: https://www.facebook.com/legal/terms / https://www.facebook.com/policy.php
- X (Twitter): https://x.com/tos / https://x.com/privacy
- WhatsApp: https://www.whatsapp.com/legal/terms-of-service / https://www.whatsapp.com/legal/privacy-policy
Installation
- Upload the
multiposterfolder to/wp-content/plugins/. - Activate the plugin through the ‘Plugins’ menu in WordPress.
- Go to Multiposter > Settings to configure the plugin.
- (Optional) Enter your Multiposter API key to enable automatic sync.
- Visit Settings > Permalinks and click “Save Changes” to register the vacancy URL slug.
FAQ
Do I need a Multiposter account?
No. The plugin works standalone without an API key. You can create and manage vacancies directly in WordPress.
How do applications work without an API key?
Applications are sent via email to the configured notification address, or to the site admin email as a fallback.
Changelog
2.7
- Tested with WordPress 7.1
- New: applications and registrations now report where the candidate came from. The
sourcefield carries theutm_sourceof the campaign link the visitor arrived through, falling back to the referring domain, and towordpressfor direct traffic as before. Attribution is first-touch, captured in the browser and kept for 30 days, so a visitor who lands on a vacancy from a campaign and applies several pages later is still attributed correctly. An explicit campaign link always replaces a stored referrer - Blocks now register with block API version 3. They were registered on the legacy v1 API while using
useBlockProps, which logged a console warning per block and wrapped every block twice in the editor (duplicate element IDs). Compatible with the always-iframed post editor in WordPress 7.1 - Fix: every single vacancy page fired a needless
admin-ajax.phprequest for the vacancy archive and then threw a JavaScript error (Cannot read properties of undefined) trying to scroll to an archive that is not on the page. The archive is now only fetched when its container is actually present, removing one uncached PHP request per vacancy page view - Fix: the Vacancy Archive block and the
[multiposter_archive]shortcode no longer output a second complete HTML document (<!DOCTYPE>, theme header and footer) inside the page content. The archive markup moved totemplate/archive-content.php;template/archive-jobs.phpremains the full-page template for the vacancy archive - Fix: the archive stayed stale for up to the cache duration (default one hour) after a vacancy was created, edited, trashed or deleted by hand, because only the API sync cleared the cache. Manual changes now clear it too
- Fix: clearing the archive cache had no effect on sites with a persistent object cache (Redis, Memcached), which store transients outside the options table. Archive cache keys now include a version number that is bumped on every invalidation
2.6
- Fix: duplicate vacancies. Three root causes are closed and existing duplicates are cleaned up automatically:
- The
jobit_idlookup during sync only saw published posts, so a vacancy that had been trashed by the expiry pass and later reappeared in the feed was inserted as a fresh duplicate. The lookup now covers all statuses and restores the trashed copy (including its original slug) instead - Added an atomic lock around the sync so overlapping runs (WP-Cron firing again during a slow sync, or “Vacatures nu ophalen” clicked while a cron sync runs) can no longer race each other into inserting the same vacancy twice. The button now reports when a sync is already running
- The 2.2 identifier migration now also runs at the start of every sync, closing the window where a cron sync fired after the plugin update but before any admin visit and re-imported the whole feed next to the still-unmigrated legacy
vacaturesposts - New cleanup pass on every sync: when multiple live posts share one
jobit_id, the copy the sync maintains (published, most recently updated) is kept and the others are moved to trash — duplicate pairs left behind by older versions disappear on the next sync - The Import Log “Verwijderd” column now records the number of trashed posts (expired plus duplicates) instead of always 0
2.5
- Fix: the archive filter spinner kept loading after switching to
wp_send_jsonin 2.3. jQuery now receives an already-parsed object on theapplication/jsonresponse, so the success handler no longer callsJSON.parseon it (which produced"[object Object]" is not valid JSON). The handler now accepts either an object or a string for safety.
2.4
- Fix: the 2.2 identifier migration could be skipped on sites where the first admin_init after the upgrade fired without
manage_options(editor-role user, custom roles, AJAX/cron contexts), leaving vacancies stored under the legacyvacaturespost type and invisible in admin and on the front-end. The migration now re-checks for legacyvacatures/cities/positionrows on every admin page load and renames any that remain, regardless of whether themultiposter_migration_v22flag was previously set - Fix: bust the posts and terms object-cache
last_changedkeys after the migration so cached query results pick up the renamed post type and taxonomies immediately
2.3
- Security: escape forward slashes in the JobPosting JSON-LD output so vacancy fields containing
</script>cannot break out of the schema<script>tag - Switched the archive AJAX handler to
wp_send_jsonand now caches the response as a structured array instead of a raw JSON string - Removed the unprefixed
[jobs_archive]and[job_single]shortcode aliases — please update existing pages to use[multiposter_archive]and[multiposter_single]
2.2
- Renamed text domain to match the WordPress.org plugin slug
- Prefixed custom post type, taxonomies and shortcodes with
multiposter_to avoid collisions - Added one-time migration that updates existing posts and terms on first admin load after upgrade — no manual action required
- Hardened API-key sanitization, escaped vacancy title in the
the_contentfilter callback, moved the inline admin loading-overlay style into the enqueued stylesheet - Documented the candidate registration endpoint and the public source repository in the readme
2.1
- Documented external services (Multiposter API, social share endpoints)
- Switched JSON responses to wp_json_encode
- Hardened output escaping on share buttons and admin settings tabs
- Corrected contributor username
2.0
- Added standalone mode (manual vacancy creation)
- Added application form email fallback
- Added security nonces to all AJAX handlers
- Added uninstall cleanup
- WordPress.org directory compliance
1.1
- Added Dutch date formatting
- Local font support
1.0
- Initial release
