Black Friday
Skip to documentation content

Troubleshooting

Run a safe conflict test and escalate

Reproduce a suspected plugin/theme conflict on an isolated copy with synthetic data. Disabling components on a trading site can affect inventory enforcement, payment recovery, queues and customer access even when the immediate symptom is visual.

Reproduce a suspected plugin/theme conflict on an isolated copy with synthetic data. Disabling components on a trading site can affect inventory enforcement, payment recovery, queues and customer access even when the immediate symptom is visual.

Prepare the isolated copy

Back up and record actual versions, source/package identity, active theme/child theme and relevant settings. Prevent outgoing mail, live payment/refund calls, OTA sync and license operations before testing. Use a mail sink and sandbox-only credentials where an integration is explicitly required.

Do not copy production secrets or real guest data simply to make the test realistic. Verify isolation and a safe cleanup/reset plan. Never use uninstall, a booking purge or removal of external blocks as preparation.

Change one variable at a time

  1. Establish the smallest reproduction and expected result on the current compatible pair.
  2. Test Free alone with a standard theme when the feature belongs to Free. Basic booking, Contact, Newsletter and booking privacy must not require purchasing Pro.
  3. Add legitimately entitled Pro only for its workflows, then the intended theme and suspected extension.
  4. Restore each test state before changing the next variable and keep separate results for source, native runtime, browser and provider checks.

Use the actual owner of each flow. Theme markup/CSS must not change server availability, tax rules, ledger decisions, policy history or external-block ownership. Missing premium entitlement is a configuration boundary, not a license-bypass test.

Verify the relevant journey

For booking issues, follow Search → Room Detail → Book Now → the applicable payment step → Confirmation, then inspect the stored reservation. For communications, check disabled/readiness states, native submission, stored record and mail capture; double opt-in needs confirmation POST, not a GET visit. For privacy, use reviewed synthetic request records and inspect both removed and retained outcomes.

Do not request another payment because a return page or email is missing. Do not weaken nonce, TLS, capability, signature, digest or source-fetch checks to obtain a green result.

Escalate with bounded evidence

Report exact versions/builds, route pattern, locale/viewport, UTC times, steps and expected/actual results. Use stable placeholders for emails, booking codes, feed URLs, access tokens and provider references. Contact service@kimorapro.com for the appropriate route; no response-time guarantee or unverified support forum is asserted.

Use the canonical Free folder kimorapro-hotel-booking for same-identity replacements; legacy migration is separate. Preserve current data and previous compatible packages. A code rollback cannot undo erasure or a provider refund. See backup and recovery.

Was this article helpful?

Your feedback helps us improve the documentation.