Block Supports is a mechanism in the Gutenberg editor that controls block functionality and style support. It allows the unified activation or disabling of specific block characteristics such as color, spacing, alignment, etc. through the theme.json file. For example, color and spacing support can be enabled for paragraph blocks in theme.json to achieve globally consistent design specifications. Common supported features include color, typography, spacing, layout and other options such as anchor links and title tags. When using it, make sure the theme.json loads correctly, and pay attention to version compatibility and syntax correctness to avoid invalid settings or errors.
When using the Gutenberg editor, you may find that some block styles or features do not appear as expected. In fact, Gutenberg provides a functional module called "Block Supports", which can help you enable or disable certain block support features in the editor, such as spacing, color, alignment, etc. It is mainly aimed at theme developers, but it can also be helpful to know these settings if you are a power user or want to customize the appearance of your website.
What are Block Supports?
Block Supports is a mechanism in Gutenberg that allows you to define which blocks should support which functions in the theme's theme.json
file. You can control the behavior and style of blocks throughout the site without having to set them separately for each block. This not only improves efficiency, but also maintains design consistency.
For example, you can decide whether all paragraph blocks can be set background color, or whether a block is allowed to be fully aligned.
How to enable Block Supports in theme.json
To use Block Supports in your theme, you first need to create or modify the theme.json
file in the theme directory. This file is used to configure various styles and behaviors of Gutenberg.
In this file, you can define the functions supported by the block through the supports
field. Here is a simple example:
{ "version": 2, "settings": { "blocks": { "core/paragraph": { "supports": { "color": { "background": true, "text": true }, "spacing": { "margin": true, "padding": true } } } } } }
In this example, we enabled support for the color (text and background) and spacing (outer and inner margins) of the paragraph block.
What are the common Block Supports features?
Common Block Supports settings include:
- Color support : Includes text color and background color.
- Typesetting support : font size, line height, letter spacing, etc.
- Spacing support : outer margin, inner margin.
- Layout support : alignment, width setting.
- Other functions : such as anchor links, title tag selection, etc.
You can set these functions for different blocks according to your needs. For example, if you want all button blocks to support background colors, you can write this:
"core/button": { "supports": { "color": { "background": true } } }
Of course, certain functions can also be completely turned off to avoid user misoperation affecting the overall style.
Notes and FAQs
There are several things to note when using Block Supports:
- Make sure your theme has the
theme.json
file loaded correctly. - The support for
theme.json
in different versions of Gutenberg and WordPress may be slightly different. It is recommended to check the official documentation to confirm compatibility. - If the modification does not take effect, try clearing the cache or checking for errors in the syntax.
- If you want to override global settings and set the style separately for a block instance, you can manually turn on the related options in the Block Settings panel.
Basically that's it. Although Block Supports may seem a bit technical, once mastered, it can efficiently manage the block styles of the entire site.
The above is the detailed content of How to use Block Supports in Gutenberg. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

The main reasons why WordPress causes the surge in server CPU usage include plug-in problems, inefficient database query, poor quality of theme code, or surge in traffic. 1. First, confirm whether it is a high load caused by WordPress through top, htop or control panel tools; 2. Enter troubleshooting mode to gradually enable plug-ins to troubleshoot performance bottlenecks, use QueryMonitor to analyze the plug-in execution and delete or replace inefficient plug-ins; 3. Install cache plug-ins, clean up redundant data, analyze slow query logs to optimize the database; 4. Check whether the topic has problems such as overloading content, complex queries, or lack of caching mechanisms. It is recommended to use standard topic tests to compare and optimize the code logic. Follow the above steps to check and solve the location and solve the problem one by one.

Miniving JavaScript files can improve WordPress website loading speed by removing blanks, comments, and useless code. 1. Use cache plug-ins that support merge compression, such as W3TotalCache, enable and select compression mode in the "Minify" option; 2. Use a dedicated compression plug-in such as FastVelocityMinify to provide more granular control; 3. Manually compress JS files and upload them through FTP, suitable for users familiar with development tools. Note that some themes or plug-in scripts may conflict with the compression function, and you need to thoroughly test the website functions after activation.

Methods to optimize WordPress sites that do not rely on plug-ins include: 1. Use lightweight themes, such as Astra or GeneratePress, to avoid pile-up themes; 2. Manually compress and merge CSS and JS files to reduce HTTP requests; 3. Optimize images before uploading, use WebP format and control file size; 4. Configure.htaccess to enable browser cache, and connect to CDN to improve static resource loading speed; 5. Limit article revisions and regularly clean database redundant data.

TransientsAPI is a built-in tool in WordPress for temporarily storing automatic expiration data. Its core functions are set_transient, get_transient and delete_transient. Compared with OptionsAPI, transients supports setting time of survival (TTL), which is suitable for scenarios such as cache API request results and complex computing data. When using it, you need to pay attention to the uniqueness of key naming and namespace, cache "lazy deletion" mechanism, and the issue that may not last in the object cache environment. Typical application scenarios include reducing external request frequency, controlling code execution rhythm, and improving page loading performance.

The most effective way to prevent comment spam is to automatically identify and intercept it through programmatic means. 1. Use verification code mechanisms (such as Googler CAPTCHA or hCaptcha) to effectively distinguish between humans and robots, especially suitable for public websites; 2. Set hidden fields (Honeypot technology), and use robots to automatically fill in features to identify spam comments without affecting user experience; 3. Check the blacklist of comment content keywords, filter spam information through sensitive word matching, and pay attention to avoid misjudgment; 4. Judge the frequency and source IP of comments, limit the number of submissions per unit time and establish a blacklist; 5. Use third-party anti-spam services (such as Akismet, Cloudflare) to improve identification accuracy. Can be based on the website

When developing Gutenberg blocks, the correct method of enqueue assets includes: 1. Use register_block_type to specify the paths of editor_script, editor_style and style; 2. Register resources through wp_register_script and wp_register_style in functions.php or plug-in, and set the correct dependencies and versions; 3. Configure the build tool to output the appropriate module format and ensure that the path is consistent; 4. Control the loading logic of the front-end style through add_theme_support or enqueue_block_assets to ensure that the loading logic of the front-end style is ensured.

To add custom user fields, you need to select the extension method according to the platform and pay attention to data verification and permission control. Common practices include: 1. Use additional tables or key-value pairs of the database to store information; 2. Add input boxes to the front end and integrate with the back end; 3. Constrain format checks and access permissions for sensitive data; 4. Update interfaces and templates to support new field display and editing, while taking into account mobile adaptation and user experience.

robots.txt is crucial to the SEO of WordPress websites, and can guide search engines to crawl behavior, avoid duplicate content and improve efficiency. 1. Block system paths such as /wp-admin/ and /wp-includes/, but avoid accidentally blocking the /uploads/ directory; 2. Add Sitemap paths such as Sitemap: https://yourdomain.com/sitemap.xml to help search engines quickly discover site maps; 3. Limit /page/ and URLs with parameters to reduce crawler waste, but be careful not to block important archive pages; 4. Avoid common mistakes such as accidentally blocking the entire site, cache plug-in affecting updates, and ignoring the matching of mobile terminals and subdomains.
