Current

This document is valid for the current version of Plone.

I think I've found a bug in Plone. Where should I report it?

« Back to Table of Contents

Security-related bugs should be reported via email to security(at)plone.org. Both security issues in Plone or its add-on products can be reported here, and we will contact the relevant maintainer if necessary.

All other Plone bugs should be reported via a ticket (issue) in an appropriate on-line tracker. For best results, you will need to do some research to figure out which such tracker is most appropriate for your situation. This is because development of core Plone components, third-party products (add-ons / plugins), other third-party packages, and Plone documentation are all handled by different teams around the world, each with their own work schedules and development infrastructure. You should anticipate needing to remain engaged with the issue after reporting -- to include working on the problem yourself and offering a patch if possible -- in order to improve the likelihood of a prompt resolution.

If you think your bug involves a core component of Plone, check to see if that product/package has its own repository at https://github.com/plone. If it does, use the associated issue tracker to submit your report. If it does not:

  1. Check the legacy issue tracker for recent activity and, if it appears to still be in active use for that product, submit your report there.
  2. In the likely event that there is no recent activity on the legacy tracker, submit your issue via the catch-all CMFPlone tracker on GitHub.
Note: after figuring out where to post your report, but before doing so, please search tracker to make sure that nobody else has already reported this issue and that it hasn't been already fixed in a new version.

Bugs for third party products should be reported in the repository they request. This is usually indicated on the pypi page for the product or on the product listing in the products section. In some cases, you may need to resort to using a web search engine or even asking for guidance in the plone irc channel.

If the problem is in the plone.org documentation, report it via the Plone documentation tracker on GitHub.

The following legacy recommendations need to be checked and updated. Right now they point people into the legacy tracker, which may no longer be correct:

If the issue is related to plone.org (this website), please file the ticket under the component "Website".

Internationalization bugs (i18n) should be filed in the Plone issue tracker under the Internationalization component.

Translation bugs (l10n) should be filed in the dedicated translation issue tracker on plone.org.