posted ago by Doggos

Version 1.1.8.0 (08/01/2020) fixes a significant issue that we came across today.

When you create a comment, a database entry is inserted and an incremental ID is assigned. That entry is then immediately edited based on the ID for the purposes of comment nesting.

In the event that this fails - which it didn't even once in the first almost four million comments, the comment will be interpreted as both the parent and the child of every other comment.

This means that when you load a post, the comment section will be in a loop - it will render the same comments endlessly.

Since this is rendered on the server side, it's a significant issue which impacts the network's stability. As a result, this fix has been deployed across all Win sites immediately.

Version 1.1.8.0 (08/01/2020) fixes a significant issue that we came across today. When you create a comment, a database entry is inserted and an incremental ID is assigned. That entry is then immediately edited based on the ID for the purposes of comment nesting. In the event that this fails - which it didn't even once in the first almost four million comments, the comment will be interpreted as both the parent and the child of every other comment. This means that when you load a post, the comment section will be in a loop - it will render the same comments endlessly. Since this is rendered on the server side, it's a significant issue which impacts the network's stability. As a result, this fix has been deployed across all Win sites immediately.
Comments (0)
sorted by: