Michel Mendiola

As with many other issues, this one was originally tagged for Final back when there wasn't an RC4 label created yet. I could argue that since there is little support...

This is similart to the other issues with sending notifications in whatever language the person who sent the notification was using. In this case, the error gets logged using the...

I agree, not doable for RC3, perhaps not even for final since it isn't a stopper in any way. Annoying? sure but not a stopper. Would be tempted to mark...

Along side a backend fix I would also like to add a frontend fix. Perhaps a checkSubmitOnce() call and disable the button via JS on first click.

I would prefer to add a scheduled task to handle this scenarios. I personally wouldn't run any query directly on the upgrade process. Check and detect, yes and If something...

The check is already there, so are the txt strings that can be modified to inform the user. The only thing left is building the scheduled task.

Does the upgrade process gets interrupted if duplicates are found? I still don't think the admin should be doing this during the upgrade, it is already convulsive enough to add...

The idea is fine. I want to know if duplicate ids are a problem doing the upgrade or if they prevent it, if not, this process can be moved to...

Cool, this is what I wanted to know. Now, how about do the check, if there are duplicates store the result somewhere in a modSettings value then add an admin...

There is none. A new interface will have to be added, if you could add it great if not we can do it but it will have low priority.