Bug submitting guidelines

Components explained

  • interface - WEB interface issues
  • backend - backend issues, e.g. incorrect data fed to web UI
  • database - database issues, e.g. schema bug, query error
  • mobile - all mobile version issues
  • gui - experimental & unreleased GUI, forget about it for now

Other guidelines

  • An example of coherent bugreport: 72
  • The most important rule: ALWAYS specify your tt-rss version. Bug reports without version information will be CLOSED.
  • Try opening tt-rss.php with ?debug=1 in address string and report contents of debug window. Since 1.2.6 you can also toggle debug output on the fly with Shift-D.
  • Provide concise and to the point description of the failure. E.g. "tt-rss doesn't work OMG!!" is a bad report, "clicking on button XYZ shows exception error if conditions A, B and C are met" is a lot better. Don't forget to provide necessary context, e.g. you know what method you use for updating feeds - I don't.
  • It is even better to provide a link to your configuration file (e.g. copy config.php to config.php.txt and link that) just in case.
  • If you are upgrading:
    • Reopen your browser and clean any browser caches. Some javascript file could stuck in cache and cause all sort of weird "OMG what's happening" and "sanity check failed" errors.
    • Check the configuration file example (config.php-dist). There could be new options which require copying into your config.php (this particular rule solves a lot of dreaded "D001" errors).