InspectorControls is a component used in Gutenberg development to add custom controls in the right sidebar. 1. It belongs to the @wordpress/block-editor package. 2. It is often used with PanelBody, TextControl and other components. 3. When using it, you need to introduce and reasonably lay out control types such as text boxes, pull-down selections, switches, sliders and color selectors in edit.js. 4. Pay attention to grouping settings, keep them simple, support internationalization and optimize performance.
In Gutenberg development, InspectorControls
is a very practical component that is used to add custom controls in the right sidebar of the editor (that is, the Block Settings panel). If you want users to adjust block properties, such as color, size, or layout options, InspectorControls
is the key tool you want to use.
Below are some common usage scenarios and specific implementation methods to help you get started quickly.
What are InspectorControls?
In short, InspectorControls
is a React component provided by WordPress @wordpress/block-editor
package. It is responsible for inserting UI controls into the right sidebar of the Gutenberg editor. It is usually used with components such as PanelBody
, TextControl
, SelectControl
and other components.
You cannot put it directly in the main editing area (other in the Edit function), it can only be rendered as a child element of InspectorControls
.
How to add basic controls
The most common approach is to introduce relevant components into your block's edit.js
file and add some control items to InspectorControls
. For example:
import { InspectorControls, PanelBody, TextControl } from '@wordpress/block-editor'; import { __ } from '@wordpress/i18n'; export default function Edit( { attributes, setAttributes } ) { const { customText } = attributes; Return ( <> <InspectorControls> <PanelBody title={ __( 'set', 'my-block' ) }> <TextControl label={ __( 'Input text', 'my-block' ) } value={ customText } onChange={ ( value ) => setAttributes( { customText: value } ) } /> </PanelBody> </InspectorControls> <p>{ customText }</p> </> ); }
This way the user can modify the displayed text content in the sidebar.
Common control types and uses
You can choose different control types according to your needs. Here are some commonly used ones:
- TextControl : Text input box, a property suitable for string type.
- SelectControl : drop-down selection box, suitable for settings with limited options.
- ToggleControl : Switch button, used for boolean values ??(true/false).
- RangeControl : Sliding bar, suitable for numerical range adjustment.
- ColorPicker : Color selector, used for color settings.
For example, adding a color selector can be written like this:
import { ColorPicker } from '@wordpress/block-editor'; <ColorPicker color={ colorValue } onChange={ ( value ) => setAttributes( { colorValue: value } ) } />
These controls can be used in combination to create a feature-rich settings panel.
Notes and best practices
- Reasonable grouping controls : Use multiple
PanelBody
to separate settings of different categories to improve readability. - Avoid overcomplexity : Don’t add too many controls at once to keep the interface simple.
- Internationalization support : All text tags should be translated using
__()
or_x()
. - Performance optimization : If there are many controls, consider lazy loading or rendering on demand.
Basically that's it. Using InspectorControls
can significantly improve the functionality and user experience of the block. Although it is not complicated, it is easy to ignore details. It is recommended to refer to the official documents and existing plug-ins to implement them.
The above is the detailed content of How to use InspectorControls 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)

Hot Topics

Use WordPress testing environments to ensure the security and compatibility of new features, plug-ins or themes before they are officially launched, and avoid affecting real websites. The steps to build a test environment include: downloading and installing local server software (such as LocalWP, XAMPP), creating a site, setting up a database and administrator account, installing themes and plug-ins for testing; the method of copying a formal website to a test environment is to export the site through the plug-in, import the test environment and replace the domain name; when using it, you should pay attention to not using real user data, regularly cleaning useless data, backing up the test status, resetting the environment in time, and unifying the team configuration to reduce differences.

When managing WordPress projects with Git, you should only include themes, custom plugins, and configuration files in version control; set up .gitignore files to ignore upload directories, caches, and sensitive configurations; use webhooks or CI tools to achieve automatic deployment and pay attention to database processing; use two-branch policies (main/develop) for collaborative development. Doing so can avoid conflicts, ensure security, and improve collaboration and deployment efficiency.

The key to creating a Gutenberg block is to understand its basic structure and correctly connect front and back end resources. 1. Prepare the development environment: install local WordPress, Node.js and @wordpress/scripts; 2. Use PHP to register blocks and define the editing and display logic of blocks with JavaScript; 3. Build JS files through npm to make changes take effect; 4. Check whether the path and icons are correct when encountering problems or use real-time listening to build to avoid repeated manual compilation. Following these steps, a simple Gutenberg block can be implemented step by step.

TosetupredirectsinWordPressusingthe.htaccessfile,locatethefileinyoursite’srootdirectoryandaddredirectrulesabovethe#BEGINWordPresssection.Forbasic301redirects,usetheformatRedirect301/old-pagehttps://example.com/new-page.Forpattern-basedredirects,enabl

In WordPress, when adding a custom article type or modifying the fixed link structure, you need to manually refresh the rewrite rules. At this time, you can call the flush_rewrite_rules() function through the code to implement it. 1. This function can be added to the theme or plug-in activation hook to automatically refresh; 2. Execute only once when necessary, such as adding CPT, taxonomy or modifying the link structure; 3. Avoid frequent calls to avoid affecting performance; 4. In a multi-site environment, refresh each site separately as appropriate; 5. Some hosting environments may restrict the storage of rules. In addition, clicking Save to access the "Settings>Pinned Links" page can also trigger refresh, suitable for non-automated scenarios.

UsingSMTPforWordPressemailsimprovesdeliverabilityandreliabilitycomparedtothedefaultPHPmail()function.1.SMTPauthenticateswithyouremailserver,reducingspamplacement.2.SomehostsdisablePHPmail(),makingSMTPnecessary.3.SetupiseasywithpluginslikeWPMailSMTPby

Tointegratethird-partyAPIsintoWordPress,followthesesteps:1.SelectasuitableAPIandobtaincredentialslikeAPIkeysorOAuthtokensbyregisteringandkeepingthemsecure.2.Choosebetweenpluginsforsimplicityorcustomcodeusingfunctionslikewp_remote_get()forflexibility.

To implement responsive WordPress theme design, first, use HTML5 and mobile-first Meta tags, add viewport settings in header.php to ensure that the mobile terminal is displayed correctly, and organize the layout with HTML5 structure tags; second, use CSS media query to achieve style adaptation under different screen widths, write styles according to the mobile-first principle, and commonly used breakpoints include 480px, 768px and 1024px; third, elastically process pictures and layouts, set max-width:100% for the picture and use Flexbox or Grid layout instead of fixed width; finally, fully test through browser developer tools and real devices, optimize loading performance, and ensure response
