Security-related bugs should be reported only via email to security@plone.org. Security issues in Plone or its add-ons can be reported this way, and the Security Team will contact the relevant maintainer if necessary. DO NOT POST SECURITY-RELATED BUGS IN PUBLIC MAILING LISTS OR DISCUSSION FORUMS.

Bugs That Are Not Security-Related

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.

Bugs in Plone Core

If you think your bug involves a core component of Plone, check to see if that component has its own repository at https://github.com/plone. If it does, use the component's issue tracker to submit your bug report. If the component does not have its own repository there, submit your bug report in the catch-all CMFPlone tracker on GitHub. Note: after figuring out where to post your report, but before doing so, please search the issue tracker to ensure this issue hasn't already been reported and that it hasn't already been fixed in a later version of the component.

Bugs in Plone Add-ons

Bugs in Plone add-ons should be reported in their repository's issue tracker, which is usually listed in the add-on's listing in the plone.org add-ons. In some cases, you may need to use a web search engine or ask for guidance in the pypi or in one of the Plone discussion forums.

Bugs in Plone Documentation

If the problem is in the Plone documentation, report it in the documentation tracker. If the problem is in the Plone training manuals, report it in the training issue tracker.

Bugs in this Website (plone.org)

If the issue is related to plone.org (this website), please file it in the plone.org issue tracker or use the Contact form to send feedback. About Plone Try Plone Download Plone Plone Releases Documentation Training Security Roadmap GitHub Community Forum Chat Contribute code Report an issue News and events Conference Join the Plone newsletter Foundation Join the foundation Board Donate Sponsors Apply for Event and Sprint Funds Code of conduct Foundation members Shop Follow us Mastodon Twitter Instagram YouTube Linkedin Facebook Privacy Policy Cookie settings

The text and illustrations in this website are licensed by the Plone Foundation under a Creative Commons Attribution-ShareAlike 4.0 International license. Plone and the Plone® logo are registered trademarks of the Plone Foundation, registered in the United States and other countries. For guidelines on the permitted uses of the Plone trademarks, see https://plone.org/foundation/logo. All other trademarks are owned by their respective owners.