BigSnicker
commented
10 months ago Email from the user:
I've found I can reply to existing comments like this... http://wedecide.green.ca/processes/create-proposals/f/457/proposals/4213?commentId=2027#comment_2027
...because by specifying an existing comment, all the 118 comments are not rendered, just the comment I can reply to. (Until I get to 4th level of nested replies, as GPC only allows 4 levels of nested replies.)
But, as you know, if I try look at all 188 comments... https://wedecide.green.ca/processes/create-proposals/f/457/proposals/4213 ...it times out at about 1 minute.
Also, Colin's proposal times out for me too now that he's at 78 comments. https://wedecide.green.ca/processes/create-proposals/f/457/proposals/4125
...it didn't before. So I'm guessing I've passed a threshold just under 78 comments.
And when I look at all-comments, when logged-in, on this proposal (16 comments)... https://wedecide.green.ca/processes/create-proposals/f/457/proposals/4121 ...it takes me about 20 seconds logged in, and 1 seconds logged out.
https://wedecide.green.ca/processes/create-proposals/f/457/proposals/4165 ...takes me 14 seconds logged in, and 1 second logged out.
paarals
A participant cannot view his own proposals because he gets a Cloudflare timeout. We believe it's related to the large number of comments (>100) his proposal has received, as the error is occurring on multiple proposals with a lot of comments.
To replicate:
Note that the timeout occurs only for the submitter. Other users can access the proposal without any problems.