I just installed the 0.18.0 release candidate 1 of the lemmy-ui component.
This version removes websockets and should solve many strange issues. Like the glitching vote totals, sudden changes of posts etc.
Let me know if you see improvements, or new issues.
Yeah, it didn’t work. I reverted back.
Thanks for the work you’re doing :)
What went wrong?
It gave error messages and then started restarting the docker container…
invalid JSON bodyI got similar issues when playing around with it yesterday evening. For some reason, the client kept reporting sorting options as integers, while the back-end just expected ‘New’.
I think there have been some API changes so you need both the new backend and the new frontend.
thanks it is normal now. May be ui version 1.18 also need server to have same version?
@ruud Any news when it will be you and running?
Thank you for your work!
FYI, I needed to drop all cached files from
lemmy.worldin chrome afterwards. Otherwise clicking on the top right profile button would shift the entire page down.
The alternatives have been doing a good job in keeping up this time, it’s good to see.
Thanks for all the work that you’re doing!
Ohh, that’s the reason for gateway internal errors. Anyway keep up the good work 👍
I get “SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data”
Clearing the browser cache resolved the issue.
Result in bad gateway when opened with browser…
wrong thread
I think your post ended up in the wrong thread, are you using multiple browser tabs?
yes. dammit
Happens :)
I’ve had this happen sometimes. I’ll open a post and comment on it, only to find that I’m commenting on a different post. I don’t know why that happens. May be the post scrolls the moment you’re clicking the link and you get the one before that.
yes
I’ve had this happen sometimes. I’ll open a post and comment on it, only to find that I’m commenting on a different post. I don’t know why that happens. May be the post scrolls the moment you’re clicking the link and you get the one before that.
It’s a bug that happens when you have multiple browser tabs opened at the same time, devs are fixing it, we just have to be patient and wait for the next release.
