Delete server rules button does not delete rule.

[dansup]

Hello, Pixelfed developer here. I am working on a fix for this, and I apologize about the inconvenience this has caused!

[nebulon]

@yehuda1491 thanks for keeping us in the loop. Presumably some folders need to be moved to read/writeable locations for the cache if it is enabled during runtime then.

[nebulon]

Just quickly tried to enable cache during runtime, but it didn't seem to change the settings situation (also can't detect any actual errors). Let us know if there are any ideas we should test there.

[dansup]

@nebulon I just released a new version!

[nebulon]

@dansup hi and welcome here! I am just trying the new version here. Should the ENABLE_CACHE_CONFIG=true be set during runtime then?

[dansup]

@nebulon Yes, I added a fallback to handle the initial race condition before the database is configured so it will work as expected!

Let me know if you have any issues or questions, and btw, I posted from my main fediverse account with a link back to this thread in case you wanted verification that I am in fact who I say I am!

https://mastodon.social/@dansup/112398832338424229

[nebulon]

@dansup unfortunately the new app version seems to behave the same on Cloudron with or without the confic cache set https://git.cloudron.io/cloudron/pixelfed-app/-/commit/512f3767c3bd6a54b4992c201d979d2a7623a86e

The actual values are never stored persistently it seems, like submitting the settings form like branding will succeed status code wise, but a reload of the settings page will reveal the defaults.

[dansup]

@nebulon Hi, I'm looking into this and will get back to you shortly!

[yehuda1491]

I'm starting to get discouraged about this...

[nebulon]

@yehuda1491 it appears that @dansup is pretty much a sole developer of pixelfed, so maybe if you have the ability to help debugging it would probably speed up the fix.

[yehuda1491]

@nebulon I wish, but coding is not my skillset. It's cool, I understand people have limited time and energy they can donate to the community.

[jkammerer]

hello @nebulon ,
i see you updated the package to 0.12.1. I made a fresh install of the app. Still i can't get the admin panel to work. Any changes in settings are dropped immediately. Is this broken only on cloudron installs? Pixelfed seems to be used widely. Is there some kind of workaround? Editing the env.production file?
Is @dansup aware that the issue persists?

[girish]

@jkammerer the package was updated to the latest tagged release and to use the latest PHP 8.3 . AFAIK, the issue still persists.

[jdaviescoates]

@dansup said in Delete server rules button does not delete rule.:

@nebulon Hi, I'm looking into this and will get back to you shortly!

Thanks! What did you discover? Does adjusting and saving settings work elsewhere? Or is this only a problem with the Cloudron package?

[andi1357]

Hello. I have the same problems with the admin dashboard. I have now noticed that in the profile settings, under manage discover settings, the options set are not saved, even though the system says it was saved successfully. But the next time I open it, everything is gone again.

[andi1357]

This post is deleted!

[girish]

I think the best way forward to solve this is to debug the app and see if this is an upstream issue or Cloudron packaging issue. I have created an internal task to debug this.

[girish]

Saving of admin values is fixed in the new package.

[girish]

Server rules also work. You can see it in action in our Pixelfed - https://pixelfed.cloudron.io/ . The 'Save' button keeps spinning (some bug?) but it works.

[archos]

Thank you very much, this is great news!