GenerateBlocks scans your content when a page loads and generates CSS based on your chosen values in each block.
If you’re generating an external CSS file (GenerateBlocks > Settings), a file will be created with the generated CSS and placed in your wp-content/generateblocks
.
This method works great and is better than inline embedding when it comes to performance. However, it can conflict with some servers/caching methods.
Removing Query Strings
Some performance/caching plugins come with an option to remove query strings. If you do this, your generated CSS file will not know when you’ve changed something on the page. This means your changes won’t display, as the browser has cached the file. Doing this can also prevent the file from loading at all when combined with caching plugins.
Solutions
a) Disable this option, or use Inline Embedding for the CSS Print Method in GenerateBlocks > Settings.
b) Regenerate your CSS files in GenerateBlocks > Settings.
Caching
Some caching plugins seem to conflict with the file generation. One we’ve observed a few times is the Siteground Optimizer plugin. If you find your pages aren’t loading their styles, it’s likely due to a caching plugin or your server caching.
Solutions
a) Choose Inline Embedding for the CSS Print Method in GenerateBlocks > Settings.
b) Regenerate your CSS files in GenerateBlocks > Settings.