Linux 软件免费装

Attributes for Blocks

开发者 websevendev
jimedwards
更新时间 2024年9月7日 12:23
PHP版本: 7.4 及以上
WordPress版本: 6.6
版权: GPLv2 or later
版权网址: 版权信息

标签

style blocks gutenberg aria attributes

下载

1.0.0 1.0.1 1.0.5 1.0.9 1.0.3 1.0.4 1.0.2 1.0.6 1.0.7 1.0.8

详情介绍:

This plugin adds additional advanced inspector controls to Gutenberg blocks that allow to add any custom HTML attributes to the block's front-end output. This allows you to add inline styles to fine-tune the block's appearance, set aria attributes to improve your site's accessibility, add data attributes to integrate with any JavaScript modules or even JavaScript DOM event attributes such as onclick, onchange or onload. Demo

安装:

Install via admin dashboard
  1. Go to your WordPress admin dashboard -> Plugins.
  2. Click "Add New".
  3. Click "Upload Plugin".
  4. Select the attributes-for-blocks.zip file.
  5. Click "Install Now".
  6. Activate the plugin from WordPress admin dashboard -> Plugins.
Manual install via FTP upload
  1. Upload the folder "attributes-for-blocks" from attributes-for-blocks.zip file to your WordPress installations ../wp-content/plugins folder.
  2. Activate the plugin from WordPress admin dashboard -> Plugins.

常见问题:

How do I add an attribute?

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: style, title, target, class, id, onclick, data-*, aria-*.

Why is the input disabled?

When the current user doesn't have unfiltered_html capabilities attributes cannot be added and all existing attributes are stripped when the post is updated.

How does it work?

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 render_callback function and they may also be applied in the editor, depending if the block is rendered server or client side.

Does it work for every block?

It should work with normal blocks that render a valid WP Element that can utilize the blocks.getSaveContent.extraProps filter as well as dynamic blocks that utilize a render_callback. Third party blocks that do something unorthodox may not work. Known unsupported blocks

Usage with Alpine.js

@ prefix in an attribute name is used for "override" mode in this plugin, for Alpine.js attributes use x-on:click instead of @click or use the shorthand syntax with two @ characters instead of one: @@click.

Disable block support

The afb_unsupported_blocks filter can be used in your child theme's functions.php file to disable block support for adding additional attributes. add_filter('afb_unsupported_blocks', function($blocks) { $blocks[] = 'core/button'; return $blocks; });

What happens when I disable this plugin?

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.

How do I add unfiltered_html capability to user roles?

You can modify which roles have the unfiltered_html capability using custom code in your theme's functions.php 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. add_action('init', function() { if($role = get_role('contributor')) { $role->add_cap('unfiltered_html'); } });

更新日志:

1.0.9 1.0.8 1.0.7 1.0.6 1.0.5 1.0.4 1.0.3 1.0.2 1.0.1