We run our own instance, and just upgraded. After the upgrade, a bunch of the communities I have subscribed to on other lemmy instances aren’t showing historic content that our instance was aware of before the upgrade.
Also, approximately half of my subscribed communities were showing the subscription as pending, despite them not being pending prior to the upgrade
Did we do something wrong, or is this a known issue?
You must log in or register to comment.
Lemmy Support
!lemmy_support@lemmy.mlSupport / questions about Lemmy.
- 0 users online
- 12 users / day
- 24 users / week
- 26 users / month
- 19 users / 6 months
- 11 subscribers
- 140 Posts
- 444 Comments
- Modlog
- mods:
Did the postgres upgrade script show any errors?
Did you do any manual DB editing before you ran this?
I ask because I tested this upgrade many times, on production DBs that have years of history, to make sure nothing got lost.
I don’t think they’re lost. They’re just not displaying correctly. They still appear in RSS feeds and notifications, and they federate successfully. They just don’t show up properly in the lemmy interface. But that’s true even on the lemmy.ml instance. If I try and view all comments for this discussion on lemmy.ml, I can’t see any comments!
We haven’t gone too deep in to troubleshooting on our end yet, because I wasn’t sure if this was a known issue. The fact that they don’t display on the flagship instance either is what made me think it might not be on our end
Screenshot of this thread on lemmy.ml, with comments not showing
Could you open up an issue on the lemmy-ui github for this? With how to replicate it too. Thanks
Will do!
Thanks. Been a lot of bugs lately, I apologize for not testing this better.