Edit by Post Type (PRO)

Location: FDP → Backend → Edit by Post Type

What this page is for

Edit by Post Type lets you deactivate plugins on WordPress admin edit screens based on the post type.

It applies to URLs like:

wp-admin/post.php?post=61&action=edit

One row represents one post type. The settings for that row apply to every edit screen of that type (all pages, all products, all posts, and so on).

This is useful when you need certain plugins only while editing pages, products, or a custom post type, and you want them disabled for other edit screens.

How it differs from Backend Singles

Page What it controls
Backend Singles Individual admin screens (Dashboard, Plugins, Settings, and also Edit Single … rows mixed with menu items)
Edit by Post Type Only admin edit screens (post.php?post=XX&action=edit), organized by post type

Use Edit by Post Type when you specifically want rules for editing content without browsing the full Backend Singles matrix.

Settings for the same post type are shared with the matching Edit Single … rows in Backend Singles. Changing one location updates the same option used by the other.

How to use it

  1. Open Backend → Edit by Post Type.
  2. Find the row for the post type you care about (for example Edit Single Page or Edit Single Product).
  3. Uncheck the plugins you want to deactivate on that post type’s edit screens.
  4. Optionally configure the theme column for that row.
  5. Click Save all changes.
  6. Open an edit screen for that post type and verify that only the plugins you need are loaded.

What is included

  • Posts (post)
  • Pages (page)
  • Custom post types that have an admin UI (show_ui => true)

Each post type with an editable admin UI gets its own row.

What is not included

  • Frontend pages (use Singles, Post Types, Custom URLs, and similar options)
  • Admin list screens (edit.php, edit.php?post_type=product) — use Backend Singles or Backend URLs
  • Other admin pages (Settings, Plugins, Dashboard) — use Backend Singles
  • Specific posts by ID — use Backend Singles, Backend URLs, or other URL-based options if you need per-item rules

Typical use cases

  • Keep page builders, SEO plugins, or ACF active only when editing pages.
  • Load WooCommerce-related plugins only on product edit screens.
  • Reduce plugin load (and conflicts) while editing a specific custom post type.
  • Speed up the Block Editor by disabling unnecessary plugins on that post type’s edit screen.

Priority and related options

Plugin deactivation in the WordPress admin can also be affected by:

  • Backend Singles (shared keys for Edit Single … rows)
  • Backend URLs
  • Disabled on backend (backend everywhere)
  • Actions / Integration (for example Saving Single Post for classic editpost saves)

For controlling which plugins load on the edit screen itself, use Edit by Post Type (or the corresponding Edit Single … row in Backend Singles).

Saving Single Post (Actions → WordPress Core) only affects the classic POST save using action=editpost. It does not replace edit-screen rules, especially when Gutenberg saves content through the REST API.

Tips

  • After changing settings, perform a hard refresh or open the edit screen in a new browser tab to verify the result.
  • Use preview or row actions (when available) to test combinations before relying on them in production.
  • If a post type does not appear, verify that it is registered with show_ui enabled and visible in the WordPress admin.

Short summary

Edit by Post Type lets you deactivate plugins on post.php?post=XX&action=edit screens based on the post type.

It is a PRO-only feature and shares its settings with the corresponding Edit Single … rows in Backend Singles.