Keep existing classes when importing templates?

How To
1

Before version 1.12:
When importing templates, if an element had a class that already existed in your site, Bricks would keep that class and use your existing class styles.

After version 1.12:
Bricks now removes any duplicate classes during template import. The imported elements arrive without those class names attached.

The Global Class Import Manager doesn’t seem to provide an option to restore the old behavior of keeping duplicate classes.

1 Like
2

I have the same issue with importing frames and acss utility classes, I think it was your post on their forum I saw?

1 Like
3

image

4

Has anyone figured out a solution for this? I have the same issue with Frames/ACSS. This new Bricks “feature” is more of a hindrance now. And there isn’t a way to turn it off. If we select to “Never” show the import manager, it just removes classes it thins are conflicts. Super annoying.

5

Are you still running into this in 1.12.2? This should’ve been fixed but if you’re still running into this let me know and I’ll double check

6

Not this issue exactly. Is it possible to completely disable the Global Class Import Manager? I just want it to add templates like it did before the Global Class Import Manager was added. If I select “Never” it automatically discards conflicting classes. Most classes when importing a Frame are marked as “conflicting”, so they aren’t added. Having to do a whole bunch of clicks every time I add a new Frame is SUPER annoying and time-consuming.

7

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:

  1. Details of the local class
  2. The template being imported
  3. 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.