I can't confirm this for certain, but I suspect my attempt to upgrade my WSN Links install to latest version has messed with my VBulletin 3.5.3 intallation.
Problem: VBulletin users can no longer access their custom PM folders (users can create new folders in which to store private messages). This error coincided with my upgrade of WSN Links.
The upgrade added a whole slew of things to my VBulletin user table:
I don't see signature listed in your list, but I've seen the signature field cause a problem before because vB has a field in another table it uses with the same name. Haven't seen that with recent versions of vB though, that was back around 2.3.0 or so that field caused a problem on my site.
Is there a file/list where I can see every change specifically, every mysql command, that the WSN install/upgrade performed on my VBulletin tables? That would help a lot.
Figured it out. The field "pmfolders" added to the VBulletin "user" table breaks the VBulletin 3.5 PM system, FYI. Probably for the same reason that you mentioned above - the user[pmfolders] var is used by VB php script, probably grabbed the info from the WSN user field.
Still though as I continue to 'clean house' the specific DB changes would help. Thanks.
Okay, adding a $newpmfolders = 'wsnpmfolders'; line to the integration file should make them use different fields... might have to manually create wsnpmfolders.
The changes are that any fields in wsnlinks_members that aren't in user are added to user.
0/5
1
2
3
4
5
This thread is closed, so you cannot post a reply.
Comments on VBulletin broken
Usergroup: Customer
Joined: May 18, 2004
Total Topics: 3
Total Comments: 10
I can't confirm this for certain, but I suspect my attempt to upgrade my WSN Links install to latest version has messed with my VBulletin 3.5.3 intallation.
Problem: VBulletin users can no longer access their custom PM folders (users can create new folders in which to store private messages). This error coincided with my upgrade of WSN Links.
The upgrade added a whole slew of things to my VBulletin user table:
(Adding member fields: timezone rating pmfolders notifyofpms acceptpms cookieduration banned location homepage occupation bio aim icq msn yahoo inactive timeonline totalpms buddies ignored isonline acceptims adminpermissions referrer groupreverttime grouprevertto moderationpm secondarygroups linksperpage commentsperpage shouts customtitle shoutban topicbans forumbans visibility birthdate lastsession interests posteditor forumaccess pmpopup pmnotify modnotes guestnotes salt lastmodnote newpms imflag orderalbums lastguestnote autosubscribe notifymethod showavatars showsigs warninglevel topics posts chatcolor)
And what else it did I don't know. But my VBulletin is broken and I'm getting a strong sense it was related to my links upgrade.
Usergroup: Customer
Joined: May 18, 2004
Total Topics: 3
Total Comments: 10
Is there an uninstall script for WSN? Or an easy way to clean out my VBulletin User table?
developer
Usergroup: Administrator
Joined: Dec 20, 2001
Location: Diamond Springs, California
Total Topics: 61
Total Comments: 7868
I don't see signature listed in your list, but I've seen the signature field cause a problem before because vB has a field in another table it uses with the same name. Haven't seen that with recent versions of vB though, that was back around 2.3.0 or so that field caused a problem on my site.
Fields can be deleted with phpmyadmin.
Usergroup: Customer
Joined: May 18, 2004
Total Topics: 3
Total Comments: 10
Is there a file/list where I can see every change specifically, every mysql command, that the WSN install/upgrade performed on my VBulletin tables? That would help a lot.
Usergroup: Customer
Joined: May 18, 2004
Total Topics: 3
Total Comments: 10
Also, is the "user" table the only one modified, or are there others? Thanks.
Usergroup: Customer
Joined: May 18, 2004
Total Topics: 3
Total Comments: 10
Paul,
Figured it out. The field "pmfolders" added to the VBulletin "user" table breaks the VBulletin 3.5 PM system, FYI. Probably for the same reason that you mentioned above - the user[pmfolders] var is used by VB php script, probably grabbed the info from the WSN user field.
Still though as I continue to 'clean house' the specific DB changes would help. Thanks.
developer
Usergroup: Administrator
Joined: Dec 20, 2001
Location: Diamond Springs, California
Total Topics: 61
Total Comments: 7868
Okay, adding a
$newpmfolders = 'wsnpmfolders';
line to the integration file should make them use different fields... might have to manually create wsnpmfolders.
The changes are that any fields in wsnlinks_members that aren't in user are added to user.