Moderated answer and the FAQ

Question

Okay, so I had an answer on this question here. In that answer I referenced Chip's answer. The reason I mentioned his answer is because one of those plugins (Role Scoper) is a fine alternative if the OP prefers the interface. However, in my experience, the plugin I suggested is the 'right' one for the job - most frequently and recently updated, greater flexibility, better RTL language support, etc. The moderator (EAMann in this case) removed my answer and made it a comment on Chip's answer instead, ensuring that I can't get answer or upvote credit for what (in my opinion) is a better solution. I'm not normally one to question the mods, but I don't understand why an answer that is standalone "should be either an edit to or a comment on" another user's answer.

Not trying to throw a tantrum, just trying to follow the logic and requesting insight so I don't make the same mistake again.

Answer 1

It is an edge case. If you label an answer as an addition to another answer and don't add extra information converting it to comment seems legit.

What we may learn:

• Make your answers a useful standalone resource, something understandable without the need to read other answers.
• Explain why you recommend an approach, a plugin or a theme (like you did here in your question).
• Tip: Add a useful(!) screenshot. These cannot be taken to a comment, so we may hesitate even more to convert it. ;)

Answer 2

No worries.

Your answer was actually flagged specifically because it did reference Chip's answer. Remember, answers aren't displayed in chronological order when viewing the site, so it might appear either before or after Chip's answer.

It was suggested that your answer be added as an edit to Chips ... proposing an alternative plugin. But as a moderator, I can only convert answers to comments, not to edits on other people's answers.

If the answers were substantially different (i.e. detailing what the features of each plugin was and why they are the best fit to the problem) then they'd make sense as separate answers. But both answers were along the lines of "Try X plugin, it's what I use" and don't stand well enough on their own to warrant being separate.

Of course I could be wrong and I'm open to feedback.

Answer 3

There is a problem with consistency here that I don't understand.

Why was SickHippie's suggestion/answer moved to a comment yet there currently is an answer (RyanS) on that page that is older and does the exact same thing.

Answer 4

I'll "out" myself here, and say that I flagged the answer, because I thought combining the answers is the correct approach in this case. But, I didn't want to add your answer to mine, without some moderator feedback.

In this case, the reason I believe it to be the correct approach is that my answer wasn't "use X Plugin", but rather, "use a Plugin to add an additional, custom user role, to which you can give specific user capabilities." The distinction is especially important, since the underlying premise of the Question was that the user wanted to edit core files to change user roles.

The specific Plugin to be used is meta information to this answer, and I listed the two I have seen the most. Listing additional, similar Plugins is merely an extension of this meta information. Thus, another answer that says, "use a Plugin" - regardless of the Plugin being recommended - is a duplicate of the existing answer, and dilutes the ability of any one answer to become a definitive/canonical answer.

I try to keep in mind that one of the purposes of SE sites is not merely to answer users' questions, but to develop a definitive source of information about a specific topic. If the roles were reversed, I would have edited (or commented) your answer, to add to your answer my list of alternative Plugins (and in fact, have made such comments/edits several times, where I have thought that my additional information didn't warrant or constitute a separate answer).

But for future reference, I welcome edits and improvements to anything I write at WPSE. After all, all site content is CC-licensed, and the community members are encouraged to edit one another's answers, to improve them.