Tickets :: [#2882] hierarchical folder rename

10/28/2005 04:33:15 AM	Michael Slusarz	Comment #3 Assigned to Michael Slusarz State ⇒ Resolved	Reply to this comment
Fixed (albeit by renaming from the top of the tree down rather than your method of 'checking' to see if child folders are auto-renamed).

10/27/2005 06:43:23 PM	dgehl (at) inverse (dot) ca	Comment #2 New Attachment: rename.txt	Reply to this comment
2) rename only the main folder, then test if the folders below have already followed and rename them only if necessary Attached the corresponding replacement code for the rename function which works for me.

10/27/2005 03:59:29 PM	dgehl (at) inverse (dot) ca	Comment #1 State ⇒ Unconfirmed Priority ⇒ 2. Medium Type ⇒ Bug Summary ⇒ hierarchical folder rename Queue ⇒ IMP New Attachment: folder_rename.png	Reply to this comment
I noticed the bug in 4.0.3, but after a look at the code in CVS, it does not seem to be fixed yet. When you rename a folder containing sub and sub-subfolders, the code in lib/Folder.php (function rename) obtains the complete list of sub-folders on the server and renames all these folders. Cyrus, since version 2, does automatically rename all subfolders. So basically, it is not any more necessary (when using a new version of cyrus) to rename the subfolders 'manually'. What is worse is that the users gets error messages when IMP tries to rename a subfolder which does not any more exist under the original name. I see at least two possible solutions ... 1) always rename the folders in the 'right' order (starting with the most imbricated ones) 2) rename only the main folder, then test if the folders below have already followed and rename them only if necessary