Hi

Thanks for contacting us. And sorry for this inconvenience. I will inform our team about it.

-Regards.

ok thanks for your feedback.

do you know when this bug will be fixed ?

I hope before christmas...because this kind of bug is very problematic when you have a lot of migration to do.

Ok I will inform our team again so that they will try to solve it ASAP.

hello,

do you have any news about this fix ?

thanks

Sorry not yet, allow our team some time please.

Hi,

What's news about this bug ? I saw you release SP page builder 5.2.0 It is very good to release new features, but could you please make an effort to correct bugs? I think the maturity and the stability of the product is equal important than having new features.

Thanks

Sorry for your issue. It's already on our bug list, I hope the team will solve it soon. There is too much workload pressure that's why it takes time. I apologize on behalf of them.

Hello,

i have the same problem in 5.2.4.

Is there meanwhile a solution for that please?

Thanks and have a nice day.

please @joomshaper : correct all the bugs reported. this has been reported for a while.....

@Mehtaz same problem, always. please do some tests before saying it id solved.

reminder : BEFORE migration some titles were uppercase and AFTER migration if I change them to lowercase I have some issues.

You do not need super admin access. you can try by yourself from your computer.

• step 1 : select a website done with SP page builder 3.X
• step 2 : check you have some H1 and H2 titles uppercase
• step 3 : upgrade SP page builder to version 5.X
• step 4 : check your H1 and H2 titles and change them to lowercase, you will see errors.

so this has been corrected in latest release 5.2.5 ?

I check this out and I come back to you. @sauerlu : if you can also from your side and tell me?

Hi, I've updated to 5.2.5 now. Cleared my browser cache, opened the website in multiple browsers, on diffrent devices, but for me the H1 an H2 as still NOT on uppercase.

Thanks.

thanks for the feedback @sauerlu

@Mehtaz Afsana Borsha : so the problem still exist, even if updated to version 5.2.5. Please check this out

Hi,

Sorry I was out for some days.

I've solved the "problem" by adding only a new css rule to the override.css

any news please?

I need access on backup file.