Announcements

We're retiring the Classic editor in Client Portal

Laura Elizabeth Last update:

Client Portal has two ways to build a portal, and we're retiring one of them in 2027.

The Classic editor is the original portal builder. You add phases and modules through settings screens, and you only see what the client sees when you preview the portal.

The block editor is what Client Portal moved to in 2024. It's built on the WordPress block editor, so phases and modules are blocks you add and arrange on the page, and what you're editing looks like the portal your client will see.

Visual showing the classic editor next to the block editor

This is about Client Portal's own editor, not WordPress's. If you use the Classic Editor plugin for the rest of your site, you can keep doing that. Here's how to use the Classic editor for WordPress and the block editor for Client Portal.

If you bought Client Portal after April 2024, this probably won't be relevant to you unless you've switched to the Classic editor. If your portals are already in the block editor, nothing changes for you.

If you bought before that, you may still have portals built in the Classic editor. There's now a tool to move them across, and the rest of this post covers why we're retiring it, when, and what you need to do.

Check whether this affects you

Go to Client Portal > Portals in your WordPress admin and look at the Editor column. If you don't see "Classic" anywhere in the list, you have no Classic portals and there's nothing to do.

You'll also see a notice on your dashboard if you have any Classic portals or templates left, with a count of how many.

Screenshot showing the classic and block editor in the backend

Why we're retiring it

Client Portal moved to the block editor in 2024, and every new feature since has been built for it. Keeping the Classic editor running alongside means maintaining two versions of the same product, and in practice the Classic one has been standing still while the block editor moves on.

Retiring it means we can stop splitting our time and put all of it into the version you'll actually be using.

What you get in the block editor

If you've been on Classic for a while, a fair amount has happened without you. A few of the things you'll have once you've moved:

  • Comments and notifications on content pages
  • Pattern syncing, so you can update a section once and have it change across several portals
  • The portal gallery, with ready-made templates you can import in a click
  • The new Text & Media module, plus link lightboxes and custom module icons
  • The Five design, including the editable "Client Portal Archive" page

The timeline

When What happens
Now Classic portals keep working. Move them whenever you're ready.
31 January 2027 Support ends. Classic portals keep working, but we no longer fix Classic editor bugs. Security fixes continue.
April 2027 The Classic editor is removed. When you update, any Classic portals you have left are converted and their clients moved over for you.

So nothing breaks on a particular date. Your portals keep working the whole way through, and if you do nothing at all, they'll be converted for you in April. Moving them yourself before then just means you get to check each one first.

I'll send reminders between now and then, so it won't sneak up on you.

The short version

Move your portals before 31 January 2027 if you want support while you do it. If you leave it, they'll be converted automatically in April 2027.

How moving a portal works

You move one portal at a time, so there's no big switchover day.

  1. Convert the portal. This makes a block editor copy, and your clients keep seeing the Classic version.
  2. Check the copy and fix anything that didn't carry over the way you'd like. You can preview the Classic version to compare.
  3. Move your clients over. They see the new version at the same link, and nobody gets an email.

The Classic version stays as a backup until you delete it, and you can move clients back to it if something isn't right. Templates work the same way, so new portals created from your registration form or WooCommerce products pick up the block version too.

👉 Read the step-by-step guide

Have any questions?

Or something that won't convert cleanly? Reply to any of the reminder emails or get in touch and I'll help you work through it.

Laura Elizabeth Read full bio
Laura created Client Portal in 2016 after working as a freelance designer for a decade. Client Portal was born out of the need for a simple tool that allows clients to access their project deliverables. Since then, it has grown into an 8,000+ customer-strong product that helps any service provider, from freelancers to law firms. In her spare time, Laura likes to sew clothes and quilts, play the piano, and hang out with her husband and children.

Related articles

  • Join us in coding a more inclusive future!

    We’re delighted to announce a special initiative that can turn your software needs into a force of change. We’ve teamed up with Freemius to support Girls Who Code and contribute to a more diverse tech future. Girls Who Code is on a mission to close the gender gap in technology. Did you know that in...

    Read more
  • Coming soon: a fresher, cleaner Client Portal

    We've been heads-down on a batch of updates to Client Portal, and they're nearly ready to go. Nothing has been rebuilt from scratch (your portals will look familiar) but a lot of the small friction points have been ironed out. Here's a quick summary of what's changed: A refreshed portal design The layout is the...

    Read more