Database not updating properly after upgrade

[kevinsdh]

After I recently upgraded my pp to the latest version 4.8.2 from an old 3.1.1. Everything but the cookies worked. And I tried for many hours to get the cookies to work with a newly updated vbulletin. 2.2.8 to 3.0.2. I did the whole nine yards - in this thread :
vB3 Integration FAQ and still no go. The cookies would not work - to my frustration. I tried every possible combination of the variables and was stumped.

So, finally I got into phpmyadmin and started looking around - amazingly, the table - "settings" was incorrect. why it did not update is beyond me. But I had to change two things and now it looks like the cookies are working.

#1 - Since I changed the vbulletin to a different database (and the pp update program didn't reflect this) even though I think it is supposed to in the 2 php files indicated in this post:
renamed mysql database during vb upgrade and have config question
I manually changed the URL in line 7 of the pp "settings" table. This now pointed to the correct vbulletin URL.

#2 - For some reason during the upgrade - this "settings" table did not update the "User Registrqation Settings" on line 41. I changed it from vb2 to vb3.


I don't know if this normal and would like a pp support team member to comment on this. And advise if this is a fix - don't change anything until a support member verifies this is acceptable practice. But if this is happening to someone else as it was me, you might just have a look see at your settings table. This may be a troubleshooting step that helps in getting your cookies working.

Cheers!

[Chuck S]

Reading your response I do not know whether you have solved your issue or just speaking out loud on your troubles understanding what needs to be done. I think the thread we post called VB3 Integration FAQ which you linked is pretty thorough in the steps converting from VB2 to VB3

1. Of course if you change database and url's info you need to edit the config file and the database to reflect the changes. Most people though do not change databases and url when upgrading VB. They simply follow the VB upgrade instructions and delete VB2 files off the server forum directly and replace with VB3 per the upgrade docs for VB

2. Same thing here if you change forum types you need to edit the forum type you integrate with in Photopost.

As far as cookies its pretty straight forward. As long as everything match's between the programs in relation to domain name path and prefix cookies are fine.

Their is one more step in VB3 cookies where alot of customers mess up and that is the VB License. Alot of customers mistake their customer number for VB as their license number.

[kevinsdh]

as I stated, I followed the instructions in the sections you mentioned exactly to the tee. I did the settings thing in several different possible configurations and even the little utility for the vb2 to vb3 upgrade. That is why I provided those links in my post. I also changed the ...inc files as advised and still had to manually change a few settings in the database "settings" - for some reason.


Just sharing my challanges on getting everything operating. I think this is a great program, if someone is unable to update, they might just want to check these settings.

[Chuck S]

Well the reason I commented is everything except you changing your database information and forum url when you upgraded is indeed covered in the integration facts thread you posted a link to.

The extra steps of changing forum url's and database access info when upgrading is not even recommended by VB upgrade docs let alone us. I think personally you made it tougher on yourself doing these unneeded steps in your forum upgrade/photopost upgrade process

As well just sharing my take on this matter as I see it.