Give each main screen one clear home
NexDirectory screens appear through shortcodes placed on normal WordPress Pages. The page shows the screen; Settings → General → Routing & Page URLs tells buttons, redirects and account navigation where to find it. Core discovery, account and workflow pages are included in Free. Only add routes for Pro features—such as paid boosts, advanced reports or PWA experiences—when that separate add-on is active.
Use the profile-neutral shortcodes for new pages
Start with [nexdirectory_listings_archive], [nexdirectory_listings_map] and [nexdirectory_submit]. They adapt their public wording to Events, Directory, Job Board or Marketplace.
Create the public archive, map, calendar, and search surfaces
Use [nexdirectory_listings_archive] for the filterable archive, [nexdirectory_listings_map] for map discovery, and [nexdirectory_listings_calendar] for the calendar. The profile supplies preferred slugs such as /events/, /listings/, /jobs/, or /marketplace/ and corresponding map/calendar paths.
For embedded landing-page modules, the plugin also registers [nexdirectory_events_query_grid], [nexdirectory_events_bento_grid], [nexdirectory_events_ajax_search], and [nexdirectory_quick_search]. These are useful components, not replacements for the canonical route pages.
Connect submissions, workspaces, saved items, and accounts
Create pages for [nexdirectory_submit], [nexdirectory_my_listings], [nexdirectory_saved_listings], [nexdirectory_whos_attending], [nexdirectory_notifications], [nexdirectory_account], and [nexdirectory_auth]. Their labels adapt to My Events, My Listings, My Jobs or My Items Selling.
Pages for paid boosts, advanced organiser reports and the installable web app belong to Pro workflows. Connect those addresses only when the separate Pro add-on is enabled and the feature is part of your plan.
Keep privileged screens available but appropriately protected
Use [nexdirectory_moderation_queue] for pending listings, reports and claims; [nexdirectory_user_management] for user operations; [nexdirectory_organizers] for the organiser directory; and [nexdirectory_claim_listing] for claim requests. Keep moderation and user-management pages out of public menus.
A claim page also needs the Claim Listing route connected. NexDirectory appends an event_id query value when linking a claimable listing to that page. Do not remove that query value in redirects or caching rules.
Create and connect each page once
Create one WordPress Page for the screen
Use a clear title and the profile-aware slug. Keep full-screen views separate so visitors never land in two competing interfaces.
Insert the matching shortcode
For example, use [nexdirectory_listings_map] on Map and [nexdirectory_account] on Account. Preview the page to confirm the interface appears.
Publish and copy the complete address
Open the published page and copy its permalink, including any subdirectory used by the WordPress installation.
Connect the address to its route
Paste the permalink into the matching field under Routing & Page URLs, save, then use a front-end button to reach it.
Test both public and member states
Check the page while signed out and signed in. Test redirects, submission buttons, saved items, account actions, moderation access and the mobile menu.
Canonical page checklist
- Archive page renders the listing archive
- Map page renders markers and filters
- Calendar page uses the calendar shortcode
- Submit and workspace pages are separate
- Account and Login / Sign Up URLs are connected
- Saved-items and attendee pages use the right profile wording
- Moderation and claim pages enforce access rules
- Navigation uses the connected canonical URLs
Questions you may have
Can I use the event shortcode names on a Directory profile?
Yes. NexDirectory registers event names and listing aliases for compatibility. For new canonical pages, the listing aliases are a clearer profile-neutral choice.
Why does a button redirect to the wrong page even though my shortcode works?
The shortcode renders the view, but redirects use the configured Routing & Page URLs or profile fallbacks. Connect the published page URL to the matching route field.
Can I add these shortcodes through Elementor?
Yes. When Elementor is loaded, NexDirectory registers a widget category and shortcode-backed widgets. Regular WordPress Pages remain fully supported.
Why should I use the archive page instead of a WordPress post archive?
The NexDirectory archive shortcode supplies the directory filters, cards and profile-aware experience. Use that published page as the canonical archive route.