Edit history

Summary

After setting up Single Community once and then reverting it to Public community again, the option becomes forever inaccessible - as in - it can't be toggled on ever again. Any attempt to toggle the option on will result in "This instance policy change is not allowed" even after all the relevant patches discovered by the community were applied. Since there's already an community ID locked to the option, it will fail, even if that community no longer exists. Regardless if this is an intentional limitation or not, the app itself handles this fine without any apparent issues and you can still choose to prune extra communities from admin panel afterwards, even create invites for them and have users join them. In a way, this could be a great way to limit people from creating other communities while still having separate communities on the app (ex. a separate community for supporters) but I do realize that this use-case is very unintentional and not within spec of the feature. I love experimenting around as you can see. Related to #583 and #640 - the only difference being is that I'm hitting fault point caused by a community lock being set. The same (potentially destructive) workaround should work for these two. edited to remove walls of text that is now outdated as single community mode is enabled properly now. Can't really verify if it still happens rn, I'll check in a week. Maybe the recent PR fixed it.

Steps to reproduce

1. Initially set it up so anyone can create communities
2. Create a few communities (optional)
3. Swap to single community mode
4. Swap back to public community mode without unrolling anything from the admin panel
5. Delete the community that was previously enrolled
6. Try to swap back to single community mode again, it will always reject the attempts to change since a lock is in place

Environment

Version: API, Media Proxy, Unfurl, Admin, Snowflakes, Users, Messages: 2026.630.20736 / pulling against :latest tag daily for the rest

Logs or screenshots

image image Developer console: fluxer-api:

Summary

After setting up Single Community once and then reverting it to Public community again, the option becomes forever inaccessible - as in - it can't be toggled on ever again. Any attempt to toggle the option on will result in "This instance policy change is not allowed" even after all the relevant patches discovered by the community were applied. Since there's already an community ID locked to the option, it will fail, even if that community no longer exists. Regardless if this is an intentional limitation or not, the app itself handles this fine without any apparent issues and you can still choose to prune extra communities from admin panel afterwards, even create invites for them and have users join them. In a way, this could be a great way to limit people from creating other communities while still having separate communities on the app (ex. a separate community for supporters) but I do realize that this use-case is very unintentional and not within spec of the feature. I love experimenting around as you can see. Related to #583 and #640 - the only difference being is that I'm hitting fault point caused by a community lock being set. The same (potentially destructive) workaround should work for these two. edited to remove walls of text that is now outdated as single community mode is enabled properly now. Can't really verify if it still happens rn, I'll check in a week. Maybe the recent PR fixed it.

Steps to reproduce

1. Initially set it up so anyone can create communities
2. Create a few communities (optional)
3. Swap to single community mode
4. Swap back to public community mode without unrolling anything from the admin panel
5. Delete the community that was previously enrolled
6. Try to swap back to single community mode again, it will always reject the attempts to change since a lock is in place

Environment

Version: API, Media Proxy, Unfurl, Admin, Snowflakes, Users, Messages: 2026.630.20736 / pulling against :latest tag daily for the rest

Logs or screenshots

image image Developer console: fluxer-api:

Checks

• ☑ I searched existing issues.
• ☑ I wrote this report in my own words, except for direct translation if needed.

Summary

After setting up Single Community once and then reverting it to Public community again, the option becomes forever inaccessible - as in - it can't be toggled on ever again. Any attempt to toggle the option on will result in "This instance policy change is not allowed" even after all the relevant patches discovered by the community were applied. Since there's already an community ID locked to the option, it will fail, even if that community no longer exists. Regardless if this is an intentional limitation or not, the app itself handles this fine without any apparent issues and you can still choose to prune extra communities from admin panel afterwards, even create invites for them and have users join them. In a way, this could be a great way to limit people from creating other communities while still having separate communities on the app (ex. a separate community for supporters) but I do realize that this use-case is very unintentional and not within spec of the feature. I love experimenting around as you can see. Related to #1007 and #1087 - the only difference being is that I'm hitting fault point caused by a community lock being set. The same (potentially destructive) workaround should work for these two. edited to remove walls of text that is now outdated as single community mode is enabled properly now. Can't really verify if it still happens rn, I'll check in a week. Maybe the recent PR fixed it.

Steps to reproduce

1. Initially set it up so anyone can create communities
2. Create a few communities (optional)
3. Swap to single community mode
4. Swap back to public community mode without unrolling anything from the admin panel
5. Delete the community that was previously enrolled
6. Try to swap back to single community mode again, it will always reject the attempts to change since a lock is in place

Environment

Version: API, Media Proxy, Unfurl, Admin, Snowflakes, Users, Messages: 2026.630.20736 / pulling against :latest tag daily for the rest

Logs or screenshots

image image Developer console: fluxer-api:

Checks

• ☑ I searched existing issues.
• ☑ I wrote this report in my own words, except for direct translation if needed.