1ConsentConsentDocs
Custom consent designs

Limitations and troubleshooting

Start from the matching supplied framework design and identify whether failure occurs during compilation, mounting, interaction, synchronization, or publication.

SymptomCorrection
Bare-binding errorQuote attribute bindings; attribute spreading is unsupported
Unclosed loopClose with [/each]
Nested-condition errorPut an element between nested conditions; compound expressions are unsupported
Missing textVerify runtime path and locale. Notice title is ui.title
Blank propDots/colons imply a path; bind configured content instead of a dotted literal
Missing componentCheck partial name/upload and local/shared override; reusable partials must not start with @view
Children errorOne placeholder per component; do not pass children without it
Input does not saveCheck framework binding, ID, native checkbox, and Save command
Cancel retains staged editsVerify supplied close command and actual runtime behavior; do not add manual storage
Notice changes affect preferencesScope CSS and check common partials/theme tokens
CSS has no effectInspect Shadow DOM and :host attributes
Inherited styles disappearLocal files replace same-named defaults; retain needed rules
Cannot delete/rename fileSeeded dependencies are protected; edit content or add a file
Creation blockedCheck access, authoring role, owning scope, and retained-resource capacity
Assignment blockedMatch framework type and accessible resource scope
CLI unauthorizedCheck token, Design Manager right, scope, and effective access
Push leaves Live unchangedPush updates drafts; preview/review/publish in Dashboard
TCF publish blockedPublic-beta restrictions also apply to custom designs
Custom design stops servingCheck confirmed billing/evaluation status, restore access, review release
System improvement missingFull-design copies do not track system updates; review and port relevant changes. Custom banner releases freeze an official secondary version; subsequent official updates follow clean-framework, version-pin and Staging rules. Customer draft edits still require review and publication
Preference files unavailable in banner editorThe light editor changes only notice HTML and CSS. Use the selected theme for official preferences; existing app-owned full designs retain their advanced editor
Save reports a conflictAnother source edit changed the notice or styles since loading. Reload the latest draft, reconcile your changes and save again
Shared banner has no previewSelect an accessible app and matching CMP, save the banner and assign it with “Use in this CMP and preview”, then preview the saved draft
Cloned design still has a full editorCloning preserves the design mode. Create a new custom banner for maintained official preferences

Unsupported features

1CL does not run arbitrary JavaScript, React components, calculations, filters, object loops, or custom requests. Script/iframe/object/embed elements, inline handlers, attribute spreading, and separately mixing independently selected system/custom views are unsupported. Text bindings do not insert raw HTML.

Templates do not override essential-service policy, GPC, protocol behavior, or subscription entitlements. Retain supported disclosure components when restructuring rich content.

Debug release mismatches

Compare selected design, owner scope, draft Preview, reviewed source, and published stage. Shared partial edits can change Preview without changing the frozen release. Verify installed app ID and intended stage before investigating caches.

For support, record view, framework, locale, file names, compile error, expected behavior, and whether it occurs locally, in Preview, or on the installed CMP. Keep tokens/private configuration out of support evidence.

On this page