Bogue in Color Library - Forum | JoomShaper
Solved SP Page Builder

Bogue in Color Library

Asked by Pascal Wickert 1 year ago Last activity 1 year ago

Hello,

I just wanted to report what seems to be a bug in the Color Library settings.

I had quickly created a few custom colors for a new site I’m working on. After using them across several pages, I realized I wasn’t consistent with the naming. So, I went back to the settings and updated the color names. Unfortunately, this broke the link between the color definitions and the elements using them on the pages.

It seems that while the interface allows renaming colors, doing so causes the associated styles to be lost across the site. Ideally, renaming a color should not affect how it’s applied in the content.

Best regards,

Accepted answer

Marked as the solution
Ofi Khan Staff

Hello Pascal Wickert,

Thank you for reaching out to our technical support forum. I’m sorry to hear about the trouble you’re experiencing.

I will ask the developer team to check and fix it on the next release.

Best regards

3 more replies

Rashida Rahman Staff

Hi there!

Thanks for reporting this.

I have tested, and found the behavior you have reported here. However, I will forward this to the team to know if this is intensional behavior or a mistake.

Best regards,

Pascal Wickert Asked this

Thank you, Ofi and Rashida,

Fortunately, I had made a backup just before making the change. Restoring the website was much quicker than going through all the sections across my 70 SP Page Builder pages. 😉

Best regards,

Rashida Rahman Staff

You're always welcome:)

Have a nice day!

Pascal Wickert Asked this

Hello,

I assume that the latest version of SP Page Builder, with the introduction of color variables and the new Global Color mode, has resolved this issue? I haven’t tested it yet myself — I didn’t want to risk breaking the site. 😉

Can you confim?

Best regards,

Ofi Khan Staff

Unfortunately, it has not been fixed. If you change the color library name, then you have to reassign it on the pages. Hopefully, we will find a workaround on the next version.

Log in to reply.