I just noticed a question that was about specific issues that one user was having with their code. The question pasted lots of their own code to which one user tried to help them and then the user answered their own question with "Oops, it was a coding error on my part."
While it might be hard at times to draw a line between questions that are broadly useful and this type of post I'd like to discuss if anyone else things the question I links it appropriate or not, and how we can keep this from becoming filled with a site with one-off individual support issues.
So here's a great example of someone who is mostly asking tons of support questions. It's clear he is struggling with WordPress and probably has a corrupted install, or does things to corrupt installs. I think the consensus (of 3 people here) was that this really shouldn't be a support site but not sure how to really handle it. Should we close all his questions? When do we start closing and where do we stop?
Why is this important? If we don't police then the site becomes a graveyard of unanswered support questions. I know I'm losing interest in helping someone who has so many problems, whose problems are likely not applicable to the broader user community, and worst of all answering questions that become a time-consuming back-and-forth diagnosis of the problem with someone of unknown competence to resolve the issue, and I'll bet others who answer a lot of questions will soon feel the same way. Having those questions unanswered makes the site look like we don't answer questions. If we were to be a specific support forum then those questions would be acceptable but we're about solutions that can apply to more than one person, right?
Help me know how (as a pro tem moderator) know how to handle this.