| 开发者 | rajdeep95 |
|---|---|
| 更新时间 | 2026年11月11日 22:31 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
build folder is compiled from the source in the src folder, which is included in the plugin. Development happens on GitHub: rajdeepgaur/block-rewind. To build the plugin yourself, clone the repository and run npm install and then npm run build.
In your browser's IndexedDB storage, separately for each site and each user. It never leaves your browser.
Versions are removed after 4 hours by default. History is also not available when you edit in another browser, on another device, in a private window, or after clearing the site's data in your browser.
No. Each user's history is stored in their own browser, and other users of the same site can't see it.
No. Revisions keep the whole post for as long as you like. Block Rewind keeps a short, detailed history of each block while you work. They work well together.
When you first edit a block, Block Rewind adds a short random ID to it (the blockRewindId attribute), so the block can find its history again. The ID is saved with the post when you save it. It holds no personal data and does not change how the block looks.
Your content is not affected. WordPress ignores the block IDs, and they are removed the next time you save a post. History already stored in your browser is no longer shown and is removed when you clear the site's data in your browser.
Not yet. Block Rewind works in the post and page editor, for posts, pages and custom post types. While you edit a template or synced pattern from a post, history pauses and resumes when you return to the post.
Yes, with two filters. For example, to keep history for 8 hours and up to 200 versions per block:
add_filter( 'block_rewind_snapshot_ttl', function () { return 8 * HOUR_IN_SECONDS; } );
add_filter( 'block_rewind_max_snapshots_per_block', function () { return 200; } );
Retention is at least 5 minutes, and at least 5 versions are kept per block.
The sidebar tells you that new versions can't be saved. Existing versions stay available, and your post is not affected. Saving starts again once the browser has space.