thrive-architect-feature-responsive-editing-1080

PageLines 5 Alternative – Why I migrated to Thrive Themes

This post may contain affiliate links. Please read my disclosure for more info.

I have used PageLines Platform 5 (Pro version) for years on several of my personal and business sites. A few months ago I realized that Andrew Powers, the brain behind PageLines, had abandoned the page builder I had so heavily invested in. So it was time to find alternatives.

Based on a recommendation from one of the other users of the PageLines Forum, I decided to give Thrive Themes and the Thrive Architect a try. In this blog post, I describe my journey and migration from PageLines to Thrive Themes.

A brief history of PageLines

I began my journey with what was called the PageLines Framework several years ago. After that, I migrated to PageLines DMS, which offered a JavaScript-based front-end editor for Chrome. I leveraged DMS to build the webpage of the company I used to work for as well as for this blog.

Then PageLines released Platform 5, a WordPress plugin that would work with any theme and in any browser. That was incredible because I could finally ditch Chrome and use Safari instead for making changes to my websites via the built-in front-end editor.

Abandoned PagesLines Themes
Abandoned PagesLines Themes

Instead of using a third-party theme, I decided to stick with the new PageLines Framework, a clean and mobile-friendly WordPress theme that PageLines had optimized for Platform 5.

At some point last year it occurred to me that none of the PageLines plugins and extensions had been updated in a while. Fortunately, I had not run into any major bugs or issues, and so the lack of updates wasn’t a significant concern. But I kept wondering about potential code vulnerabilities that I didn’t know about and that hackers could exploit.

content: "\f155\00a0";

The only issue I encountered as related to the PageLines Custom LESS plugin not saving UNICODE characters correctly. For example, when I wanted to use font-awesome icons via CSS, PageLines would strip out the leading backslash and break my character code.

As a result, I ditched the Custom LESS extension and loaded my CSS code from a separate file instead. No big deal.

PageLines was trying to keep the lights on

PageLines User Forum