Omnikyo/Help Center
Troubleshooting

Designer and theme problems

Fix errors in the designer: conflicts from simultaneous edits, offline issues, field validation, missing references and offer validation holds.

বাংলায়: ডিজাইনার এরর এলে তা এড়িয়ে যাবেন না — সাধারণ কারণ আছে এবং সমাধান আছে। কনফ্লিক্ট মানে দুটো ট্যাব একসাথে এডিট করছে, অফলাইন মানে ইন্টারনেট নেই, কম্পাইল এরর মানে মেনু বা প্রোডাক্ট মিসিং। প্রতিটি সমস্যার জন্য স্টেপ আছে নিচে।

Where to find it: Designer › check the top bar and error messages

The top bar shows "Edited elsewhere" (amber badge)

What you see: An amber Edited elsewhere badge appears in the save state badge.

Why it happens: Another device or browser tab you have open made a change to the same theme at the same time. The server version of the theme diverged from what you see in your editor, and your unsaved changes cannot be merged.

How to fix it:

  1. Look at the Conflict bar — a full-width amber strip under the top bar. It shows what changed on the server.
  2. Decide: do you want to Keep mine (discard the server version) or Take theirs (discard your changes and reload the server version).
  3. Tap the button. Save and Publish are blocked until you resolve it.
  4. If you kept yours and want to try saving again, click Save. If the conflict cannot be rebased after three attempts, the Conflict bar reappears.

Still stuck? Open the designer in one tab only. If you need to work on another device, save and exit the designer first, then open it on the other device.

The designer says "You are offline"

What you see: An amber Offline badge in the save state, and a message shows in the floating AI bar.

Why it happens: Your browser lost the network connection. The designer queued your unsaved changes but cannot flush them to the server.

How to fix it:

  1. Check your internet connection (reload the page to test).
  2. Once online, the badge should fade and the Save button will try to flush the queue.
  3. If the queue is stuck, refresh the page (unsaved edits are lost, but this unsticks you).

A field shows an error under it (red text, not a compile error)

What you see: A field in the right panel has red error text: "A name is required.", "Handles are at most 64 characters.", "Give the offer a name.", etc.

Why it happens: The field value is not valid (too long, missing required text, wrong format, duplicate handle, etc.). The change is held — it does not write to the document until the field is fixed.

How to fix it:

  1. Read the error message — it tells you what is wrong (missing, too long, wrong format, etc.).
  2. Fix the field. Type valid text, clear the field if it is empty, delete extra characters, etc.
  3. The error clears once the field is valid, and the change writes.

Examples:

  • Offer name: "Give the offer a name." → Type a name.
  • Menu handle: "Handles are at most 64 characters. Not saved yet." → Shorten the handle.
  • Offer items: "Every line needs a product and a quantity of at least 1." → Add a product and qty to each row.
  • Menu link: 'Handles are lowercase words joined by hyphens, e.g. "summer-sale".' → Use lowercase and hyphens only.

A section or block shows a red alert icon (compile error)

What you see: A red alert icon appears on the section or block name in the outline (left sidebar), with a small number ("1" or "2", etc.). In the right panel, red error text appears above the settings.

Why it happens: The section or block's settings are invalid — a missing menu handle, a deleted product reference, out-of-stock condition on a required setting, etc. The theme will not compile until you fix it.

How to fix it:

  1. Look at the red error text in the right panel. It tells you what is wrong (e.g., "Menu with handle "missing-menu" not found.").
  2. Fix the issue:
    • Missing menu — open Theme settings › Menus and create a menu with the right handle, or change the block's menu handle to one that exists.
    • Missing product — open the product picker and choose a product that exists.
    • Missing collection — open the collection picker and choose one that exists.
    • Offer validation — follow the validation message (every offer needs items and pricing, etc.).
  3. The error clears when the reference is fixed.

Still stuck? Publish is blocked until compile errors are gone. If you cannot fix it, Delete the section or block and rebuild it.

A button says "Menu with handle <handle> not found"

What you see: A Menu block shows an error "Menu with handle "main-menu" not found." The outline shows a red alert icon.

Why it happens: The block refers to a menu handle that no longer exists — it was deleted from Theme settings › Menus, or the handle was misspelled.

How to fix it:

  1. Open Theme settings › Menus. Look for a menu with the handle shown in the error (e.g., "main-menu").
  2. If it exists, the compile error is a stale cache — refresh the page.
  3. If it does not exist, create a menu with that handle, or change the block's Menu setting to a handle that exists.

An image or reference shows a red "not found" card

What you see: In the right panel, a field shows a red card: "This product no longer exists" / "This collection no longer exists."

Why it happens: The block refers to a product or collection that was deleted, archived, or hidden.

How to fix it:

  1. Delete the card (click the X), or
  2. Open the picker and choose a different product or collection.

A section or block is hidden in the outline (dimmed and marked with an eye icon)

What you see: The section or block name appears dimmed (faded) in the left sidebar. A small eye icon shows next to it.

Why it happens: You toggled Hide on the section or block. Hidden sections and blocks do not appear on the storefront.

How to fix it:

  1. Click the eye icon next to the section or block name in the outline.
  2. It becomes visible again.

Still stuck? If you cannot find the eye icon, select the section and look for a Hide button in the right panel header, or use the outline's context menu (right-click the row) and choose Show.

Theme changes do not appear on the storefront (stale storefront)

What you see: You edited theme colours, typography or settings, published the theme, but the storefront still shows the old appearance.

Why it happens: The storefront cache has not refreshed yet, or you did not publish the theme. Publishing takes a few seconds to propagate (the edge cache resets within a few minutes).

How to fix it:

  1. Check that you clicked Publish. The top bar should show Saved (no unsaved changes).
  2. Hard-refresh the storefront in your browser (Ctrl+Shift+R or Cmd+Shift+R).
  3. Wait 1–2 minutes for the edge cache to reset.
  4. If the storefront still shows old colours/fonts, the theme may not have published — check the publish status in the designer.

The storefront shows a compile error (not the designer)

What you see: The storefront page is blank or shows an error message instead of products or content.

Why it happens: The theme has compile errors that block the storefront from rendering. The compile error list is in the designer's right panel (select a section to see its errors).

How to fix it:

  1. Open the designer.
  2. Read the red error text in the right panel — it tells you what is wrong (missing menu, missing product, etc.).
  3. Fix the issue as described above.
  4. Click Publish. The storefront should appear once the publish completes.

A field is unavailable (greyed out) and the label has a tooltip

What you see: A field in the right panel is greyed out, and hovering the label shows a tooltip explaining why.

Why it happens: The field depends on another setting. For example, Focal point is disabled until you choose a fixed aspect ratio (because focal point only applies when the image is cropped).

How to fix it:

  1. Read the tooltip — it tells you what other setting must change.
  2. Change that setting (e.g., set Aspect ratio to something other than "Original").
  3. The field becomes available.

The offer form shows validation errors and I cannot save

What you see: Red error messages appear under fields in the Offers editor. The changes are held — the offer does not save until every field is valid.

Why it happens: An offer requires a name, at least one product, a pricing mode (Sum / Fixed / Discount), and every item needs a product and quantity.

How to fix it:

  1. Read each red error message:
    • Give the offer a name → type a name
    • Add at least one product → click Select products and add items
    • Every line needs a product and a quantity of at least 1 → edit each line to have a product and qty ≥ 1
    • Offers require at least one pricing choice (Sum, Fixed price, or Discount) → choose a pricing mode
  2. Once every field is valid, the changes write and you can click Discard draft or keep editing.

A message or offer is "held" and cannot save

What you see: A message appears: "The offer is added once every field below is valid." or "Changes are held until every field below is valid."

Why it happens: One or more fields in the form have validation errors (see above). The form is in draft mode and will not write to the document until every field is valid.

How to fix it:

  1. Read the red errors under each field.
  2. Fix each one.
  3. Once all fields are valid, the draft writes automatically.

Pack switch says "Nothing has changed yet" and shows an impact list

What you see: A dialog appears titled "Switch from <pack> to <pack>?" with a list of changes (e.g., "Parked sections: 3 sections archived").

Why it happens: Switching theme packs may cause sections that the new pack cannot render to be archived. The dialog shows you what will happen before you confirm.

How to fix it:

  1. Read the impact list. Look for any sections you need — they will be archived, not deleted.
  2. Click Cancel if you want to keep those sections, or the switch button (e.g., "Switch to Dawn") to proceed.
  3. If sections are archived, you can restore them later from Theme settings › Theme pack › Archived sections.

A section is archived (appears under "Archived sections" in Theme settings)

What you see: In Theme settings › Theme pack, a section appears under "Archived sections: Nothing here yet" or a list of section names.

Why it happens: You switched theme packs, and the current pack cannot render that section type. The section is kept in case you switch back.

How to fix it:

  1. Option A: Switch back to the pack that can render it (click the switch button on that pack's card).
  2. Option B: Delete the archived section (under "Archived sections", click the row and delete). You can undo this within the same editor session.
  3. If you need the section on the current pack, recreate it manually or ask OmniAI to build it.

Theme colour scheme changes do not apply to existing sections

What you see: You edited a colour scheme or added a new scheme, but sections still show the old colours.

Why it happens: Schemes change the default for new sections. Sections you already created stay on their assigned scheme until you manually change them. A new theme pack may also carry its own scheme assignments.

How to fix it:

  1. Select each section that should use the new scheme.
  2. In the right panel, find the Colour scheme setting under the Colour scheme capability group (open it if it is closed).
  3. Change the scheme to the new one.

The Field theme is "locked" to compact look and I cannot change it

What you see: Field theme sections show a Compact look toggle that is locked (greyed out, with a lock icon or message).

Why it happens: The Field theme was designed for a compact look, and that setting is fixed. You cannot change it.

How to fix it:

  1. This is by design — no fix needed. Use the compact look or switch to a different theme if you need more spacing.

Other ways people ask this

  • designer offline কাজ করতে পারি
  • theme edit করলে কেন দেখা যাচ্ছে না storefront এ
  • menu handle compile error
  • product not found designer
  • section hide কিভাবে করি
  • conflict bar কি
  • field validation error কাকে বলে
  • editor error red alert
  • offer won't save কেন
  • theme conflict ঠিক করব কিভাবে
  • designer hangs hang frozen
  • field grey out disabled
  • save করব পারছি না

Checked against the product on 2026-10-03.