Record the exact error
Copy the full browser/server message, route, order ID, Website ID or validation line where applicable.
▤ OMEGA WEB PRO DOCUMENTATION • TROUBLESHOOTING
Find the Failed Layer. Fix the Actual Cause.
Omega Web Pro spans browser UI, server-side generation, temporary preview delivery, Stripe checkout, permanent licence records, private customer accounts, licensed source editing and final deployment. Troubleshooting is fastest when you identify which layer failed instead of changing unrelated files.
Builder diagnosticsGeneration recoveryPreview asset healthCheckout statesAccount/licence recordsEditor validationDeployment checks
SYMPTOM • LAYER • CHECK • FIX • RETEST
OMEGA TROUBLESHOOTING MAP● CURRENT PLATFORM REFERENCE
DocumentationStart HereBuilderPreviewCheckoutMy AccountWebsite EditorZIP Re-editWordPressFormsDeployment
✓ Identify layer✓ Preserve paid records✓ Retest exact workflow
First principles
Before changing code, preserve evidence and identify the failing stage.
Randomly replacing multiple files at once makes root-cause diagnosis harder.
Identify the stage
Builder input, generation, preview, purchase, account, editor, export or production hosting.
Change one thing
Apply the smallest relevant fix.
Retest the same path
Repeat the exact action that previously failed.
Builder problems
If Builder will not start or generate, separate browser validation from server generation.
Check the project specification and generation state before assuming the renderer is broken.
Required input
Confirm required business/domain/platform fields are valid and the generated page total is within the current 120-page limit.
Uploads
Check file type/size and whether uploaded images/supporting material are accepted.
Planning
If remote AI planning fails, confirm the fallback path or backend configuration rather than exposing API keys in JavaScript.
Continuation
If a checkpoint fails, use available retry/recovery rather than starting a duplicate build immediately.
Preview problems
If the generated preview is broken, inspect CSS, JavaScript and images separately.
The preview health gate exists specifically to prevent a broken generated project from being treated as ready.
Unstyled page
Confirm generated stylesheet path/existence and preview delivery.
Buttons/interactions fail
Check generated JS path, browser console errors and blocked scripts.
Broken images
Check generated filenames, srcset/picture paths and preview asset access.
Preview page missing
Check whether the requested generated page exists in the build architecture and temporary preview publication completed.
Checkout problems
Treat pending, open, expired and paid states differently.
Do not manually mark an order paid because a browser redirect looked successful.
Pending order exists
Use Proceed to Checkout to resume the existing session when available.
Abandoned checkout
Use Delete Pending Checkout only for unpaid orders; this attempts to expire the Stripe session where available.
Checkout link fails
The session may be expired/invalid; create a legitimate new purchase attempt rather than editing paid records.
Paid but licence missing
Preserve the Stripe/order evidence and contact support so server-side payment/licence reconciliation can be investigated.
Account problems
If data is missing, verify ownership linkage rather than creating fake duplicate records.
Licence and purchase data are permanent commercial records.
Cannot sign in
Use forgot-password/reset flow; remember there is no public self-registration.
Licence missing
Check that the signed-in purchaser account is the one linked to the paid order/licence.
Purchase history missing
Use the actual paid order/licence records as the source of truth; do not invent a new purchase entry.
Email change pending
Complete the verification step sent to the new address before expecting the login email to change.
Editor problems
Editor errors are usually authorization, validation, canonical protection or preview issues.
Read the Omega Live Validation message before trying to bypass it.
Website not available
Confirm the Website ID belongs to the authenticated active customer licence.
Blocking line
Correct the exact highlighted syntax/data/security issue before Preview or Save can proceed.
Valid HTML5 tags blocked
If a validator incorrectly rejects standard tags, update the validator rules rather than deleting valid page structure.
Canonical locked
The root host must remain the licensed domain; internal paths may change under that host.
PHP not executing in preview
Expected behavior: customer-edited PHP is not executed by Website Editor preview.
Need prior version
Use Version History when a saved revision needs to be revisited.
Licensed ZIP problems
Uploaded re-edit ZIPs must prove they belong to the signed-in account/licence/domain.
The validation is meant to stop unrelated projects from being imported as a purchased website.
Use an Omega licensed ZIP
Upload a ZIP previously downloaded through the licensed Omega workflow.
Identity validation
Account, Licence ID, Website ID, normalized domain and Omega signature/project identity must match.
Corruption
If the ZIP was modified/corrupted, return to the latest known-good licensed export if available.
Keep latest export
Save the newest licensed ZIP safely after important generation/edit cycles.
WordPress installation
WordPress failures often come from incomplete installation or environment mismatch.
Install the generated package as a WordPress project, not as a static HTML folder.
Environment
Confirm WordPress/PHP/server compatibility.
Theme
Install/activate the generated theme correctly.
Installer/import
Run the generated setup/import workflow according to the included instructions.
Forms/search
Confirm WordPress-native features were installed and no obsolete Pure HTML endpoint references remain.
Permalinks
Refresh WordPress permalink/rewrite settings if routes return unexpected 404s.
Debug logs
Use WordPress/PHP/server logs when a white screen or fatal error occurs.
Email/form problems
A form can submit successfully in the browser and still fail later in the mail chain.
Trace request → server handler → SMTP/wp_mail → recipient delivery.
Request
Confirm expected endpoint/action and required fields.
Server handler
Check PHP/WordPress errors.
Authentication
Check private SMTP credentials/provider requirements.
Deliverability
Check sender alignment, SPF/DKIM/DMARC and spam filtering.
Live site problems
If the downloaded site worked in preview but not on hosting, inspect the deployment environment.
Common causes include path nesting, case sensitivity, permissions, server modules, CDN cache and DNS.
Wrong folder
Ensure the site is not inside an extra wrapper folder under public_html/document root.
Filename case
Linux hosting is case-sensitive; HTML references must match actual filenames.
Permissions
Typical public directories 755/files 644; avoid 777.
Cache/CDN
Purge stale CDN/server/browser cache after replacing important assets.
HTTPS/mixed content
Update production URLs and enforce HTTPS consistently.
Routes
Verify files exist, rewrites are correct and links were not renamed without updating references.
When to contact support
Escalate with enough evidence to reproduce the problem.
Good diagnostic information makes support materially faster.
Exact error
Provide the full error text and time.
Page/action
Provide the Omega page/route and the action performed.
Safe identifiers
Provide Order ID, Licence ID or Website ID when relevant—but never passwords, secret keys or card details.
Reproduction steps
List the smallest sequence that consistently produces the problem.
Omega Web Pro documentation
If the exact failing layer is still unclear, contact support with the evidence.
Include the error, route/action, relevant safe project/order/licence identifier and reproducible steps—never passwords or secret keys.