WordPress plugin that fixes corrupt Unicode escape sequences in block editor JSON data.
WordPress stores block editor settings (colors, fonts, spacing) as JSON data inside HTML comments. When these settings contain special characters, they get encoded as Unicode escape sequences like \u00e5 or \u0026.
Sometimes other plugins or processes accidentally strip the backslash, leaving broken sequences like u00e5 instead of \u00e5. This corrupts the JSON structure, causing blocks to lose styling and display "Block contains unexpected or invalid content" errors.
This plugin scans your content for these broken Unicode sequences and repairs them by adding back the missing backslashes.
- Download the plugin zip archive.
- Go to WordPress admin panel → Plugins → Add New.
- Click "Upload Plugin" and select the downloaded zip archive.
- Activate the plugin.
The dashboard widget shows a list of posts with corrupt Unicode sequences (refreshed every 12 hours). Click "Scan for corrupt unicodes" to get a new list.
For each post, you can:
- View: Opens the post on your site
- Edit: Opens the post in the WordPress editor
- Fix: Repairs the corruption and creates a new revision
Fixed posts are removed from the list and shown as "Recently fixed" with error counts.
Only users with the kntnt_unicode_fix capability can use this plugin. By default, this capability is granted to Administrators.
You can grant this capability to other roles or individual users using capability management plugins like Members.
Modifies which post types are scanned.
add_filter('kntnt-unicode-fix-post-types', function($post_types) {
// Only scan posts and pages
return ['post', 'page'];
});Modifies which post IDs are scanned.
add_filter('kntnt-unicode-fix-post-ids', function($post_ids) {
// Limit to first 100 posts
return array_slice($post_ids, 0, 100);
});If you have questions about the plugin and cannot find an answer here, start by looking at issues and pull requests on our GitHub repository. If you still cannot find the answer, feel free to ask in the plugin's issue tracker on GitHub.
If you have found a potential bug, please report it on the plugin's issue tracker on GitHub.
Contributions to the code or documentation are much appreciated. If you are familiar with Git, please create a pull request. If you are not familiar with Git, please create a new ticket on the plugin's issue tracker on GitHub.
- Initial release
- Dashboard widget with scan and fix functionality
- Automatic corruption detection using regex patterns
- Safe fixing with WordPress revision creation
- Memory monitoring and concurrent scan protection
- Capability-based security system
- Internationalization support
- Developer filter hooks
- Batch processing support
- Preview functionality
- Detailed scan statistics