READ ME FIRST – How to report issues

  • Plugin Author Hector Cabrera

    (@hcabrera)


    9 years, 4 months ago

    I’m starting this topic with a quote from an unknown author:

    “It doesn’t work.“

    Give the programmer some credit for basic intelligence: if the program really didn’t work at all, they would probably have noticed. Since they haven’t noticed, it must be working for them. Therefore, either you are doing something differently from them, or your environment is different from theirs. They need information; providing this information is the purpose of a bug report. More information is almost always better than less.

    When facing problems with this plugin (or any software out there, actually), a big part of the solution comes from user feedback. It’s vital for the developer to know under which circumstances the software fails/misbehaves in order to find out what when wrong and when. So, the more details you add to your bug report the better for us developers.

    Use a descriptive title
    Make sure the title of your bug report explains shortly what’s going on. That helps not only me but also other users who might be experiencing the same problem.

    Details matter!
    When does the problem happen? What does it affect? What options are you using with the plugin? Which version are you using? What’s your current WordPress version? Which other plugins are you using on your site? What theme are you using now? Did you make any changes recently on your site (plugins / theme updates, WordPress update)?

    The answer to these questions usually can lead to hints which ultimately can help fix the problem. Reports like “I have a problem, fix it!” aren’t really helpful. The more you can tell me about it, the better for everyone.

    https://www.ads-software.com/plugins/recently/

  • The topic ‘READ ME FIRST – How to report issues’ is closed to new replies.