Reproduce the problem, then isolate one layer
Begin with the affected address, user role, listing and time. Then open NexDirectory Diagnostics to review connected pages, map requests, scheduled tasks and environment warnings. Free and Pro share this basic method; only investigate Pro payments, notification or digest scheduling, team workflows or Chrome-draft AI when the separate Pro add-on and that feature are actually active.
Do not start with a reset
Most failures have a focused cause: the wrong connected page, a missing shortcode, invalid coordinates, a Pending listing, insufficient permission, a blocked map request, an incorrect provider key or an email-delivery problem.
Fix blank pages, shortcode text, wrong redirects, and 404s
Confirm the Page is Published and contains a registered NexDirectory shortcode. If the literal shortcode appears, confirm NexDirectory is active and the tag is spelled exactly. Then compare the permalink with Settings → General → Routing & Page URLs; buttons and redirects use those connected values or profile fallbacks.
For a listing permalink 404, verify the record is published and the events single rewrite is present. Saving Settings → Permalinks once safely refreshes WordPress rewrite rules. Do not repeatedly flush rewrites on every request.
Separate provider, REST, coordinate, and filter failures
Open the map REST URL shown in Diagnostics and check for a successful response. A working base map with no markers usually points to listing status, coordinates, bounds/radius, filters, or request limits. A completely missing tile layer points more often to provider settings, credentials, network policy, attribution configuration, or a JavaScript error.
Check representative records for numeric latitude and longitude, then reset all filters and move the map to their area. Test the configured provider connection from settings. Remember that browser “near me” needs location permission and secure browser behaviour; a denial should not break manual search.
Trace permissions, status, cron, payment, and mail
A blocked submitter should be checked for login, profile operating mode, role capability, first-submission verification, honeypot/rate-limit state, reCAPTCHA, and required fields. A missing public listing may simply be Pending or Draft; inspect the Moderation Queue and moderator notes.
For essential Free emails, send a test message and check the mail transport, provider restrictions and spam folders. With Pro active, also check the template, per-listing override and reminder schedule. For imports, confirm the CSV or JSON size, mapping preview and duplicate result; for Pro Chrome-draft AI, check the connected draft and provider configuration. For Pro tickets, compare Test or Live mode with the matching gateway credentials.
Find the cause without making the problem larger
Write a reproducible example
Record the address, time, account role, sign-in state, listing name or ID, expected result and actual result. Repeat it in a private browser before changing settings.
Read Diagnostics in context
Review must-fix and needs-review items, connected routes, map request, scheduled tasks and environment limits. Focus on checks related to the symptom.
Test the smallest useful unit
Try the page and shortcode for routing, one known coordinate for maps, one Pending listing for moderation, one test email for delivery or one Pro sandbox checkout for payment.
Capture useful evidence
Note the exact on-screen message and, when needed, the relevant runtime or browser request error. Remove passwords, secret keys, personal details and payment data before sharing a screenshot.
Make one reversible correction
Fix the specific route, status, coordinate, permission, provider mode or mail setting, then repeat the same test before changing anything else.
Safe troubleshooting checklist
- A current backup exists before repair work
- Exact URL, time, user, and listing ID are recorded
- Diagnostics has been reviewed
- Canonical route and shortcode match
- Post status and permissions are known
- REST/provider response is tested separately
- Runtime and browser errors are captured safely
- Only one controlled change is tested at a time
Questions you may have
Why does the map page load but show no listings?
Check published status, latitude and longitude, the current bounds or distance centre, filters and request limit. Then test the map response shown by Diagnostics.
Why can an administrator submit but a normal user cannot?
Administrators bypass several access gates. Check User-Generated versus Single-Organisation mode, the submitter/author capability toggle, login, first-submission verification, and form protection messages.
Why is a newly submitted listing missing from the public archive?
Completed front-end submissions enter Pending. Approve it from the Moderation Queue; Request Changes or Reject returns it to Draft.
Should I deactivate and reactivate the plugin to fix every issue?
No. First isolate routes, data, permissions, REST, provider settings, scheduling, or email. Reactivation is rarely the first useful diagnostic and can distract from the actual cause.