New to Translating WordPress? Read through our Translator Handbook to get started. Hide
| Prio | Original string | Translation | — |
|---|---|---|---|
| ↑ | Allows to add HTML attributes to Gutenberg blocks. | You have to log in to add a translation. | Details |
Original untranslated |
|||
| ↑ | Attributes for Blocks | You have to log in to add a translation. | Details |
Original untranslated |
|||
| You can modify which roles have the <code>unfiltered_html</code> capability using custom code in your theme's <code>functions.php</code> file or via a custom plugin. Only grant this capability if you trust the current and future users of that role to not do anything malicious. | You have to log in to add a translation. | Details | |
Original untranslated
You can modify which roles have the <code>unfiltered_html</code> capability using custom code in your theme's <code>functions.php</code> file or via a custom plugin. Only grant this capability if you trust the current and future users of that role to not do anything malicious.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| When the current user doesn't have <code>unfiltered_html</code> capabilities attributes cannot be added and all existing attributes are stripped when the post is updated. | You have to log in to add a translation. | Details | |
Original untranslated
When the current user doesn't have <code>unfiltered_html</code> capabilities attributes cannot be added and all existing attributes are stripped when the post is updated.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| How do I add unfiltered_html capability to user roles? | You have to log in to add a translation. | Details | |
Original untranslated
How do I add unfiltered_html capability to user roles?
CommentFound in faq header. You have to log in to edit this translation. |
|||
| Why is the input disabled? | You have to log in to add a translation. | Details | |
Original untranslated
Why is the input disabled?
CommentFound in faq header. You have to log in to edit this translation. |
|||
| @ prefix in an attribute name is used for "override" mode in this plugin, for Alpine.js attributes use <code>x-on:click</code> instead of <code>@click</code> or use the shorthand syntax with two <code>@</code> characters instead of one: <code>@@click</code>. | You have to log in to add a translation. | Details | |
Original untranslated
@ prefix in an attribute name is used for "override" mode in this plugin, for Alpine.js attributes use <code>x-on:click</code> instead of <code>@click</code> or use the shorthand syntax with two <code>@</code> characters instead of one: <code>@@click</code>.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Usage with Alpine.js | You have to log in to add a translation. | Details | |
Original untranslated |
|||
| <a href="https://playground.wordpress.net/?plugin=attributes-for-blocks&url=%2Fwp-admin%2Fpost.php%3Fpost%3D2%26action%3Dedit">Demo</a> | You have to log in to add a translation. | Details | |
Original untranslated
<a href="https://playground.wordpress.net/?plugin=attributes-for-blocks&url=%2Fwp-admin%2Fpost.php%3Fpost%3D2%26action%3Dedit">Demo</a>
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| The <code>afb_unsupported_blocks</code> filter can be used in your child theme's <code>functions.php</code> file to disable block support for adding additional attributes. | You have to log in to add a translation. | Details | |
Original untranslated
The <code>afb_unsupported_blocks</code> filter can be used in your child theme's <code>functions.php</code> file to disable block support for adding additional attributes.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Disable block support | You have to log in to add a translation. | Details | |
Original untranslated |
|||
| Blocks with custom attributes may become invalid, depending on which attributes you've added. From there you can recover the block without the custom attributes by clicking "Attempt Block Recovery" or keep the block with custom attributes as HTML by choosing "Convert to HTML". If you don't want to risk blocks becoming invalid you need to remove all custom attributes before disabling the plugin. | You have to log in to add a translation. | Details | |
Original untranslated
Blocks with custom attributes may become invalid, depending on which attributes you've added. From there you can recover the block without the custom attributes by clicking "Attempt Block Recovery" or keep the block with custom attributes as HTML by choosing "Convert to HTML". If you don't want to risk blocks becoming invalid you need to remove all custom attributes before disabling the plugin.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| It should work with normal blocks that render a valid WP Element that can utilize the <code>blocks.getSaveContent.extraProps</code> filter as well as dynamic blocks that utilize a <code>render_callback</code>. Third party blocks that do something unorthodox may not work.↵ <a href="https://plugins.trac.wordpress.org/browser/attributes-for-blocks/trunk/includes/unsupported-blocks.php">Known unsupported blocks</a> | You have to log in to add a translation. | Details | |
Original untranslated
It should work with normal blocks that render a valid WP Element that can utilize the <code>blocks.getSaveContent.extraProps</code> filter as well as dynamic blocks that utilize a <code>render_callback</code>. Third party blocks that do something unorthodox may not work.↵
<a href="https://plugins.trac.wordpress.org/browser/attributes-for-blocks/trunk/includes/unsupported-blocks.php">Known unsupported blocks</a>
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| For regular blocks, attributes are added to the block save content's root element, meaning they will be rendered only on the front end and not in the editor. For dynamic blocks the attributes are added via <code>render_callback</code> function and they may also be applied in the editor, depending if the block is rendered server or client side. | You have to log in to add a translation. | Details | |
Original untranslated
For regular blocks, attributes are added to the block save content's root element, meaning they will be rendered only on the front end and not in the editor. For dynamic blocks the attributes are added via <code>render_callback</code> function and they may also be applied in the editor, depending if the block is rendered server or client side.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| In your selected block's inspector controls (Block settings) scroll all the way to the bottom and click on "Advanced". It should contain a section called "Additional attributes".↵ Type an attribute name into the "Add attribute" field and press "Add" to add an attribute for the block. A new input with the attribute's name should appear below, into which you can optionally insert the attribute value.↵ Example attributes: <code>style</code>, <code>title</code>, <code>target</code>, <code>class</code>, <code>id</code>, <code>onclick</code>, <code>data-*</code>, <code>aria-*</code>. | You have to log in to add a translation. | Details | |
Original untranslated
In your selected block's inspector controls (Block settings) scroll all the way to the bottom and click on "Advanced". It should contain a section called "Additional attributes".↵
Type an attribute name into the "Add attribute" field and press "Add" to add an attribute for the block. A new input with the attribute's name should appear below, into which you can optionally insert the attribute value.↵
Example attributes: <code>style</code>, <code>title</code>, <code>target</code>, <code>class</code>, <code>id</code>, <code>onclick</code>, <code>data-*</code>, <code>aria-*</code>.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
Export as
Comment
Short description.