Support

There is no need to worry. This is a cosmetic Joomla! issue.

This is Joomla failing to understand what our update SQL code does, thereby WRONGLY inferring that the database is not updated. As far as I know, this is a known issue with ENUM fields and we've certainly seen it before (in Akeeba Ticket System, a few months ago). It's not causing any problem other than it being annoying, and us having to tell people that yeah, this is Joomla dropping the ball, nothing to see here.

:)

We've published version 7.4.6 which solves the problem. We had to erase a file, pretending Admin Tools 7.1.1 (the last time we had previously updated this table column) never existed. This convinced Joomla to see only the latest file and happily report that everything is fine.

This must be the silliest reason I've ever had to make a new release. In the end of the day, the problem is that Joomla! saw this column had changed twice, in version 7.1.1 and 7.4.5, correctly saw that it follows version 7.4.5, then stupidly reported that the column no longer adheres to the two and a half years older version 7.1.1.

I would've normally filed this as a bug, but they've blocked me from submitting bugs on GitHub and/or the Joomla! issue tracker. So, yeah, all I can do is being sarcastic and work around obvious bugs in Joomla instead of, you know, fix them like I had been doing between 2009 and 2014. Hopefully someone else will let the maintainers know and they will fix this issue. It's simple, really. It's just a case of filtering an array, hint hint wink wink for any core maintainers reading this.