You cannot apply the fix and try again, you have to revert to the prior database backup, apply the fix and try again.
As this sort of bug is pretty unexpected at this stage of the game I would imagine that people find this thread after the damage has been been done.
So while its fine to sit on your high horse (as I usually do) and say, "ok just use the backup you did prior to installing the language" I think it also would be a good thing to offer an sql repair patch to put things back as they were prior to the faulty insert, if that is possible, for those that did not have a recent backup,
or, probably easier, a patch to set the new language id everywhere to what it should be.
Remember, for many people the additional language is not additional, its default and essential and this bug is a real show stopper.
Bookmarks