friendica/doc/Bugs-and-Issues.md

Bugs and Issues
===============

* [Home](help)

If your server has a support page, you should report any bugs/issues you encounter there first.
Reporting to your support page before reporting to the developers makes their job easier, as they don't have to deal with bug reports that might not have anything to do with them.
Reducing the workload in this way helps us get new features faster.
You can also contact the [friendica support forum](https://helpers.pyxis.uberspace.de/profile/helpers) and report your problem there.
Bugs are rarely limited to one person, and the chances are somebody from another node has encountered the problem too, and will be able to help you.

If you're a technical user, or your site doesn't have a support page, you'll need to use the [Bug Tracker](https://github.com/friendica/friendica/issues).
This is also used for issues with addons.
Please perform a search to see if there's already an open bug that matches yours before submitting anything.

Try to provide as much information as you can about the bug, including the **full** text of any error messages or notices, and any steps required to replicate the problem in as much detail as possible.
It's generally better to provide too much information than not enough.

See [this article](http://www.chiark.greenend.org.uk/~sgtatham/bugs.html) to learn more about submitting **good** bug reports.  The better your bug report, the more likely we are to be able to actually fix it.

And last but not least: It is better to report an issue you encountered even if you can't write the perfect bug report!
local documentation library 2011-04-13 10:07:21 -04:00			`Bugs and Issues`
			`===============`

			`* [Home](help)`

minor formatting stuff mainly 2015-04-17 12:23:00 -04:00			`If your server has a support page, you should report any bugs/issues you encounter there first.`
			`Reporting to your support page before reporting to the developers makes their job easier, as they don't have to deal with bug reports that might not have anything to do with them.`
Update doco 2017-05-19 16:37:45 -04:00			`Reducing the workload in this way helps us get new features faster.`
clarification to the docs 2016-02-05 00:47:17 -05:00			`You can also contact the [friendica support forum](https://helpers.pyxis.uberspace.de/profile/helpers) and report your problem there.`
Update doco 2017-05-19 16:37:45 -04:00			`Bugs are rarely limited to one person, and the chances are somebody from another node has encountered the problem too, and will be able to help you.`
local documentation library 2011-04-13 10:07:21 -04:00
in docs there was a wrong link to the issue tracker 2016-12-09 05:38:08 -05:00			`If you're a technical user, or your site doesn't have a support page, you'll need to use the [Bug Tracker](https://github.com/friendica/friendica/issues).`
use typo.php to check before PR 2017-09-21 03:38:03 -04:00			`This is also used for issues with addons.`
minor formatting stuff mainly 2015-04-17 12:23:00 -04:00			`Please perform a search to see if there's already an open bug that matches yours before submitting anything.`
local documentation library 2011-04-13 10:07:21 -04:00
minor formatting stuff mainly 2015-04-17 12:23:00 -04:00			`Try to provide as much information as you can about the bug, including the full text of any error messages or notices, and any steps required to replicate the problem in as much detail as possible.`
			`It's generally better to provide too much information than not enough.`
local documentation library 2011-04-13 10:07:21 -04:00
Update doco 2017-05-19 16:37:45 -04:00			`See [this article](http://www.chiark.greenend.org.uk/~sgtatham/bugs.html) to learn more about submitting good bug reports. The better your bug report, the more likely we are to be able to actually fix it.`
local documentation library 2011-04-13 10:07:21 -04:00
use typo.php to check before PR 2017-09-21 03:38:03 -04:00			`And last but not least: It is better to report an issue you encountered even if you can't write the perfect bug report!`