TL;DR: If you’ve been using Tesseract and didn’t realize it had admin capabilities: surprise! It totally does.

A user pointed out to me this morning that Tesseract wasn’t detecting that they were an admin.

Basically, I completely forgot that the admin flag was moved from person to local_user in 0.19 and never updated the admin check function to account for that. So when it looked in the person object in 0.19, it wasn’t there, the admin role was never assigned, and a big chunk of the application remained hidden away.

This meant the admin panel, instance-wide moderation menus, and admin-only options (ban from instance, registration applications, private message reports, etc) were not being shown to admins on 0.19.x instances. Only communities they were explicit moderators of would show the mod options or reports.

Mea culpa.

The only instance I can test admin role functions against is my own, which is still on 0.18.5 (for reasons, I swear). So, I was not aware that this has been a bug for months 🙃

I’ve pushed a fix to the 1.3.0 branch and merged it into main as well. The Docker images for 1.3.0 and latest were also updated with this fix. The change is backwards-compatible with 0.18.x so nothing will change there.

If you deployed a version of 1.3.0 prior to 2024-05-11 12:40:00 UTC (or are still running 1.2.9 on a 0.19.x instance), you may want to pull the updated image or rebuild from the main or 1.3.0 branches to grab this fix.