Start with the exact error
Record the installed IM-Press version, the action you attempted, the expected result and the exact message. Do not include passwords, license keys, private page content or customer information in public reports.
If installation or an upgrade fails
Stop after the first error. Keep the existing backup and current package intact. Do not delete the plugin, reinstall WordPress, or alter database tables as a general troubleshooting step.
If license activation fails
An activation error does not by itself mean the WordPress installation is broken. Record the precise error and whether this is a new activation or an existing site's retry. Do not remove server activation records or share the license key to investigate it.
If an imported page looks wrong
- Compare the draft with the original source.
- Check the selected template and whether the content is blocks or styled HTML.
- Check missing assets, external dependencies and mobile layout.
- Review the import/preflight output for skipped or unsupported content.
- Keep the pre-change backup; do not treat deploy history as guaranteed complete recovery.
If the whole site stops responding
Pause changes. Distinguish DNS, HTTPS, static-file delivery and WordPress/PHP processing before choosing a fix. An outage after a change deserves investigation, but timing alone does not establish the cause.
Escalating a problem
Use the support channel supplied with your license or installation. Include the version and sanitized error details. For server availability, DNS or hosting-account issues, contact the responsible hosting provider or administrator.
Revoke an unused or compromised Application Password. Never send an account password or a completed credential file in a public support thread.
Product questions
For IM-Press product and licensing enquiries, contact contact@im-press.me. Share only a brief description and sanitized error details—never passwords or license keys.