Modification of coin bug [solved]

Hello,

When sending a request to modify a coin, if the requestor is fast enough to add the info they want to add or modify and races to hit the submit button and the coin page hasnt had a chance to load up all the info of the coin, the request will go forward and might add extra elements to be updated as null, causing unwanted modification requests.

This has happened to me many times now, especially with the Composition and Metal fields. For instance, I am trying to update a ruling authority and when I hit the submit button it sends this petition:

Field|Given value
Ruling authority|Frederick II
Composition|Single material
Material: billon

"Composition|Single material" and "Material: billon" being the original info in the coin but my update request it is asking to actually erase that data (since it was NULL in the form at the time of hitting the submit button).

Hello,
Sorry I didn't fully get your point. Could you please provide a link to the request you gave as example? For that request, do you confirm that your intention was: 1. add the ruling authority; and 2. remove the composition? If so, could you please also clarify how you removed the composition in the form: did you set "Composition" to "Unknown" or "Material" to "Unknown" or both?

Hi Xavier,

My intention, and only update was, to set the ruler to the coin. But if you move too fast and click the Modify data button before the webpage actually loads everything, the update request can include unwanted requests for info deletion.

Examples:
https://en.numista.com/catalogue/contributions/voir_demande.php?id=3547750
https://en.numista.com/catalogue/contributions/voir_demande.php?id=3548583
https://en.numista.com/catalogue/contributions/voir_demande.php?id=3547162

Thank you for the details. There was an issue with how some billon coins were registered, leading to some "ghost modification" of the composition. This is fixed.