1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

What is a reasonable timeframe for bug fixes on paid add-ons?

Discussion in 'Resource and Add-on Discussions' started by Mouth, Mar 4, 2013.


How long is a reasonable time to wait for the bug to be fixed?

Poll closed Mar 11, 2013.
  1. 3 days or less

    3 vote(s)
  2. 3 days to 1 week

    4 vote(s)
  3. 1 week to 2 weeks

    4 vote(s)
  4. 2 weeks to 4 weeks

    0 vote(s)
  5. 4+ weeks

    0 vote(s)
  1. Mouth

    Mouth Well-Known Member

    Firstly, this is not affecting me or a 'friend' but does affect us all, from time to time, and a discussion today (that I'm not involved in - just reading posts) prompted me to open the discussion and wonder on the general consensus.

    So, the scenario is that you've purchased an add-on that the dev (or seller) has not stated that it comes as-in or without support/fixes. You install the add-on and you immediately get a bug that causes your add-on (or worse, the forum) not to work - either at all, or main/core functionality.

    For sure the complexity of the add-on and the complex nature of the bug impacts, so for the sake of this discussion lets say it's a medium level functionality add-on, and an apparent medium level bug. Where medium complexity equals something like extending user conversations and the bug causes that functionality not to work (throwing a 'blue screen of death' style error to the user whenever they click/activate this add-on).
  2. Da Bookie Mon

    Da Bookie Mon Well-Known Member

    IMO 3 days or less low or medium level bugs.. This is something you purchased.. In the real world things are fixed fast.. virtual should be no different. What I find fustrating the most is when the bug is put on the back burner and you see the developer releasing or updating other add-ons rather then fixing the issues with said bug add-on.. Even if it is one or two people reporting said bug, it was still purchased and should be top of the list right under already reported bugs.. Not OMG look at this new add-on I made send me 40.00 more bucks for this one and maybe someday I'll get around to fixing that bug on the other app ppl can't use cause of it.
    Mouth and Morgain like this.
  3. Biker

    Biker Well-Known Member

    For a paid plugin, I'd have to agree that 1-3 days is sufficient for minor bug fixes.

    What chaps my hide even quicker is seeing the developer rush to make sure someone can purchase it, but not a single peep for bugs being reported for months in their support forum.
    Mouth likes this.
  4. Slavik

    Slavik XenForo Moderator Staff Member

    Depends on the situation, id say give them a week to get back to you with an eta on a fix.
  5. tenants

    tenants Well-Known Member

    Give them a nudge once, then leave them at least a week. Personally, I sometimes forget if I'm really busy, so appreciate the nudges

    Things that break straight away aren't good, but if it's a clash, it's not always the devs fault

    If I'm not that busy, I can make fixes on the that day... but there are some things that aren't so easy to fix, and if there aren't even steps to reproduce, don't expect them to be able to fix it fast.
    The more information you can provide the developer, often leads to a faster fix (especially if you explain it step by step and let them know you appreciate their help)

    (Enhancements... well, these can take months / if ever (pending if the dev agrees with it / has time for it))

    If it doesn't get fixed after a week, and you don't really want it if it's going to take longer, ask them politely if they might refund (I know I would)
  6. Edrondol

    Edrondol Well-Known Member

    To me it depends on the severity of the error. Does it break stuff you just plain can't have broken? In that case it needs to be fixed now...unless, of course, it's a conflict between 2 addons, then you have to figure out which one is a need and which one is a want.

    But for the most part it must be addressed within a couple days at the very least or I won't trust the author any longer. Even if it's not fixed, it needs to be addressed and acknowledged.
    Volion and Mouth like this.

Share This Page