Comments on specific article revisions = wrong!
-
Chris, thanks for your earlier explanation of why comments are associated with specific revisions of an article: http://www.codeproject.com/Messages/4184889/Are-comments-specific-to-an-article-revision.aspx[^] However, whilst the intention is that comments relating to article quality, whilst it is in the review process, do not make it through to the final - published article. It looks like this doesn't really work in practice! I spotted a typo on my recently published article, which is now awaiting moderation, and as a result have a number of 'my vote of 5' style comments here: http://www.codeproject.com/script/Articles/ArticleVersion.aspx?aid=342715&av=506455#_comments[^] and here: http://www.codeproject.com/script/Articles/ArticleVersion.aspx?aid=342715&av=505884#_comments[^] and of course, here, in the right place: Plotting Circular Relationship Graphs with Silverlight I have never spotted this problem before, so I am guessing this is a new feature? Also, I am pretty sure that in the past minor modifications that I made to an article did not require moderation. Can I suggest that it is made much more obvious that comments on an article which is awaiting moderation are specifically for the purpose of flagging quality issues? This might be quite hard to do with the way that it is currently set up because it is presented in exactly the same way as the regular article commenting mechanism, so I suspect regulars would just go into 'auto-pilot'. (Any chance the messages on my article revisions could be moved to the main article? - id this is a big deal, don;t worry about it) Regards, Colin E.
-
Chris, thanks for your earlier explanation of why comments are associated with specific revisions of an article: http://www.codeproject.com/Messages/4184889/Are-comments-specific-to-an-article-revision.aspx[^] However, whilst the intention is that comments relating to article quality, whilst it is in the review process, do not make it through to the final - published article. It looks like this doesn't really work in practice! I spotted a typo on my recently published article, which is now awaiting moderation, and as a result have a number of 'my vote of 5' style comments here: http://www.codeproject.com/script/Articles/ArticleVersion.aspx?aid=342715&av=506455#_comments[^] and here: http://www.codeproject.com/script/Articles/ArticleVersion.aspx?aid=342715&av=505884#_comments[^] and of course, here, in the right place: Plotting Circular Relationship Graphs with Silverlight I have never spotted this problem before, so I am guessing this is a new feature? Also, I am pretty sure that in the past minor modifications that I made to an article did not require moderation. Can I suggest that it is made much more obvious that comments on an article which is awaiting moderation are specifically for the purpose of flagging quality issues? This might be quite hard to do with the way that it is currently set up because it is presented in exactly the same way as the regular article commenting mechanism, so I suspect regulars would just go into 'auto-pilot'. (Any chance the messages on my article revisions could be moved to the main article? - id this is a big deal, don;t worry about it) Regards, Colin E.
To my mind, this is a fairly major SNAFU. When I review an article, I like to see all the comments - somebody may have posted a particularly useful snippet against an earlier revision which I would miss if I were looking at a later version. This cannot be right. While it may be useful to indicate that a message applied to an earlier revision of the article, it should not disappear.
*pre-emptive celebratory nipple tassle jiggle* - Sean Ewington
"Mind bleach! Send me mind bleach!" - Nagy Vilmos
My blog | My articles | MoXAML PowerToys | Mole 2010 - debugging made easier - my favourite utility
-
To my mind, this is a fairly major SNAFU. When I review an article, I like to see all the comments - somebody may have posted a particularly useful snippet against an earlier revision which I would miss if I were looking at a later version. This cannot be right. While it may be useful to indicate that a message applied to an earlier revision of the article, it should not disappear.
*pre-emptive celebratory nipple tassle jiggle* - Sean Ewington
"Mind bleach! Send me mind bleach!" - Nagy Vilmos
My blog | My articles | MoXAML PowerToys | Mole 2010 - debugging made easier - my favourite utility
Thanks Pete, I am glad you concur.
Pete O'Hanlon wrote:
While it may be useful to indicate that a message applied to an earlier revision of the article, it should not disappear.
It's worse than that! Messages on future revisions (i.e. new revisions awaiting moderation) do not appear either. I do wonder what will happen when the pending future revision is accepted. Where will those comments go?!! Anyhow, at least it is not just me being over-eager to get a high comment count on my article for the sake of inflating my ego. of course not. I'm very modest I am.
-
Thanks Pete, I am glad you concur.
Pete O'Hanlon wrote:
While it may be useful to indicate that a message applied to an earlier revision of the article, it should not disappear.
It's worse than that! Messages on future revisions (i.e. new revisions awaiting moderation) do not appear either. I do wonder what will happen when the pending future revision is accepted. Where will those comments go?!! Anyhow, at least it is not just me being over-eager to get a high comment count on my article for the sake of inflating my ego. of course not. I'm very modest I am.
Colin Eberhardt wrote:
It's worse than that! Messages on future revisions (i.e. new revisions awaiting moderation) do not appear either. I do wonder what will happen when the pending future revision is accepted. Where will those comments go?!!
I think I just found out, it looks like the comments do not make it into the published version when the new revision is approved. However, you can see them if you access the article by version number - even though this version is the current: http://www.codeproject.com/script/Articles/ArticleVersion.aspx?aid=342715&av=506455#_comments[^] Anywho - enough said. I'll leave this to the CodeProject peeps.
-
Chris, thanks for your earlier explanation of why comments are associated with specific revisions of an article: http://www.codeproject.com/Messages/4184889/Are-comments-specific-to-an-article-revision.aspx[^] However, whilst the intention is that comments relating to article quality, whilst it is in the review process, do not make it through to the final - published article. It looks like this doesn't really work in practice! I spotted a typo on my recently published article, which is now awaiting moderation, and as a result have a number of 'my vote of 5' style comments here: http://www.codeproject.com/script/Articles/ArticleVersion.aspx?aid=342715&av=506455#_comments[^] and here: http://www.codeproject.com/script/Articles/ArticleVersion.aspx?aid=342715&av=505884#_comments[^] and of course, here, in the right place: Plotting Circular Relationship Graphs with Silverlight I have never spotted this problem before, so I am guessing this is a new feature? Also, I am pretty sure that in the past minor modifications that I made to an article did not require moderation. Can I suggest that it is made much more obvious that comments on an article which is awaiting moderation are specifically for the purpose of flagging quality issues? This might be quite hard to do with the way that it is currently set up because it is presented in exactly the same way as the regular article commenting mechanism, so I suspect regulars would just go into 'auto-pilot'. (Any chance the messages on my article revisions could be moved to the main article? - id this is a big deal, don;t worry about it) Regards, Colin E.
Take a look at http://www.codeproject.com/script/Articles/ArticleVersion.aspx?aid=342715&av=505884#_comments[^] and let me know if this makes more sense. I can move the comments tomorrow if you wish (neeeeed sleeeeeep)
cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
-
Take a look at http://www.codeproject.com/script/Articles/ArticleVersion.aspx?aid=342715&av=505884#_comments[^] and let me know if this makes more sense. I can move the comments tomorrow if you wish (neeeeed sleeeeeep)
cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
Go. Get sleep. Speak after the weekend.
*pre-emptive celebratory nipple tassle jiggle* - Sean Ewington
"Mind bleach! Send me mind bleach!" - Nagy Vilmos
My blog | My articles | MoXAML PowerToys | Mole 2010 - debugging made easier - my favourite utility
-
Take a look at http://www.codeproject.com/script/Articles/ArticleVersion.aspx?aid=342715&av=505884#_comments[^] and let me know if this makes more sense. I can move the comments tomorrow if you wish (neeeeed sleeeeeep)
cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
Thanks Chris - that's an improvement. We'll see whether that fixes it. I have another article I am about to write up, so I'll so if this problem crops up again. Nice work :-) Would be good if you could move those comments, but only if it is not too much hassle, I am sure you have a lot of other things to do. And like Pete says - get some sleep!
-
Thanks Chris - that's an improvement. We'll see whether that fixes it. I have another article I am about to write up, so I'll so if this problem crops up again. Nice work :-) Would be good if you could move those comments, but only if it is not too much hassle, I am sure you have a lot of other things to do. And like Pete says - get some sleep!
All done.
cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
-
All done.
cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP