Thats really overkill for such an edge case issue. Not worth the effort in
my opinion. But if you have the code to cotnribute then great it can be
reviewed

On 20 September 2016 at 11:29, Wilko Rietveld notifications@github.com
wrote:

Expected result

If you use language overwrite for instant incase of a Quick Fix you would
like to remove it as soon as an update is available the only way to test
this
Actual result

at this moment you can only delete an overwrite. Meaning (in case of a not
fix)you have to rewrite the overrwite.
Additional comments

Publish / Unpublish would be a quick way to test your overwrites with
current ine files.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#12098, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABPH8XutxNb0ljZO0C2FSfSkjNQEV7pzks5qr5mAgaJpZM4KBWug
.

Brian Teeman
Co-founder Joomla! and OpenSourceMatters Inc.
http://brian.teeman.net/

That actually is harder to do than it may look.
Because the overrides are not stored in the database. They are stored in a textfile. You see the name of the file when you create/edit the override.
However for testing purposes, you edit the override and just rename the key. Like if your key is named COM_FOO_BAR just rename it to COM_FOO_BAR_TEST and save. Then you see if the fix is applied or not. If not, just rename the key back.

Closed - it can always be re-opened with a code pull request