Archiving and other rules

Archive instead of deleteCopy Anchor Link

A block cannot be deleted. It can be archived and later re-activated. An archived block is not offered in any picker and does not render.

Archiving is refused while any injectable that is not itself archived still uses the block, whether that injectable is active, paused, a draft or preview only. The message names the injectables and explains that archiving would silently stop them showing the next time StoreSpan rebuilds them. Point those injectables at another block, or remove the block from their stacks, and then archive.

Changing a used block to a scriptCopy Anchor Link

Switching a block that active injectables use to the Script kind is refused. That would put new code on storefront pages without the typed publish check an injectable normally goes through. Pause the injectables, make the change, and publish them again.

Other rulesCopy Anchor Link

• A block cannot be a Blocks stack, a Mega menu or a Kit, and cannot carry page-wide External CSS. See Blocks overview.
• Only HTML & CSS and Template blocks declare variables.
• Variable placement is strict; a misplaced variable blocks the save. See Variables.
• Duplicate copies the saved version, not unsaved edits.
• If someone else saves the block while you have it open, your save is refused and you must reload.
• A stack holds a limited number of blocks, hidden copies included (see Limits). A stacked block that has been archived is left out of the storefront output and shown as Archived in the editor; a block that no longer exists shows as Unavailable.
• A stack delivered as a widget must fit the widget size limit; the stack editor warns before you reach it. See Limits.