Have been experiencing an odd sort of error for a while now, stubborn me using a lazy workaround and F5ing the page instead of seeking a more concrete solution, but it’s limiting my access to content in the linear sort of way that I had before. I’d appreciate any insight as to the source of this error.
The main page (https://lemmy.world/) initially loads correctly as per user selected attributes (Post/Comments, Show Hidden/Hide Hidden, etc.) as before, but once the bottom of the feed is reached and [Next] is selected, nothing happens.
The page simply cycles, appearing to try and load the following one while displaying greyed-out text field where post titles, link source, poster username, community are normally displayed on a successful load. After a minute or two, the page loading completes - minus the content. It’s simply blank with only the static headers available (Rainbow Mouse symbol/Lemmy.World, Communities, Create Post, etc.)
Yes to both AdBlocker Ultimate & filters. I checked the Dev console after disabling AdBlocker Ultimate for Lemmy and refreshing the main page, then attempting to navigate to page 2 as described above. Same issue, unfortunately, and I’m at a loss as to the meaning of the Dev console’s most recent error - apparently the page’s settings blocked an inline script, which appears to be AdBlocker Ultimate. If this was, in fact, the extension causing the error, I’m at a loss as to its role in the issue if the same error presents once it’s disabled.
Can you try an incognito window to help rule out any plugins? I run ublock (as do many others) and it’s never caused an issue for me, so may be a specific rule you have. Also try dumping your cache just to be sure.
I don’t use LW so no specific knowledge here, these are just general troubleshooting steps.
Good call, it functions normally as it did before when loaded in Incognito mode. I’ve cleared the cache and the problem appears to persist when navigating to second page (presumably 3rd, 4th, etc.).
I’ve noticed another plugin which I’d forgotten about, User-Agent Switcher and Manager, in which I’ve elected to whitelist Lemmy.world. This has also not solved the issue.
At that point I’d just disable every extension, test, then turn them on one at a time.
Cripes, not ideal, but you’re onto something. I’ll try it this weekend, and get back to you with the results later.