Use this checklist when Hotel Booking Pro does not activate, premium menus are missing, updates do not appear, or booking features behave unexpectedly.
Supported environment
- WordPress 6.5 or later
- PHP 8.1 or later
- Hotel Booking Free Core 3.1.0 or later within the 3.x release line
- Hotel Booking Pro installed in the
hotel-booking-prodirectory - A valid Kimora license for premium entitlement and updates
Plugin will not activate
Install and activate Hotel Booking Free Core before Hotel Booking Pro. Confirm the PHP version, verify that the ZIP contains one top-level hotel-booking-pro directory, and check the WordPress fatal-error message or server PHP log. Do not rename the main plugin directory or entry file.
Premium menus are missing
Check that both plugins are active, the Free Core version is compatible, and the Kimora license grants Pro entitlement. Clear page cache, object cache, and opcode cache when appropriate. Sign out and back in, then test with an administrator account.
Updates do not appear
Verify the license status and assigned domain, outbound HTTPS connectivity to Kimora, WordPress cron, server time, and the plugin directory name. Refresh the WordPress update check after clearing transient or object cache. Do not install a package whose embedded version does not match the intended release.
Payments or emails fail
Confirm HTTPS, gateway credentials, callback or webhook delivery, SMTP configuration, sender authentication, scheduled actions, and uncached confirmation pages. Use provider test mode and check logs before switching to live transactions.
OTA synchronization fails
Review credentials, room mappings, property identifiers, timezone, webhook authentication, firewall rules, and scheduled jobs. Compare the external reservation reference with the local synchronization log before retrying or editing the reservation manually.
Information to include in a support request
- Hotel Booking Free Core and Pro versions
- WordPress and PHP versions
- The exact error message and time of occurrence
- Steps to reproduce the issue
- Relevant sanitized logs with passwords, keys, tokens, and customer data removed