WP-LIT-MCP

Files

T

janniclas.loosenandClaude Opus 5.5 43dc3fb889 fix: global usages follow the Theme Builder access (ruling Q17 M1)

GlobalUsages gets the Theme Builder access injected as a closure
(ThemeBuilderAccess::usageState(), wired at both construction sites through
DiviIntegration::globalUsages()). Theme Builder posts are named only while
the Theme Builder is visible to the account, otherwise only counted (also
in blocked_ids); a global edit that changes them needs canUse(), a writable
"Divi Theme Builder" group and edit_post. Without an injected access the
fail-safe default checks what canUse() checks. The duplicate
THEME_BUILDER_TYPES list gives way to DiviThemeBuilder::postTypes().

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01At3V6SjwbMe6eMzVGW3Hs7

2026-09-27 23:00:36 +02:00

content-types.md

docs: Divi guides shortform/placeholders, hints name the write tools; test: Divi write end-to-end; version 0.3.0

2026-09-26 17:13:59 +02:00

divi-attrs.md

docs: guides, readme and spec for the Divi Library (v0.4.0)

2026-09-27 03:33:38 +02:00

divi-design-system.md

docs: guides, readme and spec for the Divi Library (v0.4.0)

2026-09-27 03:33:38 +02:00

divi-library.md

fix: global usages follow the Theme Builder access (ruling Q17 M1)