Hi and thanks already for a great module that might be exactly what I am looking for.

However, I have a small suggestion that could greatly increase its scope:

Would it be possible to allow the author of an article to "reset" the comment count?

Hard to explain but I will try:

For example if you want to give people the opportunity to offer small jobs to whoever responds to it. The one to reply first will be able to make a suggestion on how this job can be accomplished and due to the limit of comments "block" others from making an offer themselves. If the author of the article is not entirely satisfied with what the first comment offers, he can "reopen" the the article for another comment (or several more). In combination with views you could then make a list with jobs/questions/requests that are still open for someone else to answer.

Thinking this further, another suggestion would be the following:
- Already pressing the "comment" or "reply" button will block others from doing the same and thus block them from posting a comment (first come, first serve).
- The one who has locked the topic this way will be given x amount of time to actually write down his comment/answer/solution and post it.
- If he doesn't manage to do so within the given time frame, the topic/article is automatically free again for everybody else to comment on.

I know this would certainly mean a lot of work so it is merely a humble suggestion in case you also think that with these features the possibilities of this module would be highly increases.

Comments

tahiticlic’s picture

Well, I haven't got many time now to do this, and since this needs to move the control on the node rather than to the node type, there's some work to do indeed.
I'll keep this in mind, in fact I'm developing a services bid platform, that could be a part of the development that I didn't think about before.

avpaderno’s picture

Status: Active » Closed (outdated)

I am closing this feature request, as it's for a not supported project version. If you want to see this feature implemented for a supported project version, please re-open this issue.