Front end editing of website built on uynson framework
Dear Brizy Support Team,
I am writing to request urgent assistance regarding a conflict between the Brizy Pro builder and a premium theme's pre-built content.
The Setup:
-
Theme: Odrin - Book Selling WordPress Theme (ThemeForest).
-
Paid Builder: Brizy Pro (Annual License - I am committed to using Brizy as my primary editor).
-
Conflict Source: The theme's demo content was originally built and installed using the now-deleted Unyson Framework Page Builder.
The Problem (The "Blank Page" Issue): When I navigate to the homepage and click "Edit with Brizy," the editor loads but displays a completely empty canvas, prompting me to "START BUILDING YOUR PAGE."
The theme's content (e.g., the book grid, headlines, etc.) is visible on the front-end, but is inaccessible and uneditable in the Brizy interface. I suspect the old Unyson shortcodes are blocking Brizy from recognizing the content structure.
My Goal: My priority is to use Brizy to easily edit the existing demo content, specifically the book product grids and text blocks.
Questions for Your Team:
-
Is there a standard method or a tool within Brizy to migrate or translate the old, nested Unyson shortcode content into an editable Brizy structure?
-
If translation is impossible, is my only solution to delete the page and manually rebuild the entire homepage using Brizy's native blocks and the Odriin theme's universal shortcodes (e.g., the
[odrin_featured_books]shortcode)?
Strategic Side Question (Brizy Cloud): I am running a very lean, annual-cost-optimized business model. Would migrating my site to Brizy Cloud resolve this shortcode conflict, or would the underlying Unyson code still prevent editing? (I need to know if the extra expense of the Cloud service is technically necessary).
Thank you for your time and expertise. I look forward to your guidance so I can proceed with building my storefront.
Best regards,
Relebogile
-
Hi Relebogile,
Thank you for contacting us.
I understand how frustrating this situation can be. The issue appears because the Odrin theme’s demo content was originally built with Unyson. While the old Unyson shortcodes still display correctly on the front-end, Brizy isn’t able to read or convert them, which is why the editor loads an empty canvas. In this case, the only reliable solution is to rebuild the homepage using Brizy and include the theme’s shortcodes where needed.
About Brizy Cloud, unfortunately it wouldn’t resolve this shortcode conflict either, as the underlying structure would still be incompatible. Brizy Cloud is only recommended if you plan to rebuild the entire site using Brizy from the ground up, and it’s important to note that third-party WordPress plugins cannot be used there.
If you have any other questions please let us know.
Best regards,
Ariel H.0 -
Thank you for the advice, I have been having a back and forth trying to figure this out. I will try to rebuild from the start.
Best regards
Relebogile
0
Please sign in to leave a comment.
Comments
2 comments