this post was submitted on 07 Jul 2023
2 points (75.0% liked)

Meta (slrpnk.net)

601 readers
18 users here now

Here we can discuss anything about this Lemmy instance/server itself.

Our XMPP support chat: Movim or XMPP client.

Please also refer to our Wiki

founded 2 years ago
MODERATORS
poVoq
Five
ProdigalFrog
2
Issues with pages loading (self.meta)
submitted 1 year ago by andrewrgross to c/meta
5 comments fedilink hide all child comments
 

I've been having issues today with the front page not loading content. Refreshing works sometimes, but not always. I've also had some posts show a loading icon indefinitely. When I leave and come back, they usually load. I'm not sure why, but I figure sharing this will help with troubleshooting.

Is there any bug submission process I should follow aside from posting in !meta?

you are viewing a single comment's thread
view the rest of the comments
[–] andrewrgross 1 points 1 year ago (1 children)

This has been on Firefox, btw. I'm just now testing on Chrome.

[–] poVoq 3 points 1 year ago* (last edited 1 year ago) (1 children)

Can you please test again with version 0.18.1 now? You might have to force reload the page with CTRL+F5 once.

[–] andrewrgross 1 points 1 year ago (1 children)

No, that hasn't resolved it yet.

The two issues I'm encountering:

  1. When I go to the main page it is blank. See below:

When I click on "Explore communities" it works, and when I click on a community it works. However...

  1. When I click to view an individual post, it gets hung on the loading screen:

I'm not sure if it's useful, but there are some errors in the console:

"The Notification permission may only be requested from inside a short running user-generated event handler" "Uncaught (in promise) TypeError: t.at is not a function" "Uncaught (in promise) TypeError: c.at is not a function"

Everything is still working in Chrome. Let me know if there's anything I can do to assist with troubleshooting. I can try Firefox on a different OS if you like.

[–] poVoq 2 points 1 year ago

I am using Firefox as well here and I can't reproduce this error at all. Did you force reloade the page with CTRL+F5? There is some issue with caching of older Javascript files from pre-0.18.1 lemmy-ui versions, but a force reload should fix that. Otherwise really no idea, sorry.