# No warning given when editing read-only files

**URL:** https://community.mp3tag.de/t/no-warning-given-when-editing-read-only-files/54812
**Category:** Fixed Bugs
**Tags:** bug-fixed
**Created:** [October 19, 2021, 6:38pm UTC](https://community.mp3tag.de/t/no-warning-given-when-editing-read-only-files/54812 "2021-10-19T18:38:45Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![ryerman](https://community.mp3tag.de/user_avatar/community.mp3tag.de/ryerman/32/5285_2.png) [@ryerman](https://community.mp3tag.de/u/ryerman)
#### Post date: [October 19, 2021, 6:38pm UTC](https://community.mp3tag.de/t/no-warning-given-when-editing-read-only-files/54812/1 "2021-10-19T18:38:45Z")

</div>

Until at least v3.05, Mp3tag showed a warning when editing a read-only file.  
Merely renaming a file was done without warning.  
I believe that was the intended behaviour.  
FWIW, Windows File Explorer does not allow metadata to be edited for read-only files.

But v3.05b, and later versions, do not warn when editing a read-only file.  
Instead, the read-only attribute is removed and the metadata is up-dated without warning.  
I can't see anything in the change logs to indicate that is a new intended behaviour.

If it is not a bug, I think the pre v3.05 behaviour should be reinstated.  
There should be a warning when trying to edit a read-only file.  
I suppose the warning could be optional.

> [@Readonly files are overwritten without notifying the user](https://community.mp3tag.de/t/readonly-files-are-overwritten-without-notifying-the-user/54768):
>
> Scenario: Create a directory which contains one readonly mp3 file. Start Mp3tag. Paste the full path of the directory to the field "Verzeichnis" and hit Enter. Right-click the mp3 file and select "Tag entfernen". Result: The file content is changed (tag is removed), the readonly attribute is removed. Expected result: Readonly files should not be simply changed without notifying the user. The intention of a readonly flag is to prevent an application from changing the file content. All other…

---

<div class="post-metadata">

### Author: ![Florian](https://community.mp3tag.de/user_avatar/community.mp3tag.de/florian/32/5759_2.png) [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [October 21, 2021, 6:41pm UTC](https://community.mp3tag.de/t/no-warning-given-when-editing-read-only-files/54812/2 "2021-10-21T18:41:29Z")

</div>

Thanks for reporting the issue!

It's a regression from the massive rewrite caused by [this bugfix](https://community.mp3tag.de/t/48411) and I'll try to bring back proper handling of read-only files soon.

---

<div class="post-metadata">

### Author: ![Florian](https://community.mp3tag.de/user_avatar/community.mp3tag.de/florian/32/5759_2.png) [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [October 23, 2021, 5:14pm UTC](https://community.mp3tag.de/t/no-warning-given-when-editing-read-only-files/54812/3 "2021-10-23T17:14:25Z")

</div>

This should be fixed with [Mp3tag v3.10c](https://community.mp3tag.de/t/455).

---

<div class="post-metadata">

### Author: ![system](https://community.mp3tag.de/uploads/default/original/2X/c/ce7035d426cb755a7916793326d23b465222a407.png) [@system](https://community.mp3tag.de/u/system)
#### Post date: [November 22, 2021, 5:15pm UTC](https://community.mp3tag.de/t/no-warning-given-when-editing-read-only-files/54812/4 "2021-11-22T17:15:12Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
