tonyair/silverstripe-framework
1
0
Fork 0
mirror of https://github.com/silverstripe/silverstripe-framework synced 2024-09-18 23:46:21 +02:00
Code Issues Projects Releases Wiki Activity
bc941c18b6
silverstripe-framework/docs/en/misc/contributing/issues.md
Ingo Schommer 786d0516da More docs on CMS issue reporting
2013-01-22 15:10:50 +01:00

3.6 KiB
Raw Blame History

Contributing Issues and Opinions

« Back to Contributing page

Reporting Bugs

If you have discovered a bug in SilverStripe, we'd be glad to hear about it - well written bug reports can be half of the solution already! Our bugtracker is located on open.silverstripe.org.

Before submitting a bug:

  • Ask for assistance on the forums, core mailinglist or on IRC if you're unsure if its really a bug.
  • Search for existing tickets before reporting a new one
  • Is this a security issue? Please follow our separate reporting guidelines below.
  • Is this a issue with the core framework or cms? Modules have their own issue trackers (see silverstripe.org/modules)
  • Try to reproduce your issue on a clean installation, maybe the bug has already been fixed on an unreleased branch?
  • The bugtracker is not the place to discuss enhancements, please use the forums or mailinglist. Only log enhancement tickets if they gather a large interest in the community and the enhancement is likely to be implemented in the next couple of months.

If the issue does look like a new bug:

  • Create a new ticket
  • Describe the steps required to reproduce your issue, and the expected outcome. Unit tests and screencasts can help here.
  • Describe your environment as detailed as possible: SilverStripe version, Browser, PHP version, Operating System, any installed SilverStripe modules.
  • Add keywords to help us organize issues, and please be realistic about the issue priority. Don't set milestones.
  • (optional) Submit a pull request which fixes the issue.

Ensure you give us enough information to diagnose your issue:

  • Switch your site to "dev mode". Paste any PHP errors with their stacktraces. A generic "Server Error" message is not enough information.
  • If you suspect a JavaScript or CSS bug, check if it appears in other browsers
  • Use the Chrome dev tools or Firefox dev tools
  • Use the JavaScript console in your browser to determine if any errors happened there, and paste the complete info into issue description.
  • Use the "Network" panel to determine if any XHR ("Ajax") requests have returned errors, and paste the HTTP headers as well as HTTP response body into the issue description.

Reporting Security Issues

Report security issues to security@silverstripe.com. See our "Release Process" documentation for more info, and read our guide on how to write secure code.

Sharing your Opinion