Critical Error on Plugin Page

@frankprim

Maximum execution time of 30 seconds exceeded in [..]src/fs/FileFinder.php

It looks like searching for translation files on disk is taking a long time, which suggests there is a lot of folders to scan.

Can you post the full stack trace so I can see specifically what search operation is taking so long?

Deleting the plugin completely has done nothing.

I’m not sure what you mean by this. If you deleted Loco Translate, it cannot possibly be running so can’t give you an error. Can you clarify?

Here are the full stack traces:

[Wed Mar 03 09:21:33.436575 2021] [proxy_fcgi:error] [pid 23582:tid 140188269410048] [client 88.207.253.135:36778] AH01071: Got error ‘PHP message: PHP Fatal error: Maximum execution time of 30 seconds exceeded in /var/www/vhosts/kaerjeng.lgs.lu/httpdocs/wp-content/plugins/loco-translate/src/fs/FileFinder.php on line 358’, referer: https://kaerjeng.lgs.lu/wp-admin/admin.php?page=loco-core&action=view

[Wed Mar 03 09:21:42.292729 2021] [proxy_fcgi:error] [pid 23582:tid 140186650404608] [client 88.207.253.135:36796] AH01071: Got error ‘PHP message: PHP Fatal error: Maximum execution time of 30 seconds exceeded in /var/www/vhosts/kaerjeng.lgs.lu/httpdocs/wp-content/plugins/loco-translate/src/fs/FileFinder.php on line 358’, referer: https://kaerjeng.lgs.lu/wp-admin/admin.php?page=loco-theme

Deleting the plugin completely has done nothing. -> Reinstalling the plugin did not fix the error

Reinstalling the plugin would not fix an error like this.

You haven’t posted stack traces. You have just posted two separate instances of the same error. Possibly a trace isn’t available to you. Moving on, I’m going to assume this is happening while searching for PO files under the languages directories.

It seems strange that scanning the wp-content/languages directory (as it would with Core) would take this long. It would not be a recursive search and I’d expect it to take under a second.

I’d want to know if this was really a long process, or an infinite loop that would never complete. The only way to know that is to debug it, and/or set a very long timeout to see what it’s doing. Do you have the means to do this?

Hello

I have set a timeout of 120 seconds. Then Loco works again

OK, good. This demonstrates it is not an infinite loop bug, but is not a permanent solution to your problem.

If I were you I’d still investigate where the bottle neck is. Maybe it’s slow disk reads, or maybe that’s just were it eventually times out. If you find out anything useful that I can do to improve the plugin, then post back. In the mean time I am marking as resolved.