Black Friday
Skip to documentation content

Troubleshooting

Troubleshoot installation, activation and dependencies

Diagnose Free-first installation, Pro dependency, compatibility and updater failures without corrupting the active package pair.

Start with package identity and the first visible error. Avoid deleting an established installation or changing database version options to make activation appear successful.

Collect a safe baseline

Record the WordPress/PHP versions, plugin/theme versions, approved ZIP checksums and the error text. Redact guest details, keys, cookies and signed booking links. Keep the pre-change database/files backup available.

Check in this order

  1. Confirm the host meets WordPress 6.5+ and PHP 8.1+ requirements.
  2. Confirm Free is KimoraPro Hotel Booking at kimorapro-hotel-booking/hotel-booking.php, and Pro is hotel-booking-pro/hotel-booking-pro.php.
  3. Check whether a legacy Free hotel-booking copy remains. Use the migration procedure; do not activate two identities together.
  4. Confirm compatible Free is active before Pro. A Requires Plugins dependency prevents unsupported activation; it does not fetch and activate Free automatically.
  5. Read the actual plugin compatibility/storage error and check package integrity, permissions and required PHP facilities before retrying.
  6. For a working plugin with a missing frontend entry, inspect Page assignment, publication state and shortcode before treating it as activation failure.

Common outcomes

Symptom Safe next action
Pro dependency missing Install/activate the approved canonical Free package first
Pro active, premium feature unavailable Inspect compatibility and Hotel Booking → License; Page creation is not entitlement
License identity/connection error Check intended site/domain and secure service connectivity; use the supported check/recovery workflow
Page in Trash, draft, private or missing shortcode Repair the intended Page/assignment through WordPress and its role’s setup screen
Old UI after exact file replacement Inspect PHP worker/OPcache and relevant object/page/CDN caches
Theme frontend locked Follow that theme’s separate license/setup procedure

Do not disable TLS, copy activation tokens, edit license options or repeatedly save Permalinks as a generic repair. Do not use a demo import to recreate operational setup.

Verify and recover

Repeat the affected admin/Page checks and a safe first-booking test. Confirm existing records remain intact. If a critical problem remains, stop new bookings and follow the tested rollback procedure.

Escalate with the redacted error, exact package identity/checksum, steps and expected/actual result. Separate a package activation error, a missing Page, a locked feature and a mail/gateway configuration issue in the report.

Was this article helpful?

Your feedback helps us improve the documentation.