# \[X\] Filename-Filename failure on grandparent folder **URL:** https://community.mp3tag.de/t/x-filename-filename-failure-on-grandparent-folder/6378 **Category:** No Bugs **Created:** [March 4, 2008, 9:45am UTC](https://community.mp3tag.de/t/x-filename-filename-failure-on-grandparent-folder/6378 "2008-03-04T09:45:04Z") **Posts on this page:** 1 **Showing post:** 5
### Author: ![chrisjj](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/c/a698b9/32.png) [@chrisjj](https://community.mp3tag.de/u/chrisjj) #### Post date: [March 4, 2008, 9:15pm UTC](https://community.mp3tag.de/t/x-filename-filename-failure-on-grandparent-folder/6378/5 "2008-03-04T21:15:23Z")
> you also told Mp3tag to move this file into a directory structure %1\%2\ > which is 02480002922629\1\ after replacing the placeholders. Sure, but I expected that directory structure to be at the position I specified in Old filename pattern. I.e. the new pattern is supposed to replace the old i.e. at the same position. Experimenting more, I find that operation ignores the position of the old filename pattern, and uses instead the current directory. This looks like a fault to me. Certainly it is undesirable behaviour e.g. it makes it impossible swap %1 and %3 in this case. Florian, I woinder if this is related to the V2.39-\>V2.40 change of behaviour reported in [Bug Or New Feature ?](https://community.mp3tag.de/t/6277/3) . --- _[View the full topic](https://community.mp3tag.de/t/x-filename-filename-failure-on-grandparent-folder/6378)._