WDX: ContentSetValue on read-only files

[tbeu]

Is it by design or a bug that the read-only flag of files is removed before [face=courier]ContentSetValue(W)[/face] of content plugins is called and reset after return? I consider this behaviour as kind of dangerous as TC or its content plugins must not change read-only files without asking.

[MVV]

I agree that TC shouldn't remove read-only attribute.

[ghisler(Author)]

This behaviour is by design and will not be changed. It's done because setting plugin attributes and the time stamp fails with read only files.

[tbeu]

I would agree with the time stamp, however I disagree with plugin attributes changed by content plugins. Why does not TC ask if the read-only flag should be removed or kept unchanged? Why does not TC let it upt to the content plugin to decide what to do with read-only files. Most content plugins should deal with the case of read-only files.