Pro 2.3.0 Classic Raw Content Element not working after Update

Support
#1

Hey guys

I guess I found a bug.
I used a lot of Raw Content Elements on my website, entered plain HTML and styled it via custom CSS file in child theme. (I tried to create my website as clean as possible. with the Raw Content Elements I could save a lot of HTML output, thats why I did it that way).

I updated to Pro 2.3.0.
I did it via FTP, renamed pro folder to pro_2, uploaded and extracted the new pro.zip. Reloaded my website, then deleted the old Pro installation. So this shouldn´t be the problem.

I deleted all cache, reloaded page and began to edit Site with Pro. When the page was loaded, the Raw Content Elements look like this:

Before I could see the styled Raw Content Element, could click and change it.
Now it´s a bit messy. I think this is some bug that can be solved.

If I missed something, please give me a hint how to overcome the problem.
I switched back to the previous Pro Version, there everything works fine again.

I tested Pro 2.3.0 in Beta and the Bug never appeared. I could use Raw Content Elements as I´m doing normally. So I guess it happens only after updating an existing Pro installation with the newest version.

Beside that I´m in love with the new Version of Pro, awesome Job!
Best regards
Mike

#2

Hi Mike,

Thanks for reaching out.

Sorry to hear you’re having this issue, but upon checking in my updated installation, the raw element works perfectly. Perhaps it’s due to the content of the raw content?

Would you mind providing your site’s URL and admin login credentials in a secure note? I like to directly check it on your end to see what’s going on. I like to copy the same raw content as well and test it on my installation.

Thanks!

#3

Hi guys,

Same issue here (see screenshot enclosed) after updating X Pro from 2.2.6 to 2.3.2.

Of course, I have deleted all caches but with no results.

With thanks in advance.

Regards,

B.

#4

I’m sorry you’re running into the same issue. Would you mind opening your own thread? We could take a closer look there. You could also add a secure note with login credentials on your own topic.

#5

Hi guys!

Thanks to the 2.3.3 upgrade, that bug has just been resolved. :thumbsup:

Regards,

B.

#6

Glad to hear that. :slight_smile:

#7

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.