Delete server rules button does not delete rule.

[girish]

@yehuda1491 maybe you can report it at https://github.com/pixelfed/pixelfed/issues/ . I have previously reported https://github.com/pixelfed/pixelfed/issues/4990 based on your report but upstream author said he had fixed it.

[yehuda1491]

@girish I left Dan a message on the Discord

[yehuda1491]

@girish Looks like a lot of other settings are not brought into the new admin section such as Landing/registration status, Branding/Server Name, Short & Long Description, Media/Media Types

[girish]

@yehuda1491 I see some stuff in settings. Is this what you mean?

[yehuda1491]

@girish Yes, but for instance in this screen the Admin Account was set before, not blank, if I reset it, it won't take. Ditto for the branding and other settings.

[yehuda1491]

[yehuda1491]

@girish It's all missing, and saving new won't take.

[iahonta1964]

My settings are also not saved and /horizon gives an error.

[archos]

I also have a problem with the version, rules cannot be added and I had a larger user storage limit and it is 5 Gb after the update and cannot be increased in the settings

[yehuda1491]

@girish It also breaks Curated Onboarding, there is just wide open registrations

[yehuda1491]

@girish Dan says "I will look into this after work, seems like something maybe corrupted in the config_cache table, however it will be easy to fix"

[yehuda1491]

@girish his fix didn't work, and of course this is much more extensive than just the rules.

[archos]

I went back, to an older version

[yehuda1491]

I had to roll back to the previous Pixelfed version, I couldn't leave everything unconfigured and registrations wide open.

[girish]

@yehuda1491 do you happen to know what his plans are? Will he be making a new release with fixes? Maybe we can revert the Cloudron package release.

[yehuda1491]

@girish I told Dan this is not a one-off issue, that more people than just me are experiencing the issue. I'm going to setup a Cloudron server with one Pixelfed instance to see if I can replicate the issue with 0.12.0 that he can diagnose. If I can't replicate it with a fresh 0.12.0, it is likely related to the upgrade from 0.11.13 I'm imagining. Is there a way to start a fresh install with a specific version?

[girish]

@yehuda1491 yes, https://git.cloudron.io/cloudron/pixelfed-app/-/blob/master/CHANGELOG?ref_type=heads gives a mapping between package version and pixelfed version. Click on pixelfed in appstore and change the URL bar to have the right package version and then click install.

[yehuda1491]

@girish It does replicate on a fresh 0.12.0 install, fyi. I'll let you know what happens.

[yehuda1491]

@girish still haven't heard from Dan.
FYI I have no idea if this is relevant, but on both v0.11.13 & v0.12.0 in env.production ENABLE_CONFIG_CACHE=true, and in v0.11.13 diagnostics ENABLE_CONFIG_CACHE is true, but in v0.12.0 diagnostics ENABLE_CONFIG_CACHE is false.

[nebulon]

I was following the upstream defaults here https://github.com/pixelfed/pixelfed/blob/v0.12.0/.env.docker#L70 also the app itself does not build anymore with config cache enabled. The mentioned docs link in pixelfed is also sadly outdated.