issues.rst 1.5 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253
  1. Reporting Issues
  2. ================
  3. Report bugs and features requests to https://github.com/Elgg/Elgg/issues.
  4. See below for guidelines.
  5. DISCLAIMERS
  6. -----------
  7. - **SECURITY ISSUES SHOULD BE REPORTED TO security @ elgg . org!**
  8. Please do not post any security issues on github!!
  9. - Support requests belong on the `community site`_.
  10. Tickets with support requests will be closed.
  11. - We cannot make any guarantees as to when your ticket will be resolved.
  12. Bug reports
  13. -----------
  14. Before submitting a bug report:
  15. - Search for an existing ticket on the issue you’re having. Add any
  16. extra info there.
  17. - Verify the problem is reproducible
  18. - On the latest version of Elgg
  19. - With all third-party plugins disabled
  20. Good bug report checklist:
  21. - Expected behavior and actual behavior
  22. - Clear steps to reproduce the problem
  23. - The version of Elgg you’re running
  24. - Browsers affected by this problem
  25. Feature requests
  26. ----------------
  27. Before submitting a feature request:
  28. - Check the `community site`_ for a plugin that has the features you
  29. need.
  30. - Consider if you can :doc:`develop a plugin </tutorials/index>` that does what you need.
  31. - Search through the closed tickets to see if someone else suggested
  32. the same feature, but got turned down. You’ll need to be able to
  33. explain why your suggestion should be considered this time.
  34. Good feature request checklist:
  35. - Detailed explanation of the feature
  36. - Real-life use-cases
  37. - Proposed API
  38. .. _community site: http://community.elgg.org