Free-core release history.
A versioned record of shipped Free-core changes, fixes, compatibility notes and upgrade requirements.
1.4.0
Confirms unlimited Free publishing, keeps the four starter blueprints and core community workflows in Free, and moves licensed advanced implementations into the separate Pro add-on.
1.0.10
Prevents block themes from adding a second site header above NexDirectory app pages while keeping WP_DEBUG clean.
1.0.9
Moves mobile event-gallery scrolling out of inline Alpine attributes so sanitised markup cannot leak as visible text.
1.0.8
Hardens onboarding markup so WordPress sanitisation cannot expose hidden steps or Alpine expressions as visible text.
1.0.7
Adds an explicit in-page confirmation for demo imports and keeps the loader hidden until the import is confirmed.
1.0.6
Stops automatic page and taxonomy-term creation during activation; setup content now requires an explicit administrator action.
1.0.5
Adds a clear agree-or-cancel confirmation before demo content can be imported.
1.0.4
Removes the admin-dashboard iframe, strengthens nonce handling, sanitises helper inputs earlier and tightens output escaping.
1.0.3
Improves service disclosures, request security, media sanitisation and WordPress 7.0 compatibility metadata.
1.0.2
Adds WordPress.org review refinements, bundled demo-media handling and workspace visual polish.
1.0.1
Refines compliance and packaging for the WordPress.org review build.
1.0.0
Introduces the directory core, front-end submissions, moderation, maps, import tooling, Elementor integration and bundled asset handling.
Plan a safer update.
Match the package version
Check the plugin details and package filename before using these notes to plan an update.
Review every intervening release
When skipping versions, read each entry between the current and target versions rather than only the newest note.
Test the update on staging
Back up the site, apply the exact package on staging and verify public, contributor and administrator journeys before production.
Common questions.
Which package does this history cover?
These entries cover the NexDirectory Free core. Pro should publish its own package-specific release notes.
Can I update directly across several versions?
Test the full jump on staging and read every intervening entry for compatibility or migration guidance.
Where do I report an update problem?
Use the support centre with the source version, target version, WordPress and PHP versions, and steps to reproduce the issue.