A lot is possible in Drupal. It just sometimes requires a lot of coding. It's usually better not to ask if something's possible -- just state your problem and the maintainer will tell you if there is a solution.

Don't open an issue just to say "I haven't solved my own problem yet." The maintainer probably can't help you, and it's just annoying while your issue sits untouched in the queue and no one can do anything about it.

Each support request is an individual person's problem. You should open a new request if you really need support. However, first make sure your question hasn't already been answered and you can't figure it out yourself. When you open the new issue, make sure you list the steps you've already taken to solve the problem yourself, including listing similar issues that you found in your search for a solution.

Say the goal, not how you want to achieve it. Usually the best way to reach the goal is not the way you expect.

Don't assume you know what the cause of your problem is, or how to fix it -- because you probably don't. If you did, you would have fixed it already. Just report what you're trying to do, what's actually happening, how to reproduce it, and the relevant technical details.

...so don't complain if you don't get either one, and be happy if you do.

The problem you're reporting may have already been fixed.

Using more than one question mark or exclamation point in a row is obnoxious.

If it was that horribly broken, there wouldn't be thousands of sites using it. Of course, we understand that a person as awesome as you are couldn't possibly make a user error, so it must be the leprechauns.

Syndicate content