hello!
I'm currently running a very old version of LinkSQL and am upgarding to version 2.2.0.
With the old version I've been using the password mod (remember that one!?), where each link has a password associated with it, and users just need to enter the link id and link password to make modifications to the link information.
What I want to do now is move everything over the new user based system, and here's where I need some advice. I don't have all the information required to fill the fields so I'm having to do some jiggling around.
This is my situation...
- the links are not currently owned by users
- every link has a 'contact email' and contact name
- a number of links have the same contact email
- all links have different passwords (some may be the same, but dif. link id)
Possible Solution:
- contact email becomes the users username
- all links with contact name = username become owned by the user
- a new random password is generated for every user
- all users are emailed with new login details
I think this is the best way to go about it - can anyone suggest a better alternative?
r
I'm currently running a very old version of LinkSQL and am upgarding to version 2.2.0.
With the old version I've been using the password mod (remember that one!?), where each link has a password associated with it, and users just need to enter the link id and link password to make modifications to the link information.
What I want to do now is move everything over the new user based system, and here's where I need some advice. I don't have all the information required to fill the fields so I'm having to do some jiggling around.
This is my situation...
- the links are not currently owned by users
- every link has a 'contact email' and contact name
- a number of links have the same contact email
- all links have different passwords (some may be the same, but dif. link id)
Possible Solution:
- contact email becomes the users username
- all links with contact name = username become owned by the user
- a new random password is generated for every user
- all users are emailed with new login details
I think this is the best way to go about it - can anyone suggest a better alternative?
r