Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make edit history available on help posts #807

Open
cellio opened this issue Jun 21, 2022 · 5 comments · May be fixed by #1487
Open

Make edit history available on help posts #807

cellio opened this issue Jun 21, 2022 · 5 comments · May be fixed by #1487
Assignees
Labels
area: html/css/js Changes to front-end code complexity: unassessed Needs further developer investigation before complexity/feasibility can be determined. priority: high type: change request New feature or request

Comments

@cellio
Copy link
Member

cellio commented Jun 21, 2022

Help topics can be edited by moderators, and when editing you can enter a revision comment (like for regular posts). This implies that a history is kept in the database, but there's no way to see it through the UI. This request is to expose edit history for help topics. The history should be visible to anybody who can see the topic -- usually everybody, but there are a few mod-only topics.

@cellio cellio added area: html/css/js Changes to front-end code type: change request New feature or request priority: medium complexity: unassessed Needs further developer investigation before complexity/feasibility can be determined. labels Jun 21, 2022
@cellio
Copy link
Member Author

cellio commented Jun 21, 2022

If the information is in the database then this should be an easy UI change (with an added access check). If the information isn't already being stored, then this becomes a much bigger request that should be re-evaluated for priority.

@cellio
Copy link
Member Author

cellio commented Jan 25, 2023

The edit history will also need to account for changed made via UPDATE_POSTS=true rails db:seed. I don't know if seed updates record their changes anywhere now.

@trichoplax
Copy link
Contributor

If it turned out that the history was not being recorded, would that make this issue high priority? If so, is it worth labelling it high priority until that is determined, and then downgrading it to medium priority if it turns out the history is already stored?

@cellio
Copy link
Member Author

cellio commented Oct 9, 2023

I had a help topic get clobbered a few months ago, so I think it's not recorded in the DB. Raising the priority.

@Oaphi
Copy link
Member

Oaphi commented Dec 15, 2024

I had a help topic get clobbered a few months ago, so I think it's not recorded in the DB. Raising the priority.

@cellio we had a bug that I fixed in #1201 - history for help / policy posts is recorded, it's just that a bug resulted in content being clobbered every time seeds with UPDATE_POSTS set to true have been run.

@Oaphi Oaphi linked a pull request Dec 15, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: html/css/js Changes to front-end code complexity: unassessed Needs further developer investigation before complexity/feasibility can be determined. priority: high type: change request New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants