| Prio | Original string | Translation | — |
|---|---|---|---|
| The raw value of the variable. Shape depends on "type" (e.g. a solid color is a plain string like "#ff0000" while a gradient is an object, font families are strings, and units/sizes are { number, unit, style } objects). A responsive variable holds an object keyed by breakpoint id instead. | You have to log in to add a translation. | Details | |
|
The raw value of the variable. Shape depends on "type" (e.g. a solid color is a plain string like "#ff0000" while a gradient is an object, font families are strings, and units/sizes are { number, unit, style } objects). A responsive variable holds an object keyed by breakpoint id instead.
You have to log in to edit this translation.
|
|||
| "%s" can only exist once in a document, so it cannot be duplicated. | You have to log in to add a translation. | Details | |
|
"%s" can only exist once in a document, so it cannot be duplicated.
You have to log in to edit this translation.
|
|||
| Unknown payload key(s): %1$s. Valid keys for this op: %2$s. | You have to log in to add a translation. | Details | |
|
Unknown payload key(s): %1$s. Valid keys for this op: %2$s.
You have to log in to edit this translation.
|
|||
| "%1$s" cannot be added because "%2$s" is already in this document. | You have to log in to add a translation. | Details | |
|
"%1$s" cannot be added because "%2$s" is already in this document.
You have to log in to edit this translation.
|
|||
| ID of the destination parent element. Defaults to the current parent (reorder in place). | You have to log in to add a translation. | Details | |
|
ID of the destination parent element. Defaults to the current parent (reorder in place).
You have to log in to edit this translation.
|
|||
| Applies a sequence of element operations atomically to a %s post. This is the tool for CHANGING what is already on a post: rewriting text and headings, swapping an image or link, retitling a button, setting element properties, moving or deleting elements. html-to-page only ever ADDS a new subtree (it appends under parent_id), so never re-run it to reword or restyle something that already exists, that duplicates the section instead of editing it. For NEW layout it is the other way round: author it as HTML with html-to-page in one call, markers included (bd-loop for repeating collections, bd-bind* for dynamic bindings, bd-woo for WooCommerce parts, bd-animate for entrance animations), rather than inserting elements one at a time here. Also use edit-post for element properties no marker covers and for the few elements html-to-page cannot create (forms, dynamic widgets, component instances). Before setting layout or column properties via a CSS class, call get-element-schemas on the target element: many elements (e.g. PostsLoop) have native design properties that emit CSS to their correct internal DOM and could be used instead of custom classes. | You have to log in to add a translation. | Details | |
|
Applies a sequence of element operations atomically to a %s post. This is the tool for CHANGING what is already on a post: rewriting text and headings, swapping an image or link, retitling a button, setting element properties, moving or deleting elements. html-to-page only ever ADDS a new subtree (it appends under parent_id), so never re-run it to reword or restyle something that already exists, that duplicates the section instead of editing it. For NEW layout it is the other way round: author it as HTML with html-to-page in one call, markers included (bd-loop for repeating collections, bd-bind* for dynamic bindings, bd-woo for WooCommerce parts, bd-animate for entrance animations), rather than inserting elements one at a time here. Also use edit-post for element properties no marker covers and for the few elements html-to-page cannot create (forms, dynamic widgets, component instances). Before setting layout or column properties via a CSS class, call get-element-schemas on the target element: many elements (e.g. PostsLoop) have native design properties that emit CSS to their correct internal DOM and could be used instead of custom classes.
You have to log in to edit this translation.
|
|||
| The priority saved on the template after this call. | You have to log in to add a translation. | Details | |
| Decides which template wins when more than one matches the same request; higher wins. Omit it to leave the current priority unchanged, unless template_type is changing or the template has no priority saved yet, in which case it defaults to the (new) template_type's defaultPriority (from get-template-conditions), the same value the builder UI assigns. | You have to log in to add a translation. | Details | |
|
Decides which template wins when more than one matches the same request; higher wins. Omit it to leave the current priority unchanged, unless template_type is changing or the template has no priority saved yet, in which case it defaults to the (new) template_type's defaultPriority (from get-template-conditions), the same value the builder UI assigns.
You have to log in to edit this translation.
|
|||
| Whether the template is active. A template only applies to the site while active. Pass true to disable it, false to enable it, or omit to leave the current state unchanged. | You have to log in to add a translation. | Details | |
|
Whether the template is active. A template only applies to the site while active. Pass true to disable it, false to enable it, or omit to leave the current state unchanged.
You have to log in to edit this translation.
|
|||
| Sets the template target type and display conditions (where it applies) on an existing template, header, or footer. Replaces the existing conditions. Can also enable or disable the template via the disabled flag. Use get-template-conditions to discover valid template types, condition slugs, operands, and values. | You have to log in to add a translation. | Details | |
|
Sets the template target type and display conditions (where it applies) on an existing template, header, or footer. Replaces the existing conditions. Can also enable or disable the template via the disabled flag. Use get-template-conditions to discover valid template types, condition slugs, operands, and values.
You have to log in to edit this translation.
|
|||
| The priority saved on the template (the explicit value passed, or the template_type's defaultPriority). | You have to log in to add a translation. | Details | |
|
The priority saved on the template (the explicit value passed, or the template_type's defaultPriority).
You have to log in to edit this translation.
|
|||
| Decides which template wins when more than one matches the same request; higher wins. Omit it to use the template_type's defaultPriority (from get-template-conditions), the same value the builder UI assigns, so the new template ranks correctly against templates made in the UI. | You have to log in to add a translation. | Details | |
|
Decides which template wins when more than one matches the same request; higher wins. Omit it to use the template_type's defaultPriority (from get-template-conditions), the same value the builder UI assigns, so the new template ranks correctly against templates made in the UI.
You have to log in to edit this translation.
|
|||
| The priority create-template/set-template-conditions apply for this type when priority is omitted. Higher wins when two templates both match the same request. | You have to log in to add a translation. | Details | |
|
The priority create-template/set-template-conditions apply for this type when priority is omitted. Higher wins when two templates both match the same request.
You have to log in to edit this translation.
|
|||
| Value lists show only the first 10 options (terms, posts, users); when the one you need is not there, look it up with search-condition-values instead of guessing. | You have to log in to add a translation. | Details | |
|
Value lists show only the first 10 options (terms, posts, users); when the one you need is not there, look it up with search-condition-values instead of guessing.
You have to log in to edit this translation.
|
|||
| Returns the available template conditions for a given template post type (templates, headers, footers, or popups), with their resolved value options. Headers, footers, and popups also include the "everywhere" target so the template can be applied site-wide. Pass the popup post type to build rule_groups for create-popup. | You have to log in to add a translation. | Details | |
|
Returns the available template conditions for a given template post type (templates, headers, footers, or popups), with their resolved value options. Headers, footers, and popups also include the "everywhere" target so the template can be applied site-wide. Pass the popup post type to build rule_groups for create-popup.
You have to log in to edit this translation.
|
|||
Export as • Download Translation Package (Updated 3 weeks ago)