Admin can't change group settings

[ThmsD]

The bot was accidentally removed from the group by another admin. After I have added it again, it is not possible to change the group settings. The message "You don't have permission to change settings" always appears.

The admin list seems to be up to date, because the counter shows the number of admins in the group.

[ranrinc]

I'm experience the same issue. However this group was not create by me, and yes, I'm the bot owner and an Admin on the groups

[aniolm9]

Same here. I'm in the SUPERADMINS list and I'm admin (not creator) of a group, but only the creator, who is not in the SUPERADMINS list can change settings. EDIT: This also applies to /kick and /ban commands. Only the creator can issue them.

[Qwerty-Space]

@aniolm9 Super admins cannot change group settings. You must be an admin of the group.

Use the /cache command to refresh the admin list.

[aniolm9]

@Qwerty-Space I'm admin of the group, with all rights except granting admin permissions. Running the /cache command I see there are 6 admins, the correct number, but I still can't change settings or issue /ban and /kick commands. The /warn command does work.

[Qwerty-Space]

@aniolm9 Did the owner grant you the change group info permission or the ban users permission?

[aniolm9]

@Qwerty-Space Yes. All permissions except adding new admins. EDIT: I have tried with the adding new admins permission and it doesn't work either.

[D-VR]

Same issue here too. Funnily enough I was able to change group settings before the /cache hit. (so when /dashboard showed 0 admins it worked fine, but after it showed admins it stopped working) I'm admin with full rights in the group, and super admin. is this a database issue? the only difference i could see to my setup is the docker versions, I'm using the recent versions instead of the old ones recommended in the Readme. Could this lead to this issue though? Is there a way to turn off admin caching? Would be interesting to see if that fixes the issue

[yangm97]

@D-VR this issue is related to the admin cache implementation using postgres, not docker related

[D-VR]

Thanks for the answer! I guess there is no fast easy fix?

I wouldn’t mind helping to solve this, but my lua and postgres knowledge is nil.

[aniolm9]

I've just checked and with the Docker image groupbutler/groupbutler:latest it works.

[BesedinSasha]

@aniolm9 hi! I have the same issue. How did you fix that? I use the same docker image