Delete server rules button does not delete rule.

[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.

[yehuda1491]

@girish @nebulon
Per Dan: ENABLE_CACHE_CONFIG must be set to true after installation (and FALSE before installation), seems like its causing a lot of issues so I will fix this after work

[yehuda1491]

@girish @nebulon A person I know says they fixed the issue, but I don't know how this relates to cloudron/docker:

"Btw, I was able to get pixelfed working I had to do the setting permissions step again

cd pixelfed
sudo chown -R http:http . # change user/group to http user and http group
sudo find . -type d -exec chmod 755 {} ; # set all directories to rwx by user/group
sudo find . -type f -exec chmod 644 {} ; # set all files to rw by user/group

(replace http in http:http with the user you run pixelfed as with the systemd service) then after this, i did

php artisan cache:clear

and then these

php artisan config:cache
php artisan route: cache
php artisan migrate --force

from the upgrade steps now it all works"

[yehuda1491]

@girish @nebulon Dan is working on my test server now...

[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?