Forum Moderators: coopster

Message Too Old, No Replies

Custom script to be integrated with Vbulletin

how to handle user registrations?

         

walkman

9:19 pm on May 17, 2007 (gmt 0)



I am having a standalone custom script done where users will be able to post youtube vids etc. It will be a small part of the site and integrated with Vbulletin when it comes to users.

Now, how to best handle it? Redirect the registration to Vb and let vb handle it or insert into vb database directly--after checking for dupes? By letting VB handle it, I need to figure out a way to redirect them to the video page and think of the gazillions of VB upgrades over the years.

Any suggestions? The prgrammer is great so he can do pretty much anything. I need a solution that saves me time and headaches in the long run--in addition to be being very user friendly of course.

henry0

9:44 pm on May 17, 2007 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



I have done something similar but with an E-Comm registration
My first trial was out of laziness to create another table and import from the
E-comm’s customer-table the user details.

But I found that it was making more sense to modify the User E-comm reg and table then in my case I added more links (to my other applications) from the user E-comm management area.

My experience with updates (not the V bulletin) is that registration area is very seldom updated
Just keep a precise manual/how-to

This is always the same problem when integrating your scripts/application with a wellknown BB or other.

Last the scary part:
What will you do if the upgrades are such that you would not be able to make them both communicate?
So maybe the independent less integrated solution is in the long run more doable?

walkman

10:09 pm on May 17, 2007 (gmt 0)



Henry,
thanks for the reply. The thing is that VB has every incentive to make their system compatible with as many scripts as possible. While what you said could happen, it is very unlikely. Even if my programmer disappears, my thinking is that I can find someone else to change a table or two. If not, screw it. I'll start from scratch, bad things do happen and no one can prepare for everything.

The scripts are standalone, other than the users of course. It makes no sense having to sign up 10 different times on my site, so every application will be based on VB's login (most of the programs installed were off the shelf scripts)