Black Friday 2026 50% off every plan Our biggest deal of the year on #1 Joomla products.
Ends in 13d 05h 49m 49s
Claim 50% off
Staff replied SP Page Builder Joomla 6

updating from 6 to 7 and custom css

Asked by Robert 5 days ago Last activity 4 days ago

I’m testing SP Page Builder 7 (beta) on Joomla 6 with Helix Ultimate, and I have a question about upgrading existing sites that rely on custom CSS.

In SPPB 6 the button markup is sppb-btn sppb-btn-primary sppb-btn-lg (plus sppb-btn-outline for the outline look). In SPPB 7 the same button is rendered as:

<button class="sppb-el sppb-el-button sppb-el-button--lg sppb-el--ds2 sppb-btn-outline">
<span class="sppb-el sppb-el-text btn-primary">Button</span>
</button>

The type (btn-primary) is now on the inner text element, not on the button. Custom CSS written for SPPB 6, such as .sppb-btn-primary, .sppb-btn-outline.sppb-btn-primary or .btn-primary, no longer matches the button, and a generic .btn-primary rule now hits the text span instead. I see this affects more than buttons, since the whole class naming changed to sppb-el-*.

My questions:

When a site is updated from SPPB 6 to 7, are existing pages converted to the new markup, or do old addons keep rendering with the old classes?
Will the old class names (sppb-btn, sppb-addon-* and so on) stay available as a compatibility layer, and for how long? I noticed some .sppb-el-button.sppb-btn rules in elements.css, which suggests partial support.
Is there a documented, stable way to style elements globally (for example the CSS variables of the new design system, or fixed hooks) so custom CSS survives future updates?
Is there a migration guide or a list of old-to-new class names for people who maintain a lot of custom CSS?
Is there a setting to keep the SPPB 6 markup on existing sites while upgrading?

For agencies with many client sites this decides how much work the upgrade will be, so any guidance would be very helpful.

Thanks,
Robert

2 replies

Ziaul Kabir Staff

Hi Robert,

Thanks for reaching out to us.

I've checked this on my end. In SP Page Builder 7, if your Button doesn't have a link, it will be rendered as a <button> tag. If a link is added, it will be rendered as an <a> tag.

Regarding the CSS classes, even though we've introduced new class names, the existing class names will also be retained to ensure backward compatibility. So your previous custom CSS should continue to work.

If you're experiencing any specific styling issues or noticing that some of your previous CSS is no longer working, please share a few screenshots showing the issues. We'll investigate them and try to resolve them.

Thanks for your feedback!

Best regards,

Robert Asked this

Hello. I not sure about this because it wasn't an update from 6 to 7. It was a fresh SPPB 7 install and I use custom css based on SPPb 6. I have to see when it's after an update from 6 to 7 what happens

Ziaul Kabir Staff

Sure, Please, let us know If you face any issues. We'll be happy to assist you.

Best Regards,

Log in to reply.