Recovering from Style Manager and Nova Blocks Update Failures

If your LT site broke right after a plugin update, identify the exact plugin before changing anything else. In recent LT reports, the two most common update-related failures were a Style Manager crash and a Nova Blocks frontend rendering regression.

Do not roll back WordPress core before you confirm which plugin changed.

Two common patterns

Match the symptoms on your site against these two patterns to pick the right recovery path below.

• Style Manager: the site goes white, shows a critical error, or locks you out of wp-admin.
• Nova Blocks: the site stays online, but decorative separators or similar elements show raw HTML or broken output on the frontend.

If Style Manager crashed the site

This is the more severe case because wp-admin may be inaccessible. When that happens, the safest recovery path is FTP or your hosting file manager.

1. Connect to your site via FTP, SFTP, or the host’s file manager.
2. Navigate to /wp-content/plugins/.
3. Delete the broken style-manager folder.
4. Upload a fresh LT-compatible copy of the plugin from your Pixelgrade account.
5. Reload the site and confirm that wp-admin is accessible again.

If a Style Manager update made your LT site inaccessible, reinstalling Style Manager 2.2.7 is the recovery version referenced in this guide.

If you need a direct download, you can get Style Manager 2.2.7 from the Style Manager 2.2.7 ZIP. The full release history is available on the Style Manager releases page.

If you are not comfortable editing plugin files directly, your hosting support team can usually perform these steps for you.

If Nova Blocks 2.1.10 broke separators or showed raw HTML

A known regression in Nova Blocks 2.1.10 caused decorative separators to render incorrectly on LT themes. Typical signs were visible <span> tags, missing separators, or broken divider output on the frontend.

1. Go to Plugins and confirm the Nova Blocks version.
2. If it is 2.1.10, update to 2.1.11 or newer.
3. Clear all site, server, CDN, and browser caches.
4. Hard-refresh the affected page and test again.

If the editor looked normal but the frontend looked broken, this specific regression is a strong match.

Direct GitHub download links

Use these direct links when your Pixelgrade account download is not available or you need a specific recovery version quickly.

• Style Manager 2.2.7 ZIP: github.com/pixelgrade/style-manager/releases/download/2.2.7/style-manager-2-2-7.zip
• Style Manager releases page: github.com/pixelgrade/style-manager/releases
• Nova Blocks 2.1.11 ZIP: github.com/pixelgrade/nova-blocks/releases/download/2.1.11/nova-blocks-2-1-11.zip
• Nova Blocks releases page: github.com/pixelgrade/nova-blocks/releases

For this specific recovery guide, use Style Manager 2.2.7 if the Style Manager update made the site inaccessible, or Nova Blocks 2.1.11 if Nova Blocks 2.1.10 broke separators or showed raw HTML.

After either recovery path

Once the plugin is restored, run through these final checks so you can confirm the fix held and capture the exact version now running.

• Clear cache everywhere, not just in the browser.
• Check the site in a private window.
• Revisit one affected page and one unaffected page.
• Note the exact plugin version now running.

When this is not the right article

This recovery guide assumes the breakage started immediately after a plugin update. Use a different starting point if your symptoms do not match that timing.

If the site did not break right after a plugin update, or the problem is limited to editor warnings like Attempt recovery or block preview failures, start with Block errors and editor troubleshooting instead.