Customizations

Use classic editor for WordPress but block editor for Client Portal

If you prefer the classic editor for your WordPress site but want to use the block editor for Client Portal, you can force the block editor for Client Portal portals while keeping the classic editor everywhere else.

We strongly recommend using the block editor for Client Portal. It offers better features, improved performance, and ongoing support. The classic editor option is legacy and will receive fewer updates over time.

Once you create a portal in either the classic or block editor, you cannot convert it to the other editor type. Portals created in classic will always use classic, and portals created in block will always use block. Choose your editor before creating portals.

Force block editor for Client Portal

To use the classic editor site-wide but keep the block editor for Client Portal portals:

  1. Install a classic editor plugin (like the official Classic Editor plugin) to enable classic editing across your site

  2. Add the code snippet below to force the block editor for Client Portal portals only

You can add this snippet using a plugin like Code Snippets, or add it to your theme's functions.php file:

/**
 * Force Block Editor for Client Portal post type even when Classic Editor is enabled.
 */
add_filter( 'use_block_editor_for_post', function( $use_block_editor, $post ) {
      if ( 'leco_client' === get_post_type( $post ) ) {
            return true;
      }
      return $use_block_editor;
}, 999, 2 );

add_filter( 'use_block_editor_for_post_type', function( $use_block_editor, $post_type ) {
      if ( 'leco_client' === $post_type ) {
            return true;
      }
      return $use_block_editor;
}, 999, 2 );

This code ensures Client Portal portals always open in the block editor, even when the classic editor is active for the rest of your site.

Screenshot of a WordPress plugin interface editing a code snippet titled Force Block Editor Client Portal showing the PHP code filter that forces the block editor for the leco_client post type

If you need to use the classic editor for Client Portal portals, you can change this in the settings:

  1. Go to CP Clients in your WordPress admin sidebar

  2. Click Settings in the top menu

  3. Under Editor, select Classic

Switching to the classic editor means you'll miss out on new Client Portal features built for the block editor. We're focusing development on the block editor, so classic support will become limited over time.

Confirm editor mode and fix save issues

If portal edits do not apply or clients see a permission-style error, the editor setting in Client Portal may not match the editor type of the portal.

Check which editor a portal uses

Look at the Editor column in the list of portals to see whether a portal was built with the block or classic editor. Match the Client Portal setting to that type before editing.

  1. Go to CP Clients in your WordPress admin sidebar.

  2. Click Settings in the top menu.

  3. Under Editor, select the mode that matches the portal's editor type.

  4. Click Save Changes.

What to check when changes don't save

Settings on the Client Portal Settings page are default values for new portals and fallback values when fields are empty.

  • In a portal's Custom Branding section, if Use default settings for empty fields is set to Yes, empty fields load values from Client Portal Settings instead of staying blank.

  • Portal editing flows use different save buttons depending on the screen: Save & Show Modules, Update Project, or Save.

Was this helpful?
Was this helpful?