| 开发者 | rnzo |
|---|---|
| 更新时间 | 2026年8月8日 12:04 |
| 捐献地址: | 去捐款 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
{{blocks:phone}} and every enabled placement displays the new value. Blocks also supports import and export for moving reusable content and variables between sites as a single JSON file.
Blocks is focused on reusable site-wide content, not on providing another decorative Gutenberg block collection. Because a block renders through a plain shortcode, the same content follows you across theme changes and builder migrations.
Full documentation, examples, and release notes live in the Blocks guide.
Reusable Content Blocks and Global Shortcodes
[block id="42"] in posts, pages, widgets, templates, and builders.{{blocks:phone}}, {{blocks:email}}, {{blocks:address}}, {{blocks:year}}, {{blocks:site_title}}, and more; the blocks: prefix means tokens never collide with other plugins.Create a source item under the Blocks menu, copy its shortcode (for example [block id="42"]), and paste it wherever the content should appear. Edit the source item to update every placement that uses it. See how it works.
Yes. Blocks ships integrations for the block editor (Gutenberg), Elementor, Divi, Bricks, Beaver Builder, WPBakery, Oxygen, Zion, Thrive, Breakdance, and Fusion (Avada). Add the shortcode or the native builder element where the content should appear.
A global content shortcode displays content managed in one source block. The same shortcode can be placed on multiple pages, widgets, templates, or supported builder layouts, and every placement updates when you edit the source.
Define a site variable such as a phone number, email address, price, or current year and display it with a token like {{blocks:phone}} or with [blocks var="name"]. Updating the stored variable changes every supported placement. Built-in tokens cover your site info, and an optional "resolve variables everywhere" setting makes tokens work typed directly into regular content, widgets, and any page builder.
Yes. The Import / Export page downloads all your blocks and variables as one JSON file and imports the same file on any other site running Blocks. Existing blocks are matched by title and are not overwritten unless you choose to.
Yes. Blocks supports categories and tags, so large libraries stay manageable.
Start with the Blocks documentation, or contact us directly and the developers will answer you. For ongoing help with your site, see our WordPress support plans.
Yes. On a new installation, the Help Improve Blocks checkbox is present, active, and checked by default. An administrator can turn it off at any time under Blocks Settings, and a saved opt-out stays off across updates. While enabled, Blocks sends a bounded product snapshot to Signls with Blocks, WordPress, and PHP versions, multisite status, and fixed aggregate 0 or 1 states for supported product capabilities and integrations. Random pseudonymous installation and device identifiers support delivery continuity. Blocks does not send content, field values, email or physical addresses, URLs, WordPress or commerce IDs, secrets, tokens, raw errors, customer or order data, messages, IP addresses, page journeys, plugin inventories, or arbitrary settings. Delivery receipts are retained for 90 days, the current snapshot is replaced by newer observations, and daily installation-level aggregates are retained for long-term product analysis.
If Blocks is useful to you, please leave a review on WordPress.org.