I had to do this once and it was a pain but I got it working. Here's what I did:
I hijacked all of the vBulletin membership features and redirected them to a cake based alternative. So things like login, registration, editing profile etc in vBulletin were all redirected to a cake equivalent. In your cake login code, you have to set the appropriate cookies for vBulletin. Probably the easiest way to do this is to clear your cookies, login to vBulletin and see what cookies are set. This part is tough and takes a lot of experimentation because vBulletin has a very specific way that it creates the hash for session ids. Maybe you can write your own but I basically copied the hashing functions from VB into my cake login code. After you figure out the correct cookie data you also have to add a record into to the vBulletin sessions table as well. I ended up using the vBulletin users table as my main users table. So when a user would register via cake, the user info would actually populate the vBulletin users table. This way I didn't have to manage two separate user tables. Logging out is pretty easy. Clear the vBulletin cookies you created and remove the record from the vBulletin sessions table for that session id. It sounds a bit simpler than it really is. This all took me a while to get right but it is possible. Just a lot of blood, sweat and tears went into the whole process : ) I wish I could send you some code but I don't have access to that site anymore. Good luck, its going to be a pain in the ass but its def do- able. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
