Auto rename doesn’t seem to be working after first use

  • Resolved wspohr

    (@wspohr)


    5 years, 7 months ago

    I have changed the title of the images. The Scan shows the correct desired filename. All the files have an unlocked icon next to them. I click on the “Rename all” button and it shows the progress count, and on completion when I refresh I see that none of the filenames have changed?
    Similarly when I use the Library directly, it shows the correct new name when I hover over the “Auto” button but when I click, it shows the twirly circle, but afterwards the filename is still unchanged. The files are definitely unlocked.

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

    (@tigroumeow)

    Hi,

    I don’t recommend you to use the bulk method right for testing, or for the first time. Maybe I should mention this in my tutorial ?? I am afraid actually some users also miss the features directly available in the Media Library.

    If the Renamer shows you a new name, but actually don’t rename the file to that name, indeed, something wrong happened. Rarely, the plugin doesn’t have access to the file, for example when it is hosted outside WordPress (an unusual directory, or a remote service like S3).

    Please have a look into your PHP Error Logs (if you don’t know about what it is, have a look here: https://meowapps.com/how-to-debug-wordpress/). What do you see?

    Thread Starter wspohr

    (@wspohr)

    I am told by my web hosting provider that this is the error log of most recent php errors. I just tried a failed auto-rename now and I note there are no errors that have popped up:

    [Wed Apr 10 20:13:56.186218 2019] [access_compat:error] [pid 241853] [client 139.180.220.10:64786] AH01797: client denied by server configuration: /home/ukuveelj/public_html/wp-content/uploads/wc-logs/
    [Wed Apr 10 20:13:56.176899 2019] [access_compat:error] [pid 241853] [client 139.180.220.10:64786] AH01797: client denied by server configuration: /home/ukuveelj/public_html/wp-content/uploads/woocommerce_uploads/
    [Wed Apr 10 20:13:53.847358 2019] [access_compat:error] [pid 238054] [client 139.180.220.10:64787] AH01797: client denied by server configuration: /home/ukuveelj/public_html/wp-content/uploads/wc-logs/
    [Wed Apr 10 13:58:47.307597 2019] [authz_core:error] [pid 236624] [client 169.1.1.233:23156] AH01630: client denied by server configuration: /home/ukuveelj/public_html/php.ini
    [Tue Apr 09 13:09:00.698737 2019] [access_compat:error] [pid 207669] [client 35.240.153.206:63236] AH01797: client denied by server configuration: /home/ukuveelj/public_html/wp-content/uploads/wc-logs/
    [Tue Apr 09 13:09:00.673018 2019] [access_compat:error] [pid 207669] [client 35.240.153.206:63236] AH01797: client denied by server configuration: /home/ukuveelj/public_html/wp-content/uploads/woocommerce_uploads/
    [Tue Apr 09 13:09:00.665725 2019] [access_compat:error] [pid 208319] [client 35.240.153.206:63238] AH01797: client denied by server configuration: /home/ukuveelj/public_html/wp-content/uploads/wc-logs/
    [Tue Apr 09 10:45:17.864798 2019] [access_compat:error] [pid 77653] [client 35.240.151.218:56425] AH01797: client denied by server configuration: /home/ukuveelj/public_html/wp-content/uploads/wc-logs/
    [Tue Apr 09 10:45:17.722854 2019] [access_compat:error] [pid 99642] [client 35.240.151.218:56423] AH01797: client denied by server configuration: /home/ukuveelj/public_html/wp-content/uploads/wc-logs/
    [Tue Apr 09 10:45:17.694545 2019] [access_compat:error] [pid 99642] [client 35.240.151.218:56423] AH01797: client denied by server configuration: /home/ukuveelj/public_html/wp-content/uploads/woocommerce_uploads/
    [Tue Apr 09 01:54:12.591378 2019] [access_compat:error] [pid 112020] [client 35.240.151.218:60059] AH01797: client denied by server configuration: /home/ukuveelj/public_html/wp-content/uploads/wc-logs/
    [Tue Apr 09 01:54:12.558997 2019] [access_compat:error] [pid 112020] [client 35.240.151.218:60059] AH01797: client denied by server configuration: /home/ukuveelj/public_html/wp-content/uploads/woocommerce_uploads/
    [Tue Apr 09 01:54:12.558553 2019] [access_compat:error] [pid 99044] [client 35.240.151.218:60060] AH01797: client denied by server configuration: /home/ukuveelj/public_html/wp-content/uploads/wc-logs/

    Thread Starter wspohr

    (@wspohr)

    I have also just uploaded a .png file and managed to autorename that just fine. But the .png files that were uploaded yesterday refuse to be renamed.

    Plugin Author Jordy Meow

    (@tigroumeow)

    Hello @wspohr,

    In fact, this looks like an Access Logs, not the PHP Error Logs. The content is very different ?? So could you ask them again for the PHP Error Logs?

    That’s quite weird the PNG you uploaded before can’t be renamed, the one today can. What are their names? Maybe there is an encoding issue? The Renamer doesn’t rename (and even AVOID doing it) if the file can’t be found in a standard way (if PHP don’t really see it). This happens when you move from one hosting service to another usually, but it doesn’t seem to be your case.

    I have a quite the same issue. Your rename-log says:

    2019-06-10 10:57:02: ** Rename Media: serv1.jpg
    2019-06-10 10:57:02: New file should be: 1.jpg
    2019-06-10 10:57:02: The new file already exists (/var/www/vhosts/hosting105092.af9be.netcup.net/wordpress.herrmittmann.de/wp-content/uploads/2016/12/1.jpg). It is not a case issue. Renaming cancelled.

    In the end quite a lot images remain un-renamed.

    I also activated “Rename on Post Save”.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Auto rename doesn’t seem to be working after first use’ is closed to new replies.