New Prismic Update has stripped my button styling

Describe your question/issue in detail

My company currently use Prismic to build and host email templates.

We use MJML to convert buttons to HTML on Prismic, which has worked well for years. Recently, adding a hyperlink prevents the button from converting to HTML and keeps it as MJML code. Removing the link makes it render correctly, but my team then has to manually add links elsewhere, which is cumbersome. This issue started after the recent Prismic update and removal of the legacy editor. Can someone help?

Impacted feature

Hyperlink and Buttons

What steps have you taken to resolve this issue already?

  • Upgraded to the new prismic from V1 to V2
  • I tried using HTML instead of MJML for the button, but it just turned the button into a string without rendering it correctly. It looks like adding a link makes the button lose its styling.

Errors

As stated above, the button becomes just a string and doesn’t render any styling or functions when a hyperlink is attached.

Your Role

Software Engineer

The core functionality between the Legacy editor and the new Page Builder is the same, so it shouldn't interfere with how you edit content. It's possible that there was a change in your content model fields. Could you explain more about the steps you take and any specific errors you encounter?

Thanks, mate. The codebase has remained unchanged and worked fine. However, it broke the buttons after the new page builder was released. I have rolled back some changes as far as two years back to see if anything I added affected the buttons, but to no avail. I am not getting any error codes. I'll attach a screenshot of the problem I am facing. There are two buttons, but only one is showing and working. The issue arises because no link is being attached when using the method shown in screenshot two, which causes it to break. It seems that as soon as I add a hyperlink using the method from screenshot two, all styling and functionality are stripped away.

It would be useful to look at your component code to see if you're rendering the links correctly and your route resolver setup.

We advise opening a request in our support portal if you're sharing sensitive information about your project.

Thanks