Issue#116

The codefix to implement the button with the right functionalities , has been extensively tested :

• the copiable token field works ( with the ", :readonly => true" , option in the f.field markup ).
• the refresh of the page doesn't regenerate the token , displays only the token that is actually in the database .
• the form submits flawlessly as it used to and the new token generated at a click of the button and puts it in the database ( when coming back to the form page
  the new token is clearly displayed )
• clicking on the regenerate token button doesn't put the new token in the base , only the submit button does it , so if you click "regenerate token" you'll see the possible new token , but if you refresh the page , the token turns back to what is in the database .... So you can click and click the regenerate button again and again until you find the one that suits you without fear of it beeing entered into the base prematurely .
• route.rb isn't affected at all