Themify

Themify Builder pages — never write content via REST/MCP

From legacy section: WordPress / MCP

Why: Themify Ultra theme + Themify Builder stores the page structure in _themify_builder_settings_json post_meta and renders via a the_content filter. post_content is a placeholder, not the source of truth. On 2026-05-13 (rockacademy.com page 12712), I tried to fix a "845 NY-212" typo by writing the corrected HTML to content.raw via mcp__wordpress__update_page. Live page suddenly had TWO themify_builder_content-12712 divs, doubled headings, doubled images, 5× "845 NY-212" — Themify rendered from meta AND my content. Setting content to empty string stopped the double-render but left the post editor's text area blank (which freaked Jim out). Final fix: Jim reverted to a pre-session revision via wp-admin Revisions UI, then made the actual fix manually in Themify Builder. Cost ~30 min and a "the content is blank" panic. How to apply: - Detect Themify Builder pages: if get_page returns full Themify HTML wrapped in <!--themify_builder_content--> markers in content.raw, treat the page as Themify-managed. Updating content is forbidden. - Safe edit paths: (1) Themify Builder UI in wp-admin (visual or backend tab), (2) WPCode PHP snippet that updates _themify_builder_settings_json post_meta directly, (3) WP-CLI script if backend access exists. - Recovery if already broken: revert to a pre-damage revision via wp-admin → Revisions. Setting content empty does NOT recover — only revision restore brings content.raw + post_meta back to consistent state. - Memory file: ~/.claude/projects/-Users-jim-Code-Evolve-Agency/memory/feedback_themify_builder_content_trap.md Date: 2026-05-13

---