Idea
Detect when a user has changed Bricks' base breakpoint (or otherwise configured breakpoints in a way that conflicts with the framework's breakpoint-free/fluid approach) and surface a clear warning in the WP admin (e.g. on the plugin's Bricks settings page or as an admin notice inside the Bricks builder).
Why
Currently there's no handling or warning around Bricks breakpoint configuration at all — a user who overrides the base breakpoint has no way to know that's what's silently breaking their layout. This is a common, hard-to-diagnose first-run footgun; a one-time detection check would save significant support/debugging time.
Scope
- Read Bricks' breakpoint settings (via its own options API) and compare against the expected/safe configuration.
- Surface a warning (admin notice or inline in the Bricks settings page) when a conflict is detected, with a short explanation of what to fix.
- Should be a passive check, not an automatic override of the user's Bricks settings.
Idea
Detect when a user has changed Bricks' base breakpoint (or otherwise configured breakpoints in a way that conflicts with the framework's breakpoint-free/fluid approach) and surface a clear warning in the WP admin (e.g. on the plugin's Bricks settings page or as an admin notice inside the Bricks builder).
Why
Currently there's no handling or warning around Bricks breakpoint configuration at all — a user who overrides the base breakpoint has no way to know that's what's silently breaking their layout. This is a common, hard-to-diagnose first-run footgun; a one-time detection check would save significant support/debugging time.
Scope