From 786d0516da9741e9777cbde771bc582997958a36 Mon Sep 17 00:00:00 2001 From: Ingo Schommer Date: Tue, 22 Jan 2013 15:10:50 +0100 Subject: [PATCH] More docs on CMS issue reporting --- docs/en/misc/contributing/issues.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/en/misc/contributing/issues.md b/docs/en/misc/contributing/issues.md index a143cc763..033096068 100644 --- a/docs/en/misc/contributing/issues.md +++ b/docs/en/misc/contributing/issues.md @@ -27,6 +27,14 @@ If the issue does look like a new bug: * Add keywords to help us organize issues, and please be realistic about the issue priority. Don't set milestones. * *(optional)* [Submit a pull request](/misc/contributing/code) which fixes the issue. +Ensure you give us enough information to diagnose your issue: + + * Switch your site to "[dev mode](http://doc.silverstripe.org/framework/en/topics/debugging)". 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](https://developers.google.com/chrome-developer-tools/docs/overview) or [Firefox dev tools](https://developer.mozilla.org/en-US/docs/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](mailto:security@silverstripe.com). See our "[Release Process](release-process)" documentation for more info, and read our guide on [how to write secure code](/topics/security).