Bug in 13.7.1 tree foldernames after renaming

Steps to reproduce:

  • Open a lister that shows the tree
  • Go to some (any) folder
  • Create subfolder in that first folder
  • Expand the first folder in the tree, so that it shows the new subfolder
  • Inline rename the subfolder in the lister, adding /x (or anything else) to the filename, creating a new subfolder
  • Name of subfolder in tree goes bad

In what sense? Could you give an example?

Foldername is prefixed with "02_" or some other number.

image

Same behavior here. It prefixed "11_".
To be fair: I never even tried a rename like this before...

Thanks, fixed in 13.7.2.

2 Likes

Thank you!