DUPLICATE/SOLVED: Page Settings only applies to the old default breakpoint

Our team is attempting to do the Mobile first approach and am having some significant issues using the Page Settings.

We have enabled custom breakpoints, created several custom breakpoints and set the mobile (smallest breakpoint) as default. We then regenerated the CSS files on the settings page.

Now when we edit the ā€œPage Settingsā€ the settings only apply on the OLD default desktop breakpoint.

We have tried uninstalling & reinstalling the bricks theme - and found that the settings were still present from the old config. So I ā€œPurgedā€ the SQL database from all bricks references which cleared the settings and allowed us to start a new installation:

-- Remove options
   DELETE FROM `wp_options` WHERE `option_name` LIKE '%bricks%';

   -- Remove post meta
   DELETE FROM `wp_postmeta` WHERE `meta_key` LIKE '%bricks%';

   -- Remove posts (templates, etc.)
   DELETE FROM `wp_posts` WHERE `post_type` LIKE '%bricks%';

   -- Remove user meta
   DELETE FROM `wp_usermeta` WHERE `meta_key` LIKE '%bricks%';

   -- Remove comments and comment meta (if any)
   DELETE c, cm FROM `wp_comments` c
   LEFT JOIN `wp_commentmeta` cm ON c.comment_ID = cm.comment_id
   WHERE c.comment_type LIKE '%bricks%';

   -- Remove any custom tables (replace 'wp_' with your table prefix if different)
   DROP TABLE IF EXISTS `wp_bricks_dynamic_data_preview`;
   DROP TABLE IF EXISTS `wp_bricks_dynamic_data_term_meta`;

However even with a fresh install the Global Page settings only apply to the OLD default base breakpoint and up.

I came across the 2 Year+ old issue and think it is related:

Hi Corry,
Welcome to the forum, and thanks so much for your report!

The issue has already been fixed in Bricks 1.10:

This was the initial report, so I’ll mark this thread as a duplicate and close it: SOLVED: Custom CSS and base mobile breakpoint

It’s not related to this report, which is, unfortunately, still in progress.

Best regards,
timmse

1 Like

Awesome thank you for the quick reply timmse. Just updated & tested it and indeed it has been resolved :smiley: