created question should set tracker topic reply to 1
preferred name - February 26, 2007 - 21:58
| Project: | Question |
| Version: | 5.x-1.x-dev |
| Component: | Miscellaneous |
| Category: | feature request |
| Priority: | normal |
| Assigned: | codepoet |
| Status: | by design |
Jump to:
Description
when the admin promotes the question, then creates the topic with the answer to that question, at that tracker (resent posts), that topic reply should be set to 1 not 0, so that the original author knows that a reply was given.
ps.. the question module is excellent!
#1
I'm not sure I follow you. What is this "topic reply" that's not set properly?
#2
consider that the author's username is now correct. The user logs in and goes to 'resent posts'. The user sees that the question is now online (the resent posts page shows a title made by the admin and the user as the author), but because there is no reply to that post, the user thinks that the answer was not yet given.
consider that the author is the admin. The user logs in and tries to find the answer to the question. The user clicks the 'resent posts" and sees that there is a big list of titles all by the admin. The user basically has to pick through each of the topics or do a search to find the answer to the question. Yet the user might not do this if at 'resent posts' the topic has no reply. if you go to my account then track, you can see the replies to your post. You would not go to a topic that did not have a reply. This is why I believe that the reply should be set to 1.
#3
I'm afraid my confusion is coming from a language disconnect. I think you mean recent (occurring at a time close to now) and not resent (to send again). So you mean the page at /tracker that lists recently-updated content on the site should show the answered question and the answer should bump the reply count to one.
No, that's not how it works. The question queue does not create nodes in the traditional sense; it only collects questions that could later be turned into nodes. Since the principal authorship of the content comes from the person answering the node is owned by the answerer.
However, what I could do is add a feature to the module to email a form letter to the user stating that the question had been answered once the created question node is published and include the URL. This would avoid a fundamental change to the module as well as notify users that desire to know when their questions have been answered.
Does that work for you?
#4
I am sorry, in my above posts, it is "recent posts", the link to the top right, and not "resent posts".
consider that the author's username is now correct. The user logs in and goes to 'recent posts'. The user sees that the question is now online (the recent posts page shows a title made by the admin and the user as the author), but because there is no reply to that post, the user thinks that the answer was not yet given.
the email will not work for a lot of admins because the smtp is disabled. There could be an option to set the default post count to 1.
at the below link is another reason why I believe that we need this post count option.
http://drupal.org/node/122949
#5
I understand what you're asking, there's no need to keep repeating the reasons I simply disagree.
When a user asks a question, it does not show up in recent posts because it's not yet a node; the user has created nothing as far as the site is concerned. When it appears in recent posts, that's when there's an answer.
Either way, there's no way to increment the reply counter at any rate because there are no replies to the item, be it in the queue or answered. It's not a number stored by the system, it's a count of actual comments on a node.
If this is the behavior you want, then don't link to the question queue. Let users create new question nodes, have them default to unpublished, and then do through and answer them and publish them. They'll still appear with no comments (because there are none) but they will be authored by the user that posed the question, since that appears to be your main concern.