Replies in moved posts get wrong link
-
Continuing the discussion from More @translator shenanigans:
Translator replied to me, not @accalia!
Specifically, it links to this post:
http://what.thedailywtf.com/t/more-translator-shenanigans/7912/3?u=raceprouk
-
After 10 translations Bing says: continue to debate some of the @translator type (repeat http://what.thedailywtf.com/t/more-translator-shenanigans/7912/72 ) :long time sound translation and does not respond to @accalia.
Filed under: English -> Portuguese -> Slovenian -> Dutch -> Thai -> Estonian -> Vietnamese -> Chinese Simplified -> Norwegian -> Japanese -> Hungarian -> English
-
I can probably guess why too: my post is post 71 in that thread, but @accalia's was probably #71 in the original thread.
-
I'm going to assume it starts from 1 with post_number rather than taking the posts moved over into account.
Yours is the 3rd post since topic creation, @accalia's the 3rd post originally.
-
Actually, that makes more sense.
And yet it is also 468557474867368589x more retarded.
-
isnt that an @translator bug, not a dicsourse bug?
-
After 10 translations Bing says: It's not @translator error in dicsourse?
Filed under: English -> Dutch -> Greek -> Vietnamese -> Korean -> Romanian -> Portuguese -> Swedish -> Slovak -> Russian -> Czech -> English
-
or was @translator's post already there and then got moved, which jacked up the "replied-to" link?
-
After 10 translations Bing says: @translator already exists for the connection.
Filed under: English -> Latvian -> Lithuanian -> Chinese Simplified -> Thai -> Bulgarian -> Vietnamese -> Finnish -> Portuguese -> Turkish -> Dutch -> English
-
Discourse bug; my post was made after the move
My understanding of @sockbot code is it uses the post ID to reply to (@accalia to confirm)
-
Yes mistress Knight of Ancient Study of Furries and Anthros, I shall appear as summoned.
-
if your post was after the move, it could be a bug grab-bag. there might be lingering original topic/post# references in the json that @accalia processes which caused her replybot to reference the wrong topic or the wrong post#, or @dicsourse itself is just flat broken. or both.
-
-
-
My understanding of @sockbot code is it uses the post ID to reply to (@accalia to confirm)
yes, but how that's stored in discourse is anyone's guess.
-
@accalia processes which caused her replybot to reference the wrong topic or the wrong post#
given that the @translator's reply was also moved... not likely @sockbot's fault
-
Yes mistress Commander @Accalia Shepard, I shall appear as summoned.
-
After 10 translations Bing says: in @translator..., probably not @sockbot error
Filed under: English -> Vietnamese -> Ukranian -> Chinese Simplified -> Swedish -> Polish -> Finnish -> Lithuanian -> Bulgarian -> Japanese -> Romanian -> English
-
posts.reply_to_post_number
post_replies.post_id
post_replies.reply_idIt's very possible that the reply_to_post_number doesn't get edited.
-
This post, however, was post-move.
http://what.thedailywtf.com/t/more-translator-shenanigans/7912/72?u=loopback0
I'm still thinking Discosocks is at fault, but whatever it was fixed itself anyway.
-
-
Erm, actually, I meant it stopped happening.
Other posts have the reply-to set correctly.