Before the Global Class Import Manager was introduced, conflicting classes (where the class name already existed locally) were always automatically discarded. Users had no control over this.
Now, the issue you’re likely referring to is a bug that initially broke expected behavior:
Previously, when an imported class conflicted with an existing local class on your site, Bricks would discard the imported class’s styles but still attach the local class to the imported elements. When the Global Class Import Manager was first introduced, this behavior was broken: Bricks was removing the class completely instead of attaching the local one.
This should’ve been fixed in Bricks 1.12.2. If you’re still experiencing issues where imported elements lose their class names instead of attaching the local version, please report it. You can either email help@bricksbuilder.io or create a new forum bug report. In your report, please include:
- Details of the local class
- The template being imported
- The steps you’re taking vs. what you expect to happen
We’ll take a look and fix any remaining issues as the “Never” option should behave just like before the Global Class Import Manager was introduced.