Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Plugins lack a consistent enabled/disabled option

Open
#18,329 0 comments 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

@lakshmidad is already working on this.

Since Oct 9, 2026.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
68/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
backend

Research direction

Start with templates/plugin/src/index.ts and compare the configuration types linked in plugin-multi-tenant, plugin-mcp, and plugin-seo. Review the affected plugin packages listed in the issue and align their on/off configuration with the template. Done means every listed plugin uses the same option and disabled plugins still add their collections and fields for schema consistency.

Written by the indexing model from the issue text.

Description

area: templates Bug created-by: Contributor plugin: ecommerce plugin: form-builder plugin: import-export plugin: mcp plugin: nested-docs plugin: redirects plugin: search plugin: seo plugin: stripe
Describe the Bug

Most official plugins can't be turned off via config, and those that can don't agree on the option name:

  • enabled?: boolean: plugin-cloud-storage, plugin-multi-tenant, plugin-sentry
  • disabled?: boolean: plugin-mcp, templates/plugin
  • no option: plugin-ecommerce, plugin-form-builder, plugin-import-export, plugin-nested-docs, plugin-redirects, plugin-search, plugin-seo, plugin-stripe

Expected: every plugin supports the same on/off option. Per the plugin template, a disabled plugin should still add its collections/fields so the DB schema stays consistent.

Link to the code that reproduces this issue

https://github.com/payloadcms/payload/blob/124b55a/packages/plugin-seo/src/types.ts

Reproduction Steps

Compare the plugin config types:

Which area(s) are affected?

plugin: ecommerce, plugin: form-builder, plugin: import-export, plugin: mcp, plugin: nested-docs, plugin: redirects, plugin: search, plugin: seo, plugin: stripe, area: templates

Environment Info
payload main @ 124b55a (4.0.0-canary.37)
Dominant language
TypeScript
Stars
45.5k
Forks
4.3k
Avg merge
1d 19h
Merged PRs (30d)
295

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from payloadcms/payload

All issues in payloadcms/payload

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.