Difference between revisions of "ReNamer:Failed renaming"
Jump to navigation
Jump to search
(Document the "long path" specification. Rephrase the introduction.) |
|||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| + | {{Up|ReNamer}} | ||
{{Expand| | {{Expand| | ||
* Give examples for all reasons | * Give examples for all reasons | ||
* Include possible workarounds}} | * Include possible workarounds}} | ||
| − | + | The renaming operation can fail for a variety of reasons. | |
| + | |||
| + | The built-in [[ReNamer:Validation|validation process]] attempts to identify common problems prior to renaming by raising warnings during the preview process, but it cannot catch all possible problems. | ||
| + | |||
| + | The most common reasons for failed renaming are as follows: | ||
{| class="wikitable" | {| class="wikitable" | ||
| Line 10: | Line 15: | ||
! Solution | ! Solution | ||
|- | |- | ||
| − | | File path | + | | File path is too long |
| − | | Shorten the | + | | Shorten the name of the file or any of its parent folders so that the total characters in the entire path is within the limit. |
| + | |||
| + | In Windows, the maximum file path length is '''260 characters''', as defined by the '''MAX_PATH''' constant. As a workaround, use the "long path" specification by prepending the file path with <code>\\?\</code> to effectively raise the maximum length of file paths to '''32,767 characters'''. See the [[ReNamer:Long paths|Long paths]] article for additional information. | ||
|- | |- | ||
| Destination file already exists (name conflict) | | Destination file already exists (name conflict) | ||
| There are multiple options: | | There are multiple options: | ||
* Rename the name in the list (Refer to [[ReNamer:Menus_for_the_Files_pane#Options_menu|Fix conflicting new names]]). | * Rename the name in the list (Refer to [[ReNamer:Menus_for_the_Files_pane#Options_menu|Fix conflicting new names]]). | ||
| − | * Rename the 'other' file that is at the destination to avoid conflict | + | * Rename the 'other' file that is at the destination to avoid conflict. |
| − | * [[ReNamer:Manual_editing|Manually edit the new name]] of the file to avoid conflict | + | * [[ReNamer:Manual_editing|Manually edit the new name]] of the file to avoid conflict. |
|- | |- | ||
| Source file does not exist | | Source file does not exist | ||
| This can happen because: | | This can happen because: | ||
* You moved or manually renamed the file outside of ReNamer. | * You moved or manually renamed the file outside of ReNamer. | ||
| − | * You [[ReNamer:Renaming_folders|renamed its folder first]] | + | * You [[ReNamer:Renaming_folders|renamed its folder first]]. |
Just remove the items listed in '''Files''' pane, and then add them again (with the new path). | Just remove the items listed in '''Files''' pane, and then add them again (with the new path). | ||
|- | |- | ||
| Line 32: | Line 39: | ||
|- | |- | ||
| Invalid destination path | | Invalid destination path | ||
| − | | You may have included invalid characters to the file name, such as: < | + | | You may have included invalid characters to the file name, such as: |
| + | <pre><nowiki>\/:*?"<>|</nowiki></pre> | ||
| + | |- | ||
| + | | Parent path changed earlier in the list | ||
| + | | A parent folder of the affected file has been renamed earlier in the list, which makes the path of the the affected file incorrect (out of date). | ||
| + | |||
| + | This can occur when renaming both folders and their contained files/folders at the same time. For this reason, the content must always be renamed first, before the parent, which can be achieved by sorting the list by the ''Folder'' or ''Path'' column in descending order. | ||
| + | |||
| + | For more information consult [[ReNamer:Renaming folders|Renaming folders]] article. | ||
|} | |} | ||
| + | |||
| + | [[Category:ReNamer]] | ||
Latest revision as of 16:03, 11 December 2023
The renaming operation can fail for a variety of reasons.
The built-in validation process attempts to identify common problems prior to renaming by raising warnings during the preview process, but it cannot catch all possible problems.
The most common reasons for failed renaming are as follows:
| Reason | Solution |
|---|---|
| File path is too long | Shorten the name of the file or any of its parent folders so that the total characters in the entire path is within the limit.
In Windows, the maximum file path length is 260 characters, as defined by the MAX_PATH constant. As a workaround, use the "long path" specification by prepending the file path with |
| Destination file already exists (name conflict) | There are multiple options:
|
| Source file does not exist | This can happen because:
Just remove the items listed in Files pane, and then add them again (with the new path). |
| The file is being blocked by other program | Find the program that is currently using the file (using utilities like the Windows Task Manager or Process Explorer) and close it. (Sometimes the file is still being downloaded, in which case just wait!) |
| You don't have sufficient privileges to rename the file. | Get privileges by contacting the Admin (or the owner if the item is shared on a neighborhood PC). If you are the Admin, check the permissions of the folder. |
| Invalid destination path | You may have included invalid characters to the file name, such as:
\/:*?"<>| |
| Parent path changed earlier in the list | A parent folder of the affected file has been renamed earlier in the list, which makes the path of the the affected file incorrect (out of date).
This can occur when renaming both folders and their contained files/folders at the same time. For this reason, the content must always be renamed first, before the parent, which can be achieved by sorting the list by the Folder or Path column in descending order. For more information consult Renaming folders article. |