[MPDev]

The issues are not a PhotoPost issue - its how your setup is configured that is the issue. Cookies are picky - if PhotoPost can read its own cookie and vB can't, then it wont work. Same in reverse - thats not a PhotoPost limitation, it's a cookie limitation.

If you aren't using the right License Number, then the encryption won't match vB3 and subsequent verifications won't work either - again, not a PhotoPost issues. vB3 added the License Number to the password hash - if you don't enter the right number, then the encrypted password is saved wrong and PhotoPost cannot verify the id.

As developers there is only so much we can do, for integrations like this its up to you to do some basic checking and configuring.

1) In the header of your vB index.php file is a comment section that looks like this:

/*======================================================================*\
|| #################################################################### ||
|| # vBulletin 3.0.0 - Licence Number 99999999
|| # ---------------------------------------------------------------- # ||
|| # Copyright ?2000?2004 Jelsoft Enterprises Ltd. All Rights Reserved. ||
|| # This file may not be redistributed in whole or significant part. # ||
|| # ---------------- VBULLETIN IS NOT FREE SOFTWARE ---------------- # ||
|| # http://www.vbulletin.com | http://www.vbulletin.com/license.html # ||
|| #################################################################### ||
\*======================================================================*/

This is where you can verify your license number that PhotoPost needs to encrypt the password. Enter the number that is in your file in bold into the config-inc.php.

2) Cookie Paths. Check your vB cookie settings, if you run vB in a directory like /forums and PhotoPost in a directory like /photopost; then you need to configure both applications to make the cookies available to both applications. You do this by setting the cookie path to "/" in both applications.

3) Cookie domains. If you have both applications on the same domain (like www.yoursite.com), then you can set this to blank "". If you run forums.yoursite.com and photos.yoursite.com, then you need to set this to ".yoursite.com" so that the cookies can be read across domains.

4) Cookie prefix. vB3 uses a default cookie prefix of "bb"; if you specify a different prefix, then you need to tell us whats different about it.

If you need to check why your system isn't working, I suggest referencing your Cookie Manager (if you use Mozilla, IE sucks). Logout from both PP and vB3. Login to PP and check what cookies are created, the values and the paths. Logout. Login to vB3, check those again. 99% of the issues can easily be traced in this manner as you will often find the paths not set properly or the prefixes.

If the password hashes don't match, then the issue is of your license number. 8 out of 10 integration issues are people using the wrong License Number. I'm considering writing a script to parse the license number out (or try to), but checking your index.php file is the easiest way.

Keep in mind, once the integration works you still need to modify your navbar and footer paths. vB3 uses relational paths and if you are using the navbar header in PhotoPost, then the header needs to know where to find the vB3 files.

I am more than happy to help you get your setups working properly, but there is no need to be rude. We have a competent and professional staff at PhotoPost.Com who monitor the forums 7 days a week and provide an extensive FAQ and conversion script to help people along the way. It isn't 100% automatic as you might like, but we do try our best to make it as easy as possible.

If, after you've done all this, and you still want my help - PM me your URL and a login id to test. I will check out the values myself and offer any suggestions that I can identify.