Server Error accessing topic revisions on a specific topic

Bug
1

Priority/Severity: Critical / Data Loss

Platform: Observed in all device types, operating systems and browsers

Description: The modal that allows to see the edits of a topic doesn’t work for a specific topic in a paying Discourse instance hosted on the official Discourse hosting. Also, the API only returns the post revision up until revision 5, but not any subsequent version after that one, like version 6, 7, 8 or 9, that return a 500 code, Internal Server Error.

Reproducible steps:

  1. Go to Designing and Operating the Reporting and Information Function - Proposals - Arbitrum
  2. Click on the orange edit pencil icon besides the post date
  3. The modal doesn’t show up

CleanShot 2024-11-29 at 03.37.15

2 Likes
2

This might be by design - site admins can restrict viewing revision history on a post and that could be what’s happening here.

If not and it should be visible, this is not data loss.

Since it’s a hosted site, if the site admins make a request for assistance, we can look into it.

2 Likes
4

hey @supermathie thank you for looking into this!

the post history is not restricted by admins in this case. otherwise the initial versions shouldn’t be available through the API, and they are, like I linked above.

I believe this was caused because this user made an edit and pasted the contents of a google doc in there. I think there might be some character that was pasted, that corrupted the data.

if you could look into it that would be great!

1 Like
5

I do see an error being logged on these requests, we’ll have someone look into it.

2 Likes
7

thank you so much! :blush:

1 Like
9

From the error in the server logs I am pretty confident there is no data loss, I added it to the list for the team, we will have look at it over the next 7 days and let you know when we have it sorted.

2 Likes
10

thank you @sam ! :pray:

1 Like
12

Thanks for the report @paulofonseca.eth, this will be fixed by

4 Likes
13

amazing! =) what an incredible turn around time I must say! :clap:

it’s already working! =)

14

The fix hasn’t been deployed to that instance just yet. Revision #5 is still “broken” :wink:

I clicked the Deploy button, should be live in ~10 minutes.

1 Like
15

yeah I just noticed that versions 5 though 12 are not showing up, neither in the API.

Thank you!

16

Annnnnd it’s fixed :wink:

1 Like
17

yup!! just saw it! awesome job! thank you so much! =)

18

This topic was automatically closed after 40 hours. New replies are no longer allowed.