The Multicolumn section is blank, missing, or incomplete.

This page is for a Multicolumn section: repeated image, heading, and body blocks arranged as columns on a homepage or landing template. If the section wrapper is absent, if only one block renders, or if the cards appear in the editor but not on the live URL, classify that boundary before editing. A Featured collection with no product cards belongs in Featured collection blank; a paired image and copy block belongs in Image with text broken.

Record the exact URL, template suffix, section heading, expected column count, device, Market, theme name, and whether the section chrome is visible. One URL failing points to template or data; every URL failing points to the published theme, shared CSS, or an app conflict.

Open Online Store → Themes and inspect the published theme and the exact template assigned to the live URL. Confirm the Multicolumn section exists, is enabled, appears in the intended order, and is not hidden by a market or device condition. Preview parameters can show a draft theme or blocks that buyers never receive.

• Wrapper missing means wrong template, disabled section, or publish mismatch.
• Wrapper visible with no cards means block data, Liquid conditions, or a section limit.
• Desktop works but phone is blank means responsive visibility, overflow, or an app script.
• One page fails while another template works means assignment or template JSON, not a global CDN issue.

In the published theme editor, verify each block has a heading, body, image, link, and valid image source where intended. Check that no block is disabled, that the section has not exceeded the theme’s allowed block count, and that a dynamic source or metaobject reference still resolves. Then inspect view-source and Network: missing block markup is a template or Liquid gate; markup with empty fields is data; markup with hidden pixels is CSS or JavaScript.

Use DevTools only to classify the gate. Compare the editor value with the rendered HTML, inspect section.settings and block IDs in the theme code, then test one block with a plain text value. Change one variable at a time and keep the failing URL as the control. Do not replace the section with a screenshot or duplicate blocks to hide a missing source.

Restore the section on the correct published template, re-enable only the confirmed blocks, repair the dynamic source or image reference that evidence identifies, and remove only the CSS or app conflict causing the failure. Preserve semantic headings, alt text, links, keyboard focus, and mobile order. Publish the smallest change; do not broadly rewrite the theme.

Retest the same URL on desktop and phone, in a clean browser, after consent, and in a second Market. Confirm the expected number of blocks, image requests, intrinsic dimensions, alt text, heading hierarchy, card links, contrast, canonical URL, and neighboring sections. Save before/after evidence so a future theme or app update is diagnosable.

Stay DIY if one Multicolumn section needs one controlled template, block, or CSS correction. Prove the live path, fix the smallest gate, publish, and retest. No agency is required and no conversion or revenue guarantee is implied.

Pay $997 one-time when the work is wiring the live Shopify stack you already use: lead capture, ops alerts, and a checkout-ready workflow. Nico at Latch AI Ops installs it on one live store in 72 hours after collaborator access is in. You are buying the install, not more orders or an earnings claim.