Keep plugin support centered on the current plugin version, supported WordPress/PHP environments, installation steps, known conflicts and approved troubleshooting. Use WordPress.org forums where appropriate, but give commercial or product-specific customers one official support destination that stays current across releases.
What matters most
- Make compatibility a first-class support field, not a footnote.
- Tie troubleshooting answers to the plugin version they apply to.
- Separate community forum support from the official product support destination when needed.
- Publish known conflicts before buyers open another support thread.
- Do not carry old fixes into a new version without reviewing them.
Compatibility is part of the support answer
WordPress itself exposes plugin compatibility information because whether a plugin has been tested or updated matters to users. For a commercial plugin, your support information should be even more specific: supported WordPress versions, PHP requirements, relevant dependencies and any known theme or plugin conflicts.
When a buyer reports that something does not work, the fastest path to a useful answer often starts with version context. Without that context, an old fix can be worse than no fix.
Use the forum for the forum, and your product support for the product
WordPress.org provides support forums for plugins in the directory, and its developer documentation explains how plugin authors and support representatives can use them. The forums are useful community infrastructure, but they do not have to become the only place your support knowledge lives.
For premium customers or product-specific documentation, an official destination under your control can hold the current compatibility matrix, installation guidance, known conflicts and approved answers. You can then link to that destination from your own plugin UI, docs or customer onboarding where appropriate.
Build a plugin support page around the questions that repeat
The recurring support set is usually smaller than it feels. Installation and activation, updates, license behavior, WordPress/PHP compatibility, conflicts with themes or other plugins and troubleshooting known issues account for a large share of repeat work for many plugins.
Make those topics visible before the buyer writes a new message. If a fix only applies to a specific release, label it clearly.
- Current plugin version
- Supported WordPress and PHP versions
- Install and update steps
- Known conflicts
- Known issues and safe workarounds
- Approved troubleshooting answers
Treat each release as a support review
When you release a new plugin version, review the support knowledge alongside the code. Confirm that compatibility statements are still correct, remove resolved known issues and decide whether previous troubleshooting still applies.
A version-specific support model makes this review explicit. The new release starts with a clean context, and you deliberately keep only the answers that remain true.
Practical checklist
- Publish the current plugin version and supported WordPress/PHP versions.
- Document installation and update steps.
- List known conflicts and known issues.
- Label troubleshooting by version when the answer is version-dependent.
- Place the support URL in your plugin Help/Settings area, docs or customer onboarding.
- Review support knowledge as part of every release checklist.
Frequently asked questions
Do WordPress plugin developers have to provide free support?
WordPress.org's plugin forum guidance says developers are not required to offer free support. The forums have their own rules, while commercial support can use the official channels appropriate for the product.
What compatibility information should plugin support show?
At minimum, the current plugin version, supported WordPress versions, relevant PHP requirements and any dependencies or known conflicts that materially affect installation or use.
Why keep support knowledge version-specific?
Because a workaround or compatibility statement that is correct for one release can become wrong after the plugin, WordPress core, PHP or another dependency changes.
Primary sources
Platform-specific statements in this guide are based on the official documentation below.
- WordPress Plugin Handbook — Using the Forums
- WordPress Documentation — Manage Plugins and compatibility
SupportKeep is an independent product and is not affiliated with WordPress or the WordPress Foundation.
Turn the support system into one permanent buyer-facing page.
Keep the current version, compatibility, known issues and seller-approved buyer answers together. If approved sources do not support an answer, SupportKeep says it is not documented instead of guessing.