To address the first question of how to relate them together:
Ok...my mind tends to work a little different, so feel free to correct me if i am wrong here (i am not a programmer, just a self taught webmistress who dabbles in picking up new stuff)....anyway, here is what i was thinking:
Add a field into the user data table to hold the subscription username value for that userid.
Upon signing up, the member is directed to a URL you determine in the verotel's site CP....preferably a private .htaccessed directory. In that directory, make the index.php a script which will ask them for 4 things: Their board username and password (although it would be great if it would auto-detect the ones who have cookies enabled), and their payment username and password (sent to them by verotel).
That script would confirm against the data file the verotelrum.pl script has already added them into, and in the case of the username/password matching, the system would add V-paymentID# into the paymentID field in their userdata....and upgrade them to the proper usergroup. In the event of a mismatch, it would simply give them a wrong password error.
On the removal of an account, it would simply search the userbase for the payment code from the field, and upon finding it, would delete the usercode, and move them back into the registered usergroup.
Don't know if any of this makes sense to anyone but me though.
Perl DBI?? i THINK so.....but honestly am not positive. This is, however a colocated server..and since i own it, i can add pretty much anything i need to.
|