Updates and upgrades are essential for maintaining DigiBlocks functionality, security, and accessing new features. However, sometimes issues can occur during the update process that affect your website’s appearance or functionality.
Common Update Issues
Assets Not Regenerating After Update
When DigiBlocks updates, the plugin’s CSS and JavaScript files may need to be regenerated to ensure compatibility with new features or fixes. If your blocks appear broken or unstyled after an update, the asset files may not have been properly regenerated.
Navigate to DigiBlocks > Settings and click the Regenerate All Assets button. This process will:
- Scan all posts and pages for DigiBlocks content
- Recreate CSS files for each post containing blocks
- Regenerate JavaScript files for interactive functionality
- Process font files if local Google Fonts are enabled
- Clean up orphaned asset files
Settings Reset or Missing
DigiBlocks stores settings in the WordPress database using the digiblocks_settings option. If settings appear to be reset after an update, check if your global settings are still configured:
- Content width and max width values
- API keys for reCAPTCHA, Google Maps, and image providers
- Newsletter platform configurations
- Font loading preferences
If settings are missing, you may need to reconfigure them manually in DigiBlocks > Settings.
Block Categories Not Appearing
After updating, if DigiBlocks blocks don’t appear in the block editor or categories are missing, this could indicate a plugin registration issue. The plugin registers multiple block categories including:
- DigiBlocks (main category)
- DigiBlocks DigiCommerce (when DigiCommerce is active)
- DigiBlocks WooCommerce (when WooCommerce is active)
- DigiBlocks Theme (for theme-related blocks)
Clear any caching plugins and refresh the block editor. If the issue persists, deactivate and reactivate DigiBlocks.
Asset File Conflicts
CSS Styles Overridden
DigiBlocks generates individual CSS files for each post containing blocks. After updates, these files may need regeneration if the underlying CSS structure has changed.
The plugin creates files in the format digiblocks-{post_id}.css in the uploads directory. If styles appear incorrect, regenerate assets to ensure the latest CSS is applied.
JavaScript Functionality Broken
Interactive blocks rely on JavaScript files generated per post. If countdown timers, animations, or form functionality stops working after an update, the JavaScript assets may need regeneration.
Files are created as digiblocks-{post_id}.js and loaded only on pages containing DigiBlocks. Regenerating assets will recreate these files with the latest functionality.
Font Loading Changes
DigiBlocks includes a font management system that can load Google Fonts locally or from CDN. Updates may change how fonts are processed, especially if switching between local and CDN loading.
If fonts appear to load incorrectly after an update, regenerate assets and verify your font loading preferences in settings. The system will reprocess all font files based on your current configuration.
Database and File System Issues
Permission Problems
DigiBlocks creates asset files in the WordPress uploads directory. If file permissions are too restrictive, the plugin may not be able to create or update these files after an update.
Ensure the uploads directory and DigiBlocks subdirectory have appropriate write permissions for the web server process.
Orphaned Files
Over time, asset files may accumulate for deleted posts or pages. The regenerate assets process includes cleanup functionality to remove orphaned files.
If you notice excessive file accumulation in the DigiBlocks assets directory, running the regeneration process will clean up unnecessary files.
Block Manager State
DigiBlocks tracks which blocks are active using the digiblocks_inactive_blocks option. Updates shouldn’t affect this setting, but if blocks unexpectedly become inactive, check the Block Manager in DigiBlocks > Dashboard.
Resolving Update Issues
Clear All Caches
After updating DigiBlocks, clear all caching layers including:
- WordPress object cache
- Page caching plugins
- CDN cache
- Browser cache
Caching can prevent updated files from loading properly and cause functionality issues.
Regenerate Assets
The most common solution for post-update issues is regenerating all DigiBlocks assets. This comprehensive process ensures all files are current and compatible with the updated plugin version.
Check Plugin Conflicts
If issues persist after updating, temporarily deactivate other plugins to identify conflicts. Some plugins may interfere with DigiBlocks asset generation or block registration.
Theme Compatibility
Ensure your active theme is compatible with the updated DigiBlocks version. Theme conflicts can cause blocks to display incorrectly or functionality to break.
File System Verification
Verify that all DigiBlocks files were properly updated by checking the plugin version in Plugins > Installed Plugins. Incomplete updates can cause various functionality issues.
Settings Validation
Review all DigiBlocks settings after updating to ensure configurations are still valid. API keys, integration settings, and preferences should be verified and updated if necessary.
If problems persist after trying these solutions, the issue may require more advanced troubleshooting or plugin-specific debugging to identify the root cause.