• Resolved extinctdisney

    (@extinctdisney)


    Sharing this purely as an FYI as I’ve removed the plugin as I don’t believe it can accomplish what I was trying to do.

    A few seconds after selecting the “Scan” option I received a critical error. This was immediately followed by an email from wordpress.

    Error Details: An error of type E_ERROR was caused in line 51 of the file /home1/pldkvsmy/public_html/wp-content/plugins/media-file-renamer/core.php. Error message: Maximum execution time of 30 seconds exceeded

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Jordy Meow

    (@tigroumeow)

    Hi ??

    Sharing this purely as an FYI as I’ve removed the plugin as I don’t believe it can accomplish what I was trying to do.

    What were you trying to do?

    Error Details: An error of type E_ERROR was caused in line 51 of the file /home1/pldkvsmy/public_html/wp-content/plugins/media-file-renamer/core.php. Error message: Maximum execution time of 30 seconds exceeded

    This error happens in some cases, where you have directories with a (really) huge number of files. For others who might encounter that issue, there is an easy way to avoid it: by unchecking the option called “Case Sensitive” in the plugin settings, and that will not happen.

    A better solution might be to change the PHP setting max_execution_time to more than 30 seconds. I normally use 300 seconds (5 minutes), and sometimes 600 seconds (10 minutes).

    Also, I can’t see a “Case Sensitive” setting (where is it?) and performing a case insensitive renaming on a Unix system can cause problems.

    Plugin Author Jordy Meow

    (@tigroumeow)

    @galbaras is right, it’s also a possibility while keeping all the features of Media File Renamer on. But if all the filenames are all in lowercase in the system, then that option can be turned off (and it will improve the performance of the plugin, and therefore, the whole Media Library).

    Also, I can’t see a “Case Sensitive” setting (where is it?) and performing a case insensitive renaming on a Unix system can cause problems.

    It’s a new option, I added it in the very last version of the plugin (so it has been out only for a day now).

    I see “case sensitive” now (just updated). Why should it make a (big) performance difference?

    Actually, on a Windows system, comparison must be case insensitive. Otherwise, renaming can overwrite valid files. On a Unix system, there is no guarantee that file names are lowercase, if they haven’t all been renamed.

    Plugin Author Jordy Meow

    (@tigroumeow)

    Case sensitive means, for the plugin, that it will make sure the file “abc.jpg” doesn’t exist already, even if it ‘s “ABC.JPG”. So basically, the safe option is to check it (by default, it is).

    However, to make that check, the content of the directory needs to be retrieved. Normally, that’s fast, but if there are tens of thousands of files… that might take time depending on the server.

    It doesn’t seem it’s an issue for many, but I had a few users running into timeouts caused by it, hence the option ??

    In my case, all filenames are using lowercase, so I don’t need that option to be checked.

    More about it here: https://stackoverflow.com/questions/3964793/php-case-insensitive-version-of-file-exists

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Critical Site Error’ is closed to new replies.