Feature Idea: Override Empty Values

[michael-e]

If values are set in the POST array but empty, the extension will not override them (which is the right behaviour, of course). It would be cool to have an option for this, in addition to the Value will override any value posted from the frontend option. It might be called Value will override empty value posted from the frontend or similar.

[brendo]

Yeah, that'd be pretty neat, so you could always provide a default even if the frontend tried to clear the value. Could be useful for security too.

[DavidOliver]

If values are set in the POST array but empty, the extension will not override them (which is the right behaviour, of course).

Maybe a silly question, but why is this the right behaviour?

Currently, a malicious user can remove an entry's field's data if they know/guess the field name and include an empty value with the POST?

[michael-e]

Yes, basically it is the right behaviour. The extension is called "Default Event Values", so it is supposed to provide default values that are used if nothing is posted.

The option "Value will override any value posted from the frontend" can be used to make the default value override the posted value.

My suggestion means something in between: Override empty values, but don't override non-empty values. There are rare use cases for this (but I don't remember mine, unfortunately).

[DavidOliver]

My suggestion means something in between

I see. So the current 'Value will override any value posted from the frontend' option can already be used to override empty values? Thanks.

[michael-e]

Yes, as it says: override any value. :-)

[DavidOliver]

Good good! The first sentence of this issue threw me.

[michael-e]

:-) (Speak: Yes, it was misleading.)