VersaPay
Member
The title pretty much says it.
Mapping a purchaser email address to a developer email address makes the assumption that the person paying for a website is the person developing a website.
As web developers you should know this is rarely true.
One simple usability issue that took my from happy customer to angry customer in less than five minutes.
Not sure what you're talking about here. If you purchased the plugin, the only email we have to send information to and to authenticate against in the forums is the email address used to make the purchase. We're not making any assumptions.
If you want to share your login information with your developer, be our guest. That's totally up to you.
VersaPay
Member
Let me clarify since I'm pretty sure this is a common issue.
My boss bought the plug-in for me to configure on our corporate website. I went to create a support account to look at the documentation. I used my personal email to create an account and verified that address to activate the account. I should now be able to add my key to that account. Instead, you have linked the product key to the email address of the person who made the purchase. This assumes that the person buying the product is the same person who will need support for that product.
So what did I do? I just changed the email in my profile to my boss's address. Since you don't verify email address changes I've essentially -stolen- support from the person who bought the product.
This is why you don't link product keys to email addresses. This whole system would be a lot simpler and much more secure if you added your support key when you create an account.
I'm sure we'll make changes to our sales/authentication process in the future, but for now this is working fine and hasn't been an issue for the majority of any of our users.
As far as stealing support, if your bosses email address already existed in the system, it wouldn't have allowed you to use that. Sorry if it inconvenienced you, but for now that's the way the process works.
