Connected topic: Questions that lack any research effort

We have three kinds of module requests here:

  1. Give me module that will ............... (example)
  2. I tried using ........ but it can't ....... or is unavailable in ......., what can substitute it? (example)
  3. How can I ........... ? and answer simply happens to be a module (example)

Now - which of these should be considered OK, and which off-topic due to lack of minimal research effort? I'd say 1. should usually be closed, 3. should usually be OK, and 2 is in the gray area (can fall into "shopping list" type), but I'd like your input.


Questions about which module to use are indeed on-topic, but as other questions, they require a little of effort from the users. I think that this answer to What information should be given when asking a question? shows what details the users are supposed to give.

If the question is about which module to use to implement a feature in a site, describe in detail the feature you want to implement, the result you want to obtain, and which modules you have already tried.
Before asking a question about which module to use, you should first search for a module to use on Drupal.org or Drupal Modules. (Use "the Module Finder" block visible on top of Drupal Modules.) If that doesn't give any good result, try googling using the "site:drupal.org" option; this should give more aimed results, if you first didn't find the more appropriate module in the first 6 search pages.

This would avoid that the users who answer suggest a module that has been already tried, but it has not been chosen for any reason.

If the question doesn't shown any research on Drupal.org or Drupal Modules, the question is probably going to be closed. Searching at least on Drupal.org is the first expected step, in such questions.

Describing the exact task you are trying to achieve allows you to get a more correct answer, especially in the case there is a more generic module that can be used, but also a more specific module has been already written.

What I find much suspicious are those questions asking for a module to use, where the answers are all similar to "You could try the [link to the module] module: [excerpt taken from the project page]." Since the user who asked the question doesn't ask further questions about the module (even in a comment for the given answer), I feel like one of the following cases applies:

  • The user who asked the question didn't search on Drupal.org, or didn't notice the module
  • The user who asked the question is merely deciding which answer to accept basing on the votes it gets

In the first case, the user didn't probably search too deep on Drupal.org; this is what I feel when I am able to find a module that suits the user's needs. (I am not that good in finding modules; if I find it, and my answer is accepted, probably the user could have found it too.)
In the second case, the user is just using the question as pool. If the question is also too generic, or subjective, then the question should be avoided.

Let's remember that the help center, under What topics can I ask about here? describes Drupal Answers as "a Stack Exchange site for project managers, themers, developers, site-builders, administrators, and businesses using or thinking about using the Drupal CMS." We should be less aggressive toward the new users, since they could simply be people who are thinking about using Drupal. This doesn't mean we should accept every question, but that we should explain why the question is not acceptable, if it is going to be voted to be closed.

  • Looks like these days the rules have changed regarding the first kind of questions (cfr bullet "1." in the question). At least that's what I seem to understand from your review of this question. Do you mind explaining your "leave open" vote? – Pierre.Vriens Jan 20 '17 at 21:31

I'm starting to feel more and more like the first type that you've outlined should fall under the "Shopping List" category of questions.

They're essentially just asking for links, another specific reason we use to close questions anyway. And I find it difficult to see how a module to solve an OP's specific use-case today is going to be useful to visitors in the future.

The second example you've given seems perfectly ok to me, as long as it's not encroaching into bug report/feature request territory.

The third is fine too IMO, as long as the OP has made an obvious attempt to solve the problem themselves.

As a side note, we (mods) are getting a little less involved in unilaterally closing questions, and deferring to the opinion of the community where possible.

So, we need your close votes!!

  • Actually the specific question that led you to bring this up has been edited into shape by the OP - so there's a lot to be said for being patient and explaining the objections clearly; the vast majority of people are willing to put the effort in if they're nudged in the right direction – Clive Sep 3 '13 at 9:02
  • Updated this question so now link points to a specific version. And I like the updated one all right. I prefer edits over closing, I'm just not good at explaining. – Mołot Sep 3 '13 at 10:05
  • 1
    This sums up how I feel, but I am fine with the first type as long as the question demonstrates some attempt to find one first. – mpdonadio Sep 3 '13 at 10:56

You must log in to answer this question.

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