My pro form element is not loading the css when generated on the frontend when I have the Bricks CSS rendering method set to external files. This fixes instantly when I change to inline CSS rendering, but don’t want to be forced to use inline just for this one element. I have recreated the issue on a brand new simple pro form with no attached scripts etc.
Thanks for the clear report — we dug into this and found a real bug on our side.
With “External Files”, Bricks writes the page CSS into a static file whenever the post is saved. If that save happens outside the Bricks builder (a plain update from the WP admin, or a plugin re-saving the post in the background), the Bricksforge elements aren’t registered in that request, and Bricks silently writes the file without any of the Pro Forms rules. Inline CSS is generated fresh on every page load, which is why switching “fixes” it instantly. We’ll fix this so the file is always complete.
Until then, you can repair affected pages by re-saving them in the Bricks builder, or via Bricks → Settings → Performance → Regenerate CSS files — then clear any page/CDN caches. If the styles disappear again later, it’s this bug re-triggering after another save outside the builder.