TROUBLESHOOT OMEGA IMAGE ENGINE PRO · Pure HTML 2.0.1

Troubleshoot Omega Image Engine Pro

Troubleshooting guidance for Omega Image Engine Pro Pure HTML 2.0.1, based on its audited architecture and technical boundaries.

Common issues and corrective actions

Start with the least destructive correction. Restore/revert a high-impact change before experimenting further on a production site.

AVIF or WebP is unavailable

Open Status and confirm the active Imagick/ImageMagick or GD installation actually exposes the requested codec. Unsupported output must not be treated as a successful conversion.

A responsive variant is missing

Check that the source is registered in the Omega Media Library, the requested width is smaller/valid for the source, and the target directory is writable.

Responsive markup was not applied

Confirm the HTML file is eligible local markup, the Base URL/path mapping is correct, and the backup/apply workflow completed without write errors.

An image must not be deleted as a duplicate

Review duplicate preview. Registered Omega originals/variants and files referenced by site HTML/CSS are protected; do not bypass those protections.

Nginx private-area protection differs from Apache

Nginx ignores .htaccess. Recreate equivalent deny/protection rules in the Nginx server configuration.

General diagnostic sequence

  1. Confirm the installed product/version matches this documentation.
  2. Review the product Status/Settings page and confirm the listed requirements are met.
  3. Check the most recent logs, scan result, preview, batch status or stored evidence relevant to the failed operation.
  4. Revert or disable the most recent high-impact setting when the problem began after a configuration change.
  5. Re-test with caches/CDN layers cleared where they can affect the observed result.
  6. Collect exact error text, timestamps, affected paths/URLs and environment details before contacting support.

Technical boundaries

AVIF/WebP availability depends on the server image editor and installed codecs. Responsive variants improve delivery options but do not guarantee a particular Lighthouse/Core Web Vitals score. HTML rewrite support is for eligible local markup; unusual templating/runtime-generated markup may require manual integration. Nginx does not process .htaccess and therefore requires equivalent server configuration for web-deny protections.

Product page and commercial specification

Review the complete public-facing capability specification, pricing and licence information for Omega Image Engine Pro.

View Omega Image Engine Pro