35.1 Troubleshooting AIUNIFY Leads

Most AIUNIFY Leads operating issues can be narrowed down by checking the Website context, Language context, permissions, subscription availability, saved configuration, and AI configuration in a consistent order.

35.2 Recommended Troubleshooting Order

1. Confirm the correct Staff Member is signed in.
2. Confirm the correct Website is selected.
3. Confirm the correct Website Language is selected.
4. Confirm the user's Role contains the required permission.
5. Confirm the feature is available under the current subscription configuration.
6. Confirm required Website Pages or Languages already exist.
7. Confirm changes were saved.
8. For AI operations, confirm AI is configured and the connection works.
9. Open the generated public URL and test the actual visitor result.

35.3 Staff Member Cannot Sign In

If the credentials appear correct but the user receives:

You are not allowed to login. Please contact administrator.

the Staff Member's Allow Login setting is disabled.

An authorized administrator should review the Staff Member's Allow Login, Status, Role, and Password configuration.

35.4 Imported Staff Member Cannot Sign In

This can be expected immediately after a spreadsheet import.

The confirmed Staff Import workflow creates imported Staff Members with Allow Login disabled.

If login is required, edit the Staff Member individually and configure the appropriate login access, Role, and Password using an account authorized to assign Roles.

35.5 A Menu or Action Is Missing

AIUNIFY Leads uses permission-based menu and route access.

If one Staff Member sees a function and another does not, compare their Roles and required permissions before treating the difference as a software fault.

35.6 Subscription Feature Unavailable

Some Website modules are subject to subscription-module availability.

The confirmed message is:

This feature is not available in your current subscription plan.

Confirm the applicable subscription configuration before changing Roles or application settings.

35.7 AI Is Not Configured

If an AI generation request returns:

AI is not configured. Please configure AI settings first.

an authorized user should review AI Settings and use the supported Test Connection operation.

35.8 AI Generate Button Is Missing

For supported AI generation tools, verify:

1. AI features are enabled.
2. The user has ai_features_access or administrative authority.
3. AI is configured.
4. A Website is selected.
5. The workflow-specific Website Languages and Pages exist.

35.9 Website Has No Languages

AI workflows and multilingual content depend on Website Languages.

If the Website has no Languages, add the required Website Language records before attempting language-dependent Page, Settings, Builder, or AI operations.

35.10 Page Key Problems

Website Page Keys participate in public routing.

Use the supported lowercase letters, numbers, and hyphen format and avoid duplicate Page Keys within the same Website.

If a public custom Page returns a not-found result, confirm:

1. The Website Slug is correct.
2. The Page Key exists.
3. The Page Key belongs to that Website.

35.11 Home Page Protection

The Home page is foundational to the Website's normal landing behavior.

If attempting to remove the Home page is blocked, maintain the Home record and edit its content rather than trying to replace the Website's fundamental home Page Key casually.

35.12 Duplicate Website Builder Section

The Builder prevents the same applicable section from being duplicated for the same Page and Language in workflows where the section is designed to be unique.

A confirmed server message is:

This section has already been added for this page and language.

Locate and edit the existing section instead of creating another copy.

35.13 Section Changes Are Appearing on Other Pages

Review the Website's:

1. Use Same Header Across All Pages setting.
2. Use Same Footer Across All Pages setting.

When shared Header or Footer behavior is enabled, applicable changes can be synchronized across Website Pages.

35.14 Wrong Language Is Displayed Publicly

Review:

1. The Website's Default Language.
2. Whether the intended Language is configured for that Website.
3. The Website-specific visitor language cookie.
4. Website Settings for the selected Language.
5. Whether the public route supports an explicit language query for that page type.

35.15 Public Website Root Opens Login

In this confirmed deployment, the bare application root redirects to the administrative login page.

Use the Website's generated Landing Page URL as the authoritative public Website destination unless the deployment routing is intentionally changed.

35.16 Public Page Returns 404

For an ordinary Website Page, verify the requested Page Key actually belongs to the Website identified by the URL Slug.

AIUNIFY Leads intentionally rejects a Page Key that does not belong to that Website instead of displaying another Website's Page.

35.17 Legal Page URL Problems

For a Website Legal Page, verify:

1. The Website.
2. The Legal Page Slug.
3. The Website Language.
4. The Legal Page Status.
5. The generated Page URL rather than a manually constructed URL.

35.18 Deleting a Multilingual Legal Page

Critical: Legal Page deletion can remove the corresponding same-Slug Legal Page entries across the Website's languages.

Before deleting a Legal Page, inspect the same Slug in every Website Language and confirm that all corresponding versions should be removed.

35.19 Custom CSS or JavaScript Causes Display Problems

Custom CSS and Custom JavaScript can override or alter normal theme behavior.

If a Website began malfunctioning immediately after a Custom CSS or Custom JavaScript change:

1. Review the most recent custom-code change.
2. Temporarily remove or correct the suspect code.
3. Save the Website.
4. Reload the public Landing Page URL.
5. Retest desktop and mobile presentation.

35.20 Email Configuration Problems

After changing Email Settings, use Send Test Mail to a valid Email address.

If the test control is unavailable or disabled, confirm the supported Mail/SMTP configuration and applicable verification state.

35.21 Role Changes Cause Lost Access

A Role update synchronizes its permission set.

Removing permissions can therefore affect all Staff Members using that Role.

Before making broad changes:

1. Review who uses the Role.
2. Review the entire permission selection.
3. Avoid altering the protected Admin Role.
4. Verify another administrator retains management access.

35.22 AI-Generated Content Should Be Reviewed

AI Website, Page, Section, and Legal Page generation is an assistance workflow, not a replacement for human review.

Review generated material for:

1. Business accuracy.
2. Brand accuracy.
3. Correct links and calls to action.
4. Translation quality.
5. Layout and mobile presentation.
6. Legal accuracy where Legal Pages are involved.

35.23 Ongoing Operational Best Practices

1. Confirm Website and Language context before every major edit.
2. Use individual Staff Member accounts.
3. Apply least-privilege Roles.
4. Keep Website Slugs and Page Keys stable after public distribution whenever possible.
5. Review multilingual content in every configured Language.
6. Test Email after mail configuration changes.
7. Test AI after AI configuration changes.
8. Preview the actual public Landing Page URL after Website changes.
9. Test important Pages and Legal Pages after structural changes.
10. Review desktop and mobile presentation.
11. Review Staff Member and Role access periodically.

35.24 Final Operating Principle

Build in the correct Website context, control access through Roles, verify every Language, test the actual public URL, and review AI-generated content before relying on it publicly.

Following that operating sequence provides a reliable foundation for managing AIUNIFY Leads as a No Code Website & Landing Page Builder.