Skip Navigation

WordPress 5.5 breaks post revision links for CPTs registered with Types

Resolved

Symptoms

When you register a custom post type with Types you can check the option for supports post revisions, and then you will see links to edit revisions on the normal post edit screens (both Blocks and Classic).

After updating to WordPress 5.5 these edit links disappear and revisions cannot be accessed.

The problem only appears to occur for post types registered with Types. If you manually register post types the post revision links are still available.

Workaround

5 thought on WordPress 5.5 breaks post revision links for CPTs registered with Types

  • Hello, wanted to report an additional detail regarding this error. I have not created any Custom Post Types (I am instead using Custom User Fields and User Forms), but the disabling of revisions seems to happen when I simply have the Toolset Forms plugin activated.

    • As we discussed in the support thread, I cannot reproduce the issue with the Forms plugin. Revisions for standard posts are available with or without Forms active, the issue is confirmed to happen with custom post types registered with Types. If you can demonstrate the issue on your site with just Toolset Forms, please re-open the existing thread or create a new one and provide a copy of your site as described here: https://wp-types.com/faq/provide-supporters-copy-site/

  • Hi Can you confirm if this has been fixed please? We have built an entire site that requires WP to be kept up to date to stay secure and updating to 5.5 has broken most of the application. This is an internal proprietary system and so the issues cannot be seen by non logged in users. Thanks

    • The new releases were mostly focused on new features, and the next dev cycle will tackle the backlog of bug-fixes, including this one. Sorry that means waiting a little longer.

  • Yesterday we released Types version 3.4.2. Re-testing this issue on a brand new installation with the updated version I can no longer reproduce the problem, and am closing this erratum.

Comments are closed