As previously announced via banners and our newsletters, support is no longer available through this platform.
For easier navigation, you can still click on "Submit a Ticket" here, choose the appropriate category, and you'll be redirected to the correct support channel for your plugin.
You can still access your previous tickets and browse public tickets, but please note that responding to tickets is no longer possible.
Paid customers: Please log in to your store account for support.
Pre-purchase questions: Use the support widget in the bottom-right corner of our websites:
https://wpamelia.com
https://wpdatatables.com
https://wpreportbuilder.com
We have many events for on our site, and some of our users that are signing up for additional events are getting messages when registering for a new event a few days later. Like this message "email already exists". In a few cases the user accidentally put a space at the end of the first field. Why doesn't Amelia ignore these spaces like other sign in forms like other online forms?
Is there a way for Amelia to ignore any spaces at the end of their entries?
There are other users that are just having issues registering for an event with that same message "email exists"
There have been about six users total trying to reserve space in an event, and have had trouble. Can you please let me know how to resolve this issue, either from your experience or some possible solutions?
Hello Dean Sauls,
Apologies for replying a bit later, we don't work on weekends.
You should disable the option Check customer's name for existing email when booking in Amelia -> Settings -> Roles settings -> Customer, and the form won't check if the name is the same as the one used before for that email address. When this option is enabled it is checking if the name is the same - but everything needs to be completely the same as the first time they booked - so if they used big/small letters, if maybe some space is added by mistake, etc.
Regarding the space at the end of the name/string , I will add that to our feature requests list, so it could be considered for implementation if possible in the future.
If you have any other questions or concerns feel free to open a new ticket and we will gladly help out.