7

Borrowing from the new Stack Overflow reasons, I really like this one: Questions must demonstrate a minimal understanding of the problem being solved. Tell us what you've tried to do, why it didn't work, and how it should work. That would stop the zero-effort "I want this, how do I do?" questions from proliferating. Plus we already know it's a valid ...


6

I think the text for Issues found in existing modules/themes should be clarified to something like Issues and bugs in contributed modules and themes (bugs should be reported to the relevant issue queue on Drupal.org) This is a fairly common reason and I think slightly longer, unambiguous help text would be useful here.


5

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 ...


4

So long as shows zero research effort is the main point, I have no issue at all with code requests being closed.


4

Nope! Lack of research = close the hell out of it :-)


4

It will vary by question, but "no" answers are perfectly acceptable. Explain why it can't be done. Suggest alternate solutions. If possible, outline how a patch could be done.


3

I would like to see the following closing reason, borrowed from Stack Overflow, added to off-topic: Questions concerning problems with code you've written must describe the specific problem and include valid code to reproduce it. See SSCCE.org for guidance. This would stop those questions talking in abstract of code and asking why it doesn't work. To ...


3

Now the problematic one. It has been misapplied a lot. Probably for questions that didn't show minimal effort and should better be flagged as "needs details or clarity" or "needs more focus". Nevertheless questions merely asking to find a module are quite a problem. So I'd throw this one in the ring again. I'm adding the small word explicitly, explicitly ...


3

I already asked for the bug report close reason in 2018 and really want it to be in the list. But, I think the recommendation close reason is a little bit more important. But you do the voting so here comes a bug report close reason. This is a bug report or support request to a third-party project hosted on drupal.org or elsewhere and must be reported in ...


3

It’s simply that they get reset each year. From Community Promotion Ads — 2019 Why do we reset the ads every year? Some services will maintain usefulness over the years, while other things will wane to allow for new faces to show up. Resetting the ads every year helps accommodate this, and allows old ads that have served their purpose to be cycled out for ...


3

The question in question is asking "Why does this happen?" It doesn't ask what to do; the user could be trying to understand why it happens in a development site, and not in production, for example. I know the question could be seen as a PHP one, but users on Stack Overflow who don't use Drupal would not probably be able to answer it without seeing the code ...


3

Maybe the part of the Help Center that describes which questions should not be asked needs to be changed. What we are really trying to avoid are those questions where the OP simply reports a warning or an error message shown by a module implemented by others, and asks what to do. What is wrong with those questions is that: The OP doesn't show to understand ...


3

The question the user is asking is: How can I give the right database credentials to Drush? Can I define something in drushrc files per project? I take it as asking "If Drush is using the php.ini file I am not expecting, is there any other way to tell Drush what the database credentials are?" I think it is a question about Drupal. I assume the user doesn'...


2

Closed due to simply being simple? No. Sometime it might be hard to find an answer for a simple question. See Views and their lack of / buggy documentation (and even untrue comments in code sometimes). Closed for the sake of lack of minimal understanding and own research? Hell yes.


2

Generally speaking, questions about tools used exclusively for Drupal should be on-topic for Drupal Answers; for example, Drush is surely not a module, but questions about Drush are on-topic. If I cannot expect people using Drupal to answer questions about Drush, I don't know where else I should ask questions about Drush; for sure, I cannot ask to people ...


2

OK so we seem to have a reasonably strong consensus (as strong as our meta crowd will normally get anyway ;), but I have to confess I'm softening a bit on the idea. I don't think we necessarily need a blanket ban on code-request questions. Anything egregiously offensive by way of such a request would almost always fall into the "not enough research effort" ...


2

Instead of the closing reason that it already enabled, I would use a different closing reason that has a reference to more than one Stack Exchange site. Questions on programming, PHP, SQL, etc. that do not relate directly to Drupal are off-topic here, but can be asked on Stack Overflow. For example, if we get questions that should be asked on Server ...


2

I would LOVE to see a close reason of "This is in the documentation" or "Handbook page available" or something like to those ends. I guess it would be a polite way of saying RTFM (polite because d.o can be a nightmare to navigate sometimes). Not sure how we would handle the case of someone casting this a close vote though - only way I can think of is ...


2

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 ...


2

All SE sites are allowed three custom close reasons. Our current ones are Questions on programming, PHP, SQL, etc. that do not relate directly to Drupal are off-topic here, but can be asked on Stack Overflow. This question was caused by a problem that can no longer be reproduced, was solved by a cache clear, or was a simple typographical error. While ...


1

Let's keep the second one as-is. This happens quite often and it's also a good close reason for outdated questions. This question was caused by a problem that can no longer be reproduced, was solved by a cache clear, or was a simple typographical error. While similar questions may be on-topic here, this one was resolved in a manner unlikely to help future ...


1

You get your privilege to flag way earlier than you get privilege to vote close. This means there need to be entry in flag list for it - so folks can flag even without access to vote menu. If you will try to cast duplicate flag when you already have a vote to close privilege, flag will be automatically converted to vote. Probably it won't even get listed in ...


Only top voted, non community-wiki answers of a minimum length are eligible