this post was submitted on 13 Aug 2023
18 points (100.0% liked)

Beehaw Support

2797 readers
6 users here now

Support and meta community for Beehaw. Ask your questions about the community, technical issues, and other such things here.

A brief FAQ for lurkers and new users can be found here.

Our September 2024 financial update is here.

For a refresher on our philosophy, see also What is Beehaw?, The spirit of the rules, and Beehaw is a Community

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

if you can see this, it's up  

founded 2 years ago
MODERATORS
remington
Zmodem
Gaywallet
alyaza
Lionir
Penguincoder
18
"blur nsfw", "auto expand" and "open in a new tab" settings won't stay. (self.support)
submitted 1 year ago by Seathru to c/support
6 comments fedilink hide all child comments
 

If I check any of those selections, click save, and then refresh the page, they are unchecked again. But all the other settings retain their status.

Firefox 116.0.2

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

Hi,

It's likely due to the 0.18.4 changeover/upgrade for Beehaw. Front end (UI) went fine to the 0.18.4 which is why you have those settings available to change; but the backend server (BE) had some issues and I needed to rollback to 0.18.2 to get the site functional. This is because those settings exposed in the UI are new with 0.18.4, while the other settings existed before 0.18.4 so they have a corresponding entry in the DB.

I know this is a frustrating setup and I'm sorry you're experiencing issues with expected behavior vs actual. We are working to resolve the BE issues quickly, to get everything in sync.

[–] Seathru 6 points 1 year ago

I figured it was something like that since auto expand and open in a new tab were new options. I only noticed when NSFW stuff wasn't blurred anymore and just wanted to bring it up in case no one had noticed.

Absolutely no bother. Appreciate all ya'll do.

load more comments (1 replies)