7

It sounds like from Brandon's comment here that bug reports should be submitted directly to Craft Support.

...please contact us directly when you run into bugs such as PHP/MySQL errors. Preferably through the Get Help widget on your Dashboard (which can include a DB backup), or you can email support@buildwithcraft.com.

With that in mind, should bug report-type questions (PHP or MySQL errors), be allowed at all? Or simply closed as off-topic?

| |
8

Yes. Bugs are better served and corrected by Pixel & Tonic. While many of us more PHP-experienced users can probably fix it, it would be a waste of our energies since we can't distribute the fix to others like Pixel & Tonic can. Not to mention you can send a DB backup to them for better diagnosis, and they are wicked smart and quick to fix issues.

| |
  • My biggest concern with the no bug reports rule is that in many cases a beginner user may not know whether their issue is just user error or actually a bug report. There are many times when I, as a fairly advanced developer, spend time hunting around before realizing I've hit a bug. I really wish there was a way we could keep questions that indicate that symptoms of a bug, so that users can easily see that there is a documented fix. – Jeremy Gimbel Jun 12 '14 at 22:00
  • @Jeremy Maybe a "Common Bugfix"-Guide would be a solution to this? – Victor In Jun 12 '14 at 22:59
  • 1
    Sure, sometimes it’s not clear. If you’re getting a PHP/MySQL error though, it should be pretty clear that’s not intended behavior. – Brandon Kelly Jun 12 '14 at 23:14
  • 2
    I think Brandon's quote (or something similar) from the question should be placed in the sidebar to avoid confusion in the future. – Victor In Jun 13 '14 at 0:10
  • 3
    I think we also have to remember not to be assholes, particularly when new folks aren't sure how/what to post. Kind people have helped me learn from my embarrassing questions, so I edit with vigor and pay it forward. – Matt Stein Jun 13 '14 at 0:22
  • 2
    Isn't this part of being a community though? If it's considered off-topic, we can simply explain in the reason for being off-topic. Better yet, we can even give possible next steps. For bugs, we simply say, "This sounds like a bug! You should use the support form in the CP." – Bryan Redeagle Jun 13 '14 at 1:01
  • 3
    I'm not sure if there's any disagreement, I just mean that it's better to close gently rather than slam. Because it's being part of a community. "Closed as off-topic" can seem pretty harsh to a new member if a bunch of people voted on it and nobody mentioned why. Google+ isn't nearly the same platform, but it doesn't have the same hard edges either. Apologies if I'm being unclear; that's kind of what I do here. – Matt Stein Jun 13 '14 at 1:23

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .