ACTIONS that mimics a WYSIWYG to Change File Extension or File Name and Extension (2022-2023)

[wneclass2018]

@ohrenkino

way - it is not: if I enter e.g. mP3 as new file extension, the extension becomes lower case.
Why doesn't the action create the fields it needs when all it does is to convert to lower case only any way?
Where is the benefit that I have to create user-definded fields first, then apply the action, then delete these fields again?
While a simple "Replace with regular expression" would serve the same purpose much quicker, see

WYSIWYG only applies to the first 2 actions. It doesn't apply to the "CONVERT File Extension (%_extension%) to Lowercase by wneclass2018 (February 20th 2023).mta" since that .mta file was created convert uppercase extensions to lowercase.
If you truly want a WYSIWYG with no restrictions (i.e. can add spaces as a extension), then you can use this string, without quotations, "%preserve_original_filename%.$if2(%NEW_FILE_EXTENSION%,%preserve_original_extension%)". Likewise, on a different mp3tag community forum, I explained it more in detail here: Not possible to change filename w/ extension via file view - #6 by wneclass2018