If the workaround using 5224 can't be fixed, it needs to be disabled. It has really messed up at least three threads now
 | Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years. Thanks, CNET Support |
General discussion
Another thread messed up in SE ...
If the workaround using 5224 can't be fixed, it needs to be disabled. It has really messed up at least three threads now
Discussion is locked
5 Posts
- Collapse
- Collapse -
I seem to get message 71 of 71 messages here:
http://reviews.cnet.com/5208-6130-0.html?forumID=50&threadID=103986&messageID=1197055
What I'm still waiting on is 115 of 115 messages in this thread:
http://reviews.cnet.com/5208-6130-0.html?forumID=50&threadID=102960&messageID=1185397
It was apparently padlocked by a Moderator, but still was promised to be fixed and had this at the last post:
"< An unexpected failure has occured. It has been logged and will be addressed by support."
- Collapse -
Then the issue will go away. Can you please relay this message to the SE folks, Glenda? Thanks!
- Collapse -
Any one that read the thread now understands the problem, I hope!
CNET Forums
Operating Systems
Software
Electronics & Gadgets
Hardware
Tablets & Mobile Devices
General Help
Roadshow Autos
Chowhound
Comic Vine
GameFAQs
GameSpot
Giant Bomb
TechRepublic