Support

Your installation is missing a file. You can very easily fix this.

Download the latest version of Admin Tools from our site.

Extract the ZIP file locally.

You will have a folder named admintoolswp.

Upload this folder into your site's wp-content/plugins folder, overwriting existing folders and files.

The error should now just go away.

I am wondering the same thing as well!

The crazy thing is that the Akeeba\AdminTools\Admin\Helper\Language class —therefore its file, admintoolswp/app/helper/language.php— have been around since the first alpha builds we created internally back in 2017 when we were still developing this product. It's not a new file. Moreover, the last time we did any update to this file other than changing the copyright date was on January 21st, 2020. The next three years all we changed on that file was the copyright from 2017-2020 to 2017-2021, 2017-2022, and 2017-2023. That's the beginning, middle, and end of the changes.

Since this file is basically unmodified for just over 3 years I cannot believe that it's some kind of host suddenly starting to delete it, like what we had seen nearly 10 years ago. I mean, sure, that's a possibility… but it's unlikely. Unless some hosts are running some insanely broken malware scanner which sees INI parsing and misunderstands it as ini_set which modified the PHP configuration. Then again, we do use ini_set in other parts of the code which neither go missing, nor cause any problem. Insane, right?!

Further to that, we have only started seeing this problem since WordPress 6.1.0 was released. At the same time, we also saw problems with updating Akeeba Backup, again pointing to files going missing or at the very least their contents not matching what we ship (and I did checked the files you get from 5 different locations, they are always correct, so it's not an issue with our packaging process or the distribution process, something we last touched a year ago).

I thought this might be something broken in WordPress, but I can't see any change which would corroborate this suspicion. I originally thought that WordPress does not clean the OPcache on update (there's a filter to disable this behaviour and I could reasonably suspect a third party doing something idiotic), but here you are saying that you had installed this update at least two months before this problem occurred.

If you are not sure that the update was installed for a while, please let me know. It would at least not rule out something breaking in WordPress plugin updates.

I am not going to put the blame on Watchful because we have seen it happen on sites which used WordPress itself to update the plugin. 

Moreover, knowing the approximate overlap between users of our software and users of Watchful (based on off-the-record, approximate numbers they shared with us in an in-person discussion a couple of years ago), I don't think they are the problem. If Watchful were to blame I would expect to see a heck of a lot more tickets, much closer to the release of the update. We have seen very sporadic issues.

Finally, I know they don't delete files. The problem here was a missing file.

Let me ask another question. Did that problem happen to all of your WordPress sites or only some of them? If it happened to more than one sites, are they all hosted with the same hosting company or different ones?

I checked the other reports, they are not on the same host and I have seen that some of them explicitly stated it was WordPress which updated the plugin. It looks like something in WordPress is broken but it only breaks on SOME hosts. To me, it sounds a lot like the bug in Joomla which makes it sometimes forget to copy files on update, something many of us have seen and tried to identify and fix but can't figure out why is happening, or what is triggering it.