Required project fields
Confirm the domain, business information, platform target and other required fields are valid before starting generation.
◉ OMEGA WEB PRO SUPPORT • FROM FIRST BUILD TO LIFETIME EDITING
Get Help with the Exact Stage That Needs It — Builder, Checkout, Account, Editor or Deployment.
Omega Web Pro support covers the complete website lifecycle: Universal Website Studio, AI-assisted planning, generation checkpoints, responsive Builder preview, secure Stripe checkout, NZ$999 lifetime single-domain licensing, purchase-created customer accounts, Pending Checkout, Purchase History, lifetime Builder regeneration, licensed ZIP re-editing, the private Website Editor, exact-line validation, version history, Pure HTML and WordPress packages, forms, SMTP, hosting and deployment.
Builder support
Generation + preview support
Stripe + checkout support
My Account + licence support
Website Editor support
Pure HTML + WordPress
Deployment guidance
IDENTIFY • DIAGNOSE • FIX • RETEST • ESCALATE
SUPPORT MAP● COMPLETE CUSTOMER LIFECYCLE
Builder + GenerationSpecification, uploads, AI planning, checkpoints, images and platform rendering.
Preview + ValidationBuilder preview health, Website Editor preview and exact-line validation.
Purchase + My AccountStripe, pending checkout, purchase records, licences, account access and security.
Editing + Re-editingBuilder regeneration, licensed ZIP restore, direct code editing, versions and updated ZIPs.
Pure HTML + WordPressPackage-specific installation, forms, SMTP and platform troubleshooting.
DeploymentDocument root, hosting, DNS, HTTPS, permissions, caching, backups and live testing.
73Industry starting points
105Built-in page types
120Current pages/build
2Live-preview workflows
14Editor validation responsibilities
∞Same-domain lifetime editing
Start here before emailing support
Identify the stage that failed and preserve the exact evidence.
Omega spans several separate systems. A Builder input problem is not the same as a Stripe problem, an editor validation problem or a hosting problem. Support is fastest when the failing layer is identified first.
Copy the exact error message.
Include the complete visible message, validation line, order status or server/browser error rather than paraphrasing it.
Identify the page and action.
State whether you were using Builder, preview, checkout, My Account, Website Editor, ZIP re-editing, WordPress installation or the deployed website.
Include the relevant safe identifier.
When useful, include Order ID, Licence ID or Website ID. Do not send passwords, API keys, SMTP secrets, Stripe secret keys or payment-card details.
Describe the smallest reproducible sequence.
List the exact steps that lead to the problem so the same path can be tested.
Change one thing at a time.
Avoid replacing several application files at once unless the support fix specifically requires a coordinated file set.
Retest the same workflow after the fix.
Confirm the original failing action now succeeds rather than assuming the issue is solved because the page loads.
Never send secrets to support: do not email passwords, full card numbers, API keys, Stripe secret keys, SMTP passwords, database passwords, private signing keys or other authentication secrets.
Builder + generation support
Troubleshoot specification, uploads, AI planning and staged generation separately.
The Universal Website Studio creates the authoritative project specification, but generation happens through server-side stages. A problem in one stage does not automatically mean the whole Builder is broken.
Page-count limit
The current browser and server generation paths support up to 120 generated pages. Repeatable services, locations, products, case studies, team members and articles also count toward the final project total.
Source/supporting files
Check supported file type, file size, ZIP contents and path/security restrictions if supporting material is rejected.
Uploaded media
Confirm the source image format is supported and the hosting image libraries can process it. Source quality also limits the quality of responsive derivatives.
Remote AI planning
If Groq or another configured provider fails, diagnose provider configuration separately. Omega Local Assist can keep the planning path operational when appropriate.
Checkpoint failure
Large builds use continuation/checkpoint stages. If a continuation fails temporarily, use the available retry/recovery path rather than starting duplicate builds immediately.
Pure HTML renderer
Confirm Pure HTML was the selected production target and inspect generated HTML/CSS/JavaScript and supporting files.
WordPress renderer
Confirm WordPress was selected and troubleshoot the generated theme/content/setup package as WordPress—not as a static HTML export.
Preview + validation support
Omega has two different live-preview systems, and they fail for different reasons.
Builder preview validates a newly generated website before purchase. Website Editor preview mirrors valid direct source edits for an authenticated licensed project.
Builder Live Preview
If the generated preview is incomplete, inspect the actual asset health:
- Unstyled: check generated CSS existence/path and preview delivery.
- Interactions missing: check generated JavaScript and browser console/network errors.
- Broken imagery: check generated filenames, picture/srcset references and image delivery.
- Purchase/export unavailable: confirm required CSS, JavaScript and image health signals passed.
Website Editor Live Preview
If a code change does not enter preview, read the Omega Live Validation result first:
- Correct the exact highlighted blocking line.
- Check which of the 14 validation responsibilities raised the issue.
- Remember customer-edited PHP is intentionally not executed in editor preview.
- Do not bypass canonical-domain protection or security validation.
Important: if a validator incorrectly rejects legitimate standard HTML5 structure, the correct fix is to update the validator rules—not to damage valid HTML merely to silence the validator.
Stripe checkout + pending order support
Pending, open, expired and paid checkout states must be handled differently.
Never manually convert an order to paid because a browser page looked successful. Payment and licence issuance rely on authoritative server-side state.
Pending Checkout exists
An unpaid account-linked licence order can appear in My Account with its domain, Order ID, created time, platform and amount.
Proceed to Checkout
If the existing Stripe Checkout Session is still open, use Proceed to Checkout to resume that exact pending order rather than creating a duplicate.
Delete Pending Checkout
Use this only for an abandoned unpaid order. Omega removes the pending order and attempts to expire/cancel the active Stripe Session where available.
Stripe link no longer opens
The Session may have expired or become invalid. Start a legitimate new checkout attempt rather than editing completed commercial records.
Payment made but licence missing
Preserve the actual Stripe/order evidence and contact support so payment/licence reconciliation can be investigated. Do not manufacture a duplicate paid purchase record.
Paid records are protected
Completed payments, Purchase History, issued Licence IDs, Website IDs and permanent licensed domains are not deletable through the Pending Checkout control.
My Account support
Account issues usually involve authentication, ownership linkage or permanent commercial records.
There is no public Create Account registration flow. The customer account is created or associated after confirmed paid licence purchase.
Cannot sign in
Use the forgot-password/reset-by-email workflow. Confirm you are using the purchaser account email associated with the actual licence.
Licence missing
Confirm the signed-in account is the account linked to the paid order and permanent Licence ID / Website ID relationship.
Purchase History missing
Investigate the actual paid order/licence linkage rather than inserting a synthetic duplicate purchase record.
Email change not complete
A requested login-email change does not become active until the new address completes the secure verification step.
Permanent IDs
Customer Account ID, Licence ID, Website ID and permanent licensed domain are protected commercial identity records.
Same-domain rights
A future generation/export for the same permanent licensed domain is not a new NZ$999 purchase.
Website Editor support
Authorization, live validation, canonical protection and project-level export are the key support boundaries.
Website Editor is limited to authenticated purchased projects. It is not a public arbitrary-code execution environment.
Website ID not available
Confirm the active Website ID belongs to the authenticated account and has a valid purchased licence relationship.
Code change blocked
Correct the exact highlighted issue before changed Preview/Save can proceed.
Validation area
The editor maps issues across Website Specification, Brief Normalizer, AI Planning, Plan Validation, Site Architecture, Content Conversion, Design System, Image Engine, SEO + Schema, Accessibility, Forms + Backend, Deployment, Quality / Metrics and Final Validation.
Syntax/data errors
Check HTML, CSS, JavaScript, JSON/JSON-LD, XML and malformed-data conditions such as invalid UTF-8 or NUL bytes.
Canonical-domain block
The home canonical host must remain the permanently licensed root domain. Internal filenames and paths can change under that host when updated consistently.
PHP does not execute in preview
This is expected behavior. Customer-edited PHP is not executed inside the live preview sandbox.
Need a previous revision
Use Website Editor Version History for accepted saved revisions where the interface provides restore access.
Updated ZIP fails
Run whole-project validation and resolve any licence/canonical/project issues before generating the updated signed licensed ZIP.
Lifetime re-editing + licensed ZIP support
Builder regeneration and Website Editor are different lifetime editing paths.
Choose the path that matches the change instead of forcing every update through the wrong workflow.
Builder regeneration path
Use Builder for architecture, design-system, content-direction, platform or broader specification changes. A supported licensed ZIP can be uploaded through My Account and must pass account, Licence ID, Website ID, domain and Omega project-signature checks.
Website Editor path
Use Website Editor for direct supported source-file changes, real-time code preview, live validation, versioned saves and updated licensed ZIP generation.
Keep your latest licensed ZIP: temporary Omega build workspaces are not intended to replace your own portable backup. Keep the latest downloaded licensed ZIP and normal production-site backups.
Platform-specific support
Always identify whether the current project is Pure HTML or WordPress before troubleshooting deployment.
The two outputs have different runtime and installation assumptions.
Pure HTML support
- Check generated HTML/CSS/vanilla JavaScript.
- Check responsive image paths and local assets.
- Deploy files at the correct document root.
- Configure compatible PHP/backend only where server-side form handling is actually used.
- Keep SMTP credentials private and server-side.
WordPress support
- Use a compatible WordPress environment.
- Install/activate the generated theme correctly.
- Use the generated setup/import/content package as instructed.
- Confirm WordPress-native forms and wp_mail behavior.
- Refresh permalink/rewrite settings when routes unexpectedly 404.
Deployment + hosting support
If the site worked in preview but fails on hosting, inspect the production environment.
Hosting paths, case sensitivity, permissions, DNS, HTTPS, cache/CDN behavior, PHP configuration and third-party services can all introduce deployment-only problems.
Wrong folder level
Make sure index.html or the WordPress install is not buried inside an accidental extra wrapper folder under the intended document root.
Filename case
Linux hosting is case-sensitive. Referenced paths must match the actual filenames exactly.
Permissions
A common public-site baseline is 755 directories and 644 files. Avoid 777. Where supported, private Omega storage can use tighter 750 directories / 640 files.
CDN/browser cache
Purge CDN, server and browser caches after replacing important CSS, JavaScript, PHP or image assets.
HTTPS + mixed content
Confirm the production hostname has a valid TLS certificate and that generated/external resources are loaded consistently over HTTPS.
DNS
Confirm the domain points to the correct hosting account and record changes have propagated.
Forms + email
Trace form request → server handler → SMTP/wp_mail → recipient delivery. A visible success message alone does not prove email arrived.
Production testing
Test navigation, forms, responsive layout, redirects, canonicals, sitemap, robots, schema, Lighthouse/Core Web Vitals, accessibility and security on the final live URL.
How to send a useful support request
Send enough information to reproduce the issue without sending secrets.
A precise support request can often eliminate several rounds of follow-up.
Exact error text
Copy the complete visible error or validation message exactly.
Omega page / route
State whether the issue occurred on Builder, preview, checkout, account, Website Editor, ZIP import, deployment or another route.
Action performed
Explain what you clicked or submitted immediately before the issue occurred.
Safe identifiers
Include Order ID, Licence ID or Website ID when directly relevant.
Reproduction steps
List the shortest repeatable sequence that causes the failure.
Do not send
Passwords, payment-card details, API keys, SMTP passwords, Stripe secrets, database passwords or private signing keys.
Example subject: Website Editor validation block — Website ID OWP-WEB-… — index.html line 24. A specific subject makes the request much easier to route than “website broken.”
Self-service support library
Use the documentation page that matches the workflow you are working on.
The documentation library is designed to answer detailed implementation questions before support escalation is necessary.
Getting StartedFirst build, preview, purchase, account activation and licensed export.Open guide →
Builder DocumentationComplete Universal Website Studio controls and generation process.Open guide →
Generation PipelineStages, checkpoints, renderers, quality gates, preview and export.Open guide →
Builder PreviewResponsive preview, CSS/JS/image health and purchase boundary.Open guide →
CheckoutPending orders, Stripe Sessions, verification and licence creation.Open guide →
My AccountLicences, purchases, pending checkout, profile and security.Open guide →
Website EditorDirect code editing, live preview, validation, versions and ZIP export.Open guide →
Lifetime Re-editingBuilder regeneration, ZIP restore and source-editing paths.Open guide →
Forms + SMTPPure HTML backend, private SMTP and WordPress-native form handling.Open guide →
DeploymentPure HTML/WordPress install, DNS, HTTPS, testing and backups.Open guide →
TroubleshootingFull diagnostic guide across Builder, account, editor and hosting.Open guide →
FAQDirect answers to 100+ common product and customer questions.Open FAQ →
Contact the right team
Use the channel that matches the request.
This keeps customer support, sales and general enquiries separated.
Technical Support
Builder, generation, checkout, account, licence, Website Editor, export and deployment issues.
support@omegawebpro.comSales
Pre-purchase questions, commercial enquiries and licence information.
sales@omegawebpro.comGeneral Enquiries
Company, website and general Omega Web Pro enquiries.
contact@omegawebpro.comFor legal matters: use legal@omegawebpro.com. Binding policies are available in the site footer and Documentation/FAQ resources.
Identify • Diagnose • Fix • Retest
Need technical help with a real Omega Web Pro project?
Email support with the exact stage, exact error, safe project/order/licence identifier when relevant and the smallest reproducible steps. Never include credentials or payment secrets.