FileSieve 4

  • Status Assigned
  • Percent Complete
  • Task Type Bug Report (major)
  • Category Plugin
  • Assigned To
    Joseph Cox
  • Operating System All
  • Severity Medium
  • Priority Medium
  • Reported Version 4.19
  • Due in Version Undecided
  • Due Date Undecided
  • Votes
  • Private
Attached to Project: FileSieve 4
Opened by Joseph Cox - 28 June 2017
Last edited by Joseph Cox - 05 January 2018

FS#278 - Tag (and possibly EXIF?) Method doesn't rename actual files

The Tag plugin is where the issue was found; the EXIF plugin will be investigated later.

The Tag plugin doesn’t actually rename processed files, but instead just creates directories based on the entered Name Mask.

Was this the original intention? Doesn’t seem anywhere near as useful as also being able to rename the files.

For example, original file:

  • my_song.mp3


This results in:

  • My Album\My Song.mp3\my_song.mp3

It should be:

  • My Album\My Song.mp3

The original filename for the file doesn’t get changed by FileSieve when it gets processed. FileSieve doesn’t seem to modify the filename at all.

That can’t be right?

Joseph Cox commented on 28 June 2017 05:23 PM

I think FileSieve had a critical part of its processing core rewritten so that paths and filenames are treated independently but the Tag (and EXIF) plugins haven't been updated to reflect the change.

Joseph Cox commented on 28 June 2017 05:30 PM

This isn't going to be an easy fix; will have to dedicate tomorrow morning to fixing any affected plugins.

Joseph Cox commented on 28 June 2017 06:01 PM

Development blog post: Cores, Plugins, and Rewrites

Douglas Wofford commented on 28 June 2017 07:15 PM

Interesting. I wasn't seeing this because I haven't been changing file names – just reorganizing files from a single directory into a hierarchy of directories. As a result, my naming mask is only for the path and does not specify a mask for the file name at all.

You are correct, however, that I would also expect to be able to change the filename as well as the path if that was my need. Does it make sense for the file renaming to be handled in a Modifier? The current explanations seem to point to Method as a path definition and then Modifiers as a file name modifier once the file has been moved to the new path. If there was a file name mask available as a Modifier, that would make a lot of sense (from the interface) to me. I don't know, though, if that's easier/harder in the current code.

Joseph Cox commented on 07 July 2017 11:45 AM

Due to a major bug fix in 4.20 that I want to release ASAP, I'm going to push this task back. This Method will need significant rewriting, anyway.


Available keyboard shortcuts


Task Details

Task Editing