Issues for formspree/formspree


  • correct JavaScript capitalization

    Changes proposed in this pull request:

    correct JavaScript capitalisation


  • React users dashboard

    Fixes # . In order for people inside of china to use formspree, I suggest updating the fallowing two changes. Currently, using the domain www.google.com can't access inside of china Changes proposed in this pull request:

    Have you made sure to add:

    Screenshots and GIFs

    [Insert screenshot or GIFs of old and new behavior]

    Deploy notes

    [Put any changes necessary in order to deploy (such as DB migrations)]

    Any Additional Information


  • Minor changes

    Changes proposed in this pull request:

    Have you made sure to add:

    Any Additional Information Not sure if I've gotten all the email templates, but I believe I have?


  • Session tokens

    Pre-emptive step to disabling user accounts

    Changes proposed in this pull request:

    Have you made sure to add:

    Screenshots and GIFs

    Deploy notes Need to run a DB migration upon deployment. This PR is for adding the columns necessary for session tokens. It will create a session token for all new users moving forward. We will need to manually apply a DB migration that will create session tokens for all existing users and then change the user loader to use the session token.

    Any Additional Information Going forward, these migrations will be used to disable malicious users and implement security features to force the logout of a single user.


  • Rewrote japanese translation into intuitive and user-friendly expression

    Changes proposed in this pull request:


  • Treat URLs ending with .html and slashes or starting with www. as indistiguishable.

    For all newly registered forms, remove starting 'www.', ending slashes and ending '.html' or '.htm'.

    Then, for all forms, try to fetch not only the url that comes in the Referer (after referrer_to_path), but also its same version without 'www.', without '.html' or '.htm' and without the ending slash.

    All existing forms will match as always. all new forms will be cleaned up and match against their cleaned version, it doesn't matter if their url change to add or remove 'www.', '.html' or '/' later.


  • keep documentation in sync

    keep documentation in sync


  • show an error page on 500.

    For a long time we've had a "500.html" template that seated uselessly in the codebase. Not anymore!

    Changes proposed in this pull request:

    Have you made sure to add:

    Screenshots and GIFs

    screenshot-error