▤ 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.

Contact Support → Documentation Hub Customer Support

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

Omega Hosting • two dedicated, protected website editors

Separate editing workspaces for Pure HTML and native WordPress websites.

Omega uses the verified website's hosting record, platform and authorised Website ID to select its editor. The Pure HTML and WordPress tools are separate OVHcloud pages, not two modes of the older combined website-editor.php. Sign in through My Account and select your purchased website; do not choose a platform by changing the URL.

Pure HTML Website Editor

dashboard.omegawebpro.com/website-editor.php

Work with the site's authorised HTML, CSS, JavaScript and supporting project files. Use the code editor with Save, Undo, Redo, Find and Replace, a desktop/tablet/mobile sandbox preview, validation, version history, updated licensed ZIP export, Builder-source adoption and guarded Deploy / Update Live Website.

The selected Pure HTML site can also access its eight applicable Omega hosted Website Plugin implementations and compatible third-party HTML add-ons through the editor's website-specific plugin panels. The embedded Omega AI Agent assists with code, validation explanations and reviewable proposed fixes; customers approve and save changes themselves.

Native WordPress Website Editor

dashboard.omegawebpro.com/website-editor-wordpress.php

Work with native WordPress Pages and Posts, their HTML/block content and responsive WordPress preview, plus the integrated WordPress Manager for supported site administration. WordPress engine dashboards, the installed-plugin repository and one-at-a-time plugin administration workspace operate within the authorised editor.

Builder-generated WordPress theme/content changes, validation and live publication follow the WordPress-specific staging and deployment process—not the Pure HTML static-file editor. Saved WordPress database content and a published WordPress theme are distinct operations. The Omega AI Agent is also embedded here for page/code guidance, validation help and controlled, reviewable repair suggestions.

Both editors retain customer/Website ID checks and protected workflows. Each paid Omega Hosting purchase covers one website; only the eight engines appropriate to that website's detected platform apply. Both pages include the floating bottom-right Omega AI Agent for public web research with sources, NativeAI knowledge and planning, six-stage Builder guidance, code explanations, error/log review, website-scoped validation help and staged repair proposals. Customer-specific account, hosting and source assistance require a verified session and authorised Editor context; suggested changes require explicit review, saving and validation before publication, never silent live edits. Lifetime licence editing and licensed ZIP rights are separate from the paid hosting entitlement required to deploy. Hosting, editing, staging and publication remain subject to the selected site's permissions, entitlements and validation checks.

New: lifetime-licensed WordPress editing without Omega Hosting

Private WordPress Website Editor — for WordPress lifetime licence holders without Omega Hosting

A customer who owns a lifetime licence for a WordPress website but does not have active Omega Hosting for that same Website ID uses the dedicated Private WordPress Website Editor. Sign in, select your authorised website in the customer Dashboard, and use its Edit Website action. This is a private project workspace, not a hosted WordPress installation.

For a lifetime-only WordPress site, open the private Editor through the authenticated Dashboard. If no project appears, check the licensed Website ID, account ownership and latest Builder package. If preview differs from live WordPress, remember the preview is sandboxed package HTML/CSS and does not execute PHP, plugins or a WordPress database. Private Omega dashboards report package findings, not hosted scans or real-time traffic. Check private validation and version history before exporting the latest ZIP.

Three distinct editing paths: website-editor.php is the Pure HTML Editor; website-editor-wordpress.php is for an authorised WordPress website with eligible active, provisioned Omega Hosting (including lifetime-licensed customers who also have that hosting); website-editor-wordpress-private.php is for lifetime-licensed WordPress customers without active Omega Hosting for that website. The Dashboard determines the correct editor from the website's platform and entitlements.

Hosting boundary: a lifetime licence allows the private WordPress project to be edited and its ZIP exported without buying Omega Hosting. It does not include live hosting, public deployment, live WordPress administration, live plugin execution, visitor-traffic metrics or server-side WordPress PHP rendering. Publishing to Omega Hosting requires a separate, eligible hosting entitlement for that same website.

Open your customer Dashboard to select the licensed website. The authorised private workspace is Private WordPress Website Editor (website selection and sign-in required).

First principles

Before changing code, preserve evidence and identify the failing stage.

Randomly replacing multiple files at once makes root-cause diagnosis harder.

Record the exact error

Copy the full browser/server message, route, order ID, Website ID or validation line where applicable.

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.

INPUT

Required input

Confirm required business/domain/platform fields are valid and the generated page total is within the current 120-page limit.

MEDIA

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.

CSS

Unstyled page

Confirm generated stylesheet path/existence and preview delivery.

Buttons/interactions fail

Check generated JS path, browser console errors and blocked scripts.

IMG

Broken images

Check generated filenames, srcset/picture paths and preview asset access.

404

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.

STRIPE

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.

LIC

Licence missing

Check that the signed-in purchaser account is the one linked to the paid order/licence.

BUY

Purchase history missing

Use the actual paid order/licence records as the source of truth; do not invent a new purchase entry.

MAIL

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.

TAG

Valid HTML5 tags blocked

If a validator incorrectly rejects standard tags, update the validator rules rather than deleting valid page structure.

CAN

Canonical locked

The root host must remain the licensed domain; internal paths may change under that host.

PHP

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.

Editor troubleshooting • action by action

A change is not visible: determine which stage actually succeeded.

Pure HTML: code looks correct but live website is unchanged

Confirm you selected the correct purchased Pure HTML website and saved the affected file—not just an unsaved buffer or sandbox preview.
Run the authoritative Validate Licensed Website action; check exact errors and any canonical-domain restriction.
Confirm whether Generate Updated Licensed ZIP only produced an export or Deploy / Update Live Website actually completed for eligible Omega hosting.
After confirmed deployment, reload the public URL and consider normal browser/CDN cache. If the host/site ID is wrong or the operation failed, stop and use the error details.

WordPress: source saved but the live view differs

Verify you are on website-editor-wordpress.php with the expected verified WordPress site.
Select the same Page/Post and use Reload from WordPress to compare the live database version with the editor buffer. An unsaved private source-package edit does not necessarily change WordPress database content.
Check Live WordPress Preview for that Page/Post. A static generated snapshot is not the authoritative WordPress render.
If you changed a theme, Builder package or template instead of a Page/Post, inspect the WordPress-specific staging/validation/deploy status; do not confuse it with Save to WordPress for content.

For either platform, record the error and action before refreshing or retrying. Do not blindly overwrite live files or replace the customer's WordPress database to force a preview update.

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.

ZIP

Use an Omega licensed ZIP

Upload a ZIP previously downloaded through the licensed Omega workflow.

SIG

Identity validation

Account, Licence ID, Website ID, normalized domain and Omega signature/project identity must match.

FILE

Corruption

If the ZIP was modified/corrupted, return to the latest known-good licensed export if available.

LATEST

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

Theme

Install/activate the generated theme correctly.

SETUP

Installer/import

Run the generated setup/import workflow according to the included instructions.

FORM

Forms/search

Confirm WordPress-native features were installed and no obsolete Pure HTML endpoint references remain.

LINK

Permalinks

Refresh WordPress permalink/rewrite settings if routes return unexpected 404s.

LOG

Debug logs

Use WordPress/PHP/server logs when a white screen or fatal error occurs.

WordPress hosting • account and editor checks

If WordPress setup or live editing fails, check the correct account, Website ID and editing path.

If the WordPress onboarding email is not received, verify the WordPress site's owner email and provisioning status, check spam/junk and distinguish this message from the Omega account activation or hosting/DNS setup email. Request a new WordPress password setup link through that site's own /wp-login.php?action=lostpassword route if direct WordPress access is needed; never send support your password or a recovery token.

When hosting is newly purchased, distinguish hosting allocation, automatic WordPress initialisation, owner invitation email and DNS/SSL connection. The lifecycle checks eligible provisioned websites periodically, so an owner email may follow allocation rather than arrive at checkout. Do not run another WordPress installation or replace wp-config.php just because the email has not yet appeared. Check the correct purchased site’s status and contact Omega support if provisioning or email delivery remains incomplete.

Website missing from the Editor

Sign into Omega My Account and select the correct purchased, entitled WordPress Website ID. If the site is absent or displayed as Pure HTML, verify the paid hosting allocation and recorded platform rather than copying another Website ID.

Changes not visible on live WordPress

First confirm you opened the separate WordPress Editor (website-editor-wordpress.php), rather than the Pure HTML Editor (website-editor.php). Check whether you edited the WordPress Source Code panel and clicked Save to WordPress, or instead edited the separate static HTML snapshot. Use Live WordPress Preview, then refresh the live site and consider page caching. Native theme deployment is separate.

Manager or plugin dashboard not available

Confirm the selected website is an authorised WordPress hosting site and that the plugin is installed there. Supported original plugin dashboards run in scoped sessions; site permissions, compatibility and security checks may restrict individual actions without requiring an additional WordPress login.

Plugin and AI diagnostics

Search, enable and dashboard failures need different checks.

Plugin appears missing or incompatible

Check the authorised Website ID, paid hosting state and detected platform first. An HTML website cannot activate a WordPress plugin, and a WordPress website does not receive HTML-only managed add-ons. Omega's eight hosted plugins per platform are separate from third-party repository results and separate from the Builder's sixteen generation engines.

Search works but a third-party package is not installed

A result from the public cdnjs or npm directory is discovery-only. For WordPress.org, select a supported compatible official package and perform the requested authorised installation; the full public directory is searchable and paginated, but search results are not automatically installed. Check installation status on the selected site before activating it.

Enable, mode selection or Open Dashboard fails

Record the plugin, tab and clicked control; note the previous and requested states, the exact message and whether a page refresh reverts the value. A WordPress Performance profile such as Conservative, Balanced or Aggressive is a plugin setting, not a Builder engine selection. An error from the hosted operation should be escalated with safe diagnostic evidence; do not bypass server-side permission checks or repeat destructive operations.

Omega AI suggestion was not applied

Chat replies, research findings, Apply to Builder, staged Apply to Editor candidates, authorised Save, validation and Deploy are different steps. Confirm each completed action. Review all affected files before using Save All AI Fixes where offered; do not assume a proposal or a staged candidate changed live production.

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.

REQ

Request

Confirm expected endpoint/action and required fields.

PHP

Server handler

Check PHP/WordPress errors.

SMTP

Authentication

Check private SMTP credentials/provider requirements.

DNS

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.

ROOT

Wrong folder

Ensure the site is not inside an extra wrapper folder under public_html/document root.

CASE

Filename case

Linux hosting is case-sensitive; HTML references must match actual filenames.

755

Permissions

Typical public directories 755/files 644; avoid 777.

CACHE

Cache/CDN

Purge stale CDN/server/browser cache after replacing important assets.

SSL

HTTPS/mixed content

Update production URLs and enforce HTTPS consistently.

404

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.

ERR

Exact error

Provide the full error text and time.

URL

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.

STEP

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.

Contact Support →All Documentation

OMEGA WEB PRO HOSTING

Troubleshoot the hosted lifecycle by layer

For recurring plans, distinguish Builder generation, preview, checkout, hosting entitlement, project workspace, staging, production, DNS/HTTPS, database, SFTP and backup states. A successful payment does not by itself prove every deployment step completed.

Customer control plane

Use My Account for commercial/account state and the Omega Web Pro Hosting Dashboard for operational hosting state. Preserve exact errors, project/website identifiers and the failing stage when contacting support; never send passwords, private keys or secret credentials.

Managed hosting plans

Monthly US$9.99 · Annual US$99 · Two Years US$179. Managed Omega Web Pro Hosting remains available while the recurring plan is active.

∞

Lifetime software licence

US$999 one time for permanent supported build, edit and export rights for one licensed website domain. Production hosting is separate and can be added when required.

Current account, billing & hosting architecture

My Account, Billing Centre and the Hosting Dashboard are connected but have different jobs.

My Account is the authenticated commercial identity centre. The Billing Centre is the Stripe-hosted billing entry point for a usable canonical production Stripe customer. The Full Hosting Dashboard is available to websites with an active managed-hosting entitlement. A lifetime single-domain software licence remains independent from optional hosting status.

Billing & recovery

Recurring invoice state can restrict paid hosting actions without removing the customer identity. Billing recovery can remain available through My Account/Billing Centre.

Billing documentation →

Hosting operations

Provisioning, DNS/SSL connection and entitled operational hosting controls are handled through authenticated Omega customer interfaces.

Hosting documentation →

Lifetime rights

The US$999 lifetime licence preserves supported same-domain build, edit and licensed export rights. Production hosting is separate.