Major Problem

Forum
Last Post
Threads / Messages

RoconzaArt

Member
Member
Joined
Jan 9, 2011
Messages
479
Points
0
Location
NJ Shore (and proud of it)
Mysidian Dollar
25,728
email verification is really need in the nest release.

Let me explain after signing up I noticed that not only can you sign up with a fake e-mail but with the same e-mail too. In fact there is no stopping a user from signing up a bunch of times and getting countless amounts of rare adoptables and trading them to there main account for common adoptable.

I went and tried this on my site and found I could sign up countless amounts and trade pets that normally had restrictions such as

"The user does not have more than of this type of adoptable"

More over I could trade then adopt then trade and start the whole process again.

BUT wait that not all! I can adopt and abandon and then adopt again and recover my abandoned adoptable and countless amounts of restricted adoptable.s

Not only can users sign up countless times and send them selves rare adopts but they can use other major faults in the adopt process!

I think theses problems should be looked at before any scripts in the next release. This is a major problem for owner who want to stop mass cheating on a wide scale.
 
Last edited:
There is no email adress verification check, your right. Although checking for multiple emails would be an easy fix. Actually, writing a code to send an email out with the users 'code' they randomly get and then require them to enter it should really not be a problem. We'll definitely look at this before the version 1.2.- release. Thanks for pointing this out.
 
Ditto to what Kaeliah said. We will discuss this issue in details in dev staff forum, but we cannot guarantee that it will be available for version 1.2.0. However, it may appear in either later v1.2.x series or v1.3.0 release.
 
Lol I told you. =P

I tell you what reconza, after I finish uploading the forum script, I'll make a tutorial on how to make the email verification, so you can have it on your board before the next release.
 
Huh. In my complete rewrite of the script I think I did actually add email verification. It's easy enough to add, so I don't see why it shouldn't be introduced in v1.2.x.
 
Huh. In my complete rewrite of the script I think I did actually add email verification. It's easy enough to add, so I don't see why it shouldn't be introduced in v1.2.x.

There is email verification, it verifies that what you typed in is actually an email.

i.e. wordhere@wordhere.com

It however does not check the database to see if there is a user already using that email, or check to see if the email is correct.
I've already added this to my old script when I was making modifications almost everyday.
 
There is email verification, it verifies that what you typed in is actually an email.

i.e. wordhere@wordhere.com

It however does not check the database to see if there is a user already using that email, or check to see if the email is correct.
I've already added this to my old script when I was making modifications almost everyday.

What I mean is when you get sent a verification link to your email account and can't loggin until you click that link to comfirm your email account it real.
 

The information will need to be changed but yeah, that can be added (its similiar to what I am assuming for the forum).

What I mean is when you get sent a verification link to your email account and can't loggin until you click that link to comfirm your email account it real.

Oh, yeah that can be done too. But eliminating the ability for fake emails will help with that.
 
That's what I meant, Bloodrun. My script basically sent out an email to the email given, then added a row to a verification database which was basically only id, user, and code. Then when they clicked on the link in the email, it changed the user's account to normal user (as opposed to unactivated) and removed the row from the DB.
 
That's what I meant, Bloodrun. My script basically sent out an email to the email given, then added a row to a verification database which was basically only id, user, and code. Then when they clicked on the link in the email, it changed the user's account to normal user (as opposed to unactivated) and removed the row from the DB.

Oh, my apologies for not understanding correctly.
 

Similar threads

Users who are viewing this thread

  • Forum Contains New Posts
  • Forum Contains No New Posts

Forum statistics

Threads
4,280
Messages
33,130
Members
1,603
Latest member
Monako
BETA

Latest Threads

Top