What you will set up.
Narrow down routing, email, maps, security and integration problems before asking for support.
Before you begin
Back up the site, use staging and gather any provider credentials without placing secrets in page content.
ExploreWhat you will verify
Check the public result, affected account roles, empty and error states, and any schema, email or notification output.
ExplorePlan and package notes
Diagnostics, security, spam protection and performance improvements remain part of Free. Pro-specific services should be tested with the Pro companion plugin active.
Put this guidance into practice.
Capture the environment
Record the WordPress, PHP, theme and NexDirectory versions plus the page and user role affected. Never include passwords or private keys.
Test one dependency at a time
Check permalinks and pages first, then email, maps, reCAPTCHA and any optional provider used by the failing workflow.
Create a reproducible report
Write the shortest sequence that triggers the problem, the expected result, the actual result and any safe diagnostic message.
Common questions.
Should I do this on a live site?
Use staging first, particularly for imports, payments, routing, profile changes and external service credentials.
Does this require Pro?
No. Diagnostics, security, spam protection and performance improvements remain part of Free.
Where can I troubleshoot the result?
Use the support centre and diagnostics guide, including your exact WordPress, PHP and NexDirectory versions.