View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0020606 | MMW 5 | Tagging / organizing (properties / auto-tools) | public | 2024-02-13 16:05 | 2024-03-01 10:32 |
| Reporter | lowlander | Assigned To | |||
| Priority | urgent | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 5.1 | ||||
| Target Version | 5.1 | Fixed in Version | 5.1 | ||
| Summary | 0020606: Custom field names can be same as tag which causes problems with (Auto-)Tag (Files) | ||||
| Description | You can name a Custom field Album, which means you now have 2 fields named Album. When using (Auto-)Tag (Files) with the Mask <Album> it takes the actual Album value, leaving no method to use the Custom field. There is also conflict with Masks like <Folder>. 1) Users should still be able to use <Custom x> as Mask even when they gave the field a name. Custom name should also be allowed, but in case of conflict the original field (as currently implemented) would be used. 2) When changing the Field name to an existing tag name the user should get a warning that this name has already been used, potentially warning about organizing conflict. | ||||
| Additional Information | https://www.mediamonkey.com/forum/viewtopic.php?t=105778 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 3000 | ||||
|
|
Both 1&2 fixed in build 3000 2) as indicating just "Error!" would not be informative I implemented avoiding to enter existing field i.e. if user renames 'Custom 1' heading to 'album' in Options > Fields then OKing the dialog leaves it still as 'Custom 1' (the old value) not allowing to change it to an existing mask field.. |
|
|
Verified 3001 |
