This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
addons:bridge:vbulletin [2009/09/28 23:36] jonyo Added known issue section, removed legacy section. |
addons:bridge:vbulletin [2015/01/13 23:27] (current) geomatt |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== VBulletin Bridge ====== | ====== VBulletin Bridge ====== | ||
| - | This //bridge type// | + | This //bridge type// |
| ====== Steps inside vBulletin Admin ====== | ====== Steps inside vBulletin Admin ====== | ||
| - | Since this bridge is // | + | Since this bridge is // |
| - | The solution to this, is to disable user registrations, | + | The solution to this, is to disable user registrations, |
| - | <tip c n> | + | <tip c n> |
| + | |||
| + | Also note that the current bridge has been tested on newer vBulletin versions, and is known to work on **4.0** versions, including the newer vBulletin CMS. If you do experience any problems with a newer released version of vBulletin, please contact support. | ||
| ===== Disable Registrations ===== | ===== Disable Registrations ===== | ||
| Line 80: | Line 82: | ||
| The following are things to note with the vBulletin bridge functionality. | The following are things to note with the vBulletin bridge functionality. | ||
| + | - If you see an error to the effect of " | ||
| - There is currently no way to modify Vbulletin profile information settings | - There is currently no way to modify Vbulletin profile information settings | ||
| through the bridge or current Geodesic Solutions installations. < | through the bridge or current Geodesic Solutions installations. < | ||
| Line 88: | Line 91: | ||
| - Only the Geodesic Solutions installation lost password facility can be used. < | - Only the Geodesic Solutions installation lost password facility can be used. < | ||
| - The username for a user cannot be changed within Geodesic Solutions installations and recommend that you not allow this in any other installations. | - The username for a user cannot be changed within Geodesic Solutions installations and recommend that you not allow this in any other installations. | ||
| - | - User removal in Geodesic software will not remove the user in vBulletin, this is a usability | + | - User removal in Geodesic software will not remove the user in vBulletin |
| - | - If the registration, | + | - If the "registration", " |
| - When a user is registered (or user info changes), if there is already a matching username OR e-mail in vBulletin, that user **cannot be created or synced** in vBulletin. < | - When a user is registered (or user info changes), if there is already a matching username OR e-mail in vBulletin, that user **cannot be created or synced** in vBulletin. < | ||
| - If the password in Geo software and vBulletin get //out of sync//, **changes will not be synced for that user** as a security precaution, if the user pass doesn' | - If the password in Geo software and vBulletin get //out of sync//, **changes will not be synced for that user** as a security precaution, if the user pass doesn' | ||
| + | ====== Important Configuration for vBulletin 4.2.x ====== | ||
| + | |||
| + | If using vBulletin version 4.2 (confirmed on 4.2.1 and 4.2.2 (all patch levels) as of this writing), you must make a small change to the vBulletin PHP code in order for the bridge to work correctly. If you need assistance making this change, open a Support Ticket with us. | ||
| + | |||
| + | Open the file **includes/ | ||
| + | |||
| + | <code php> | ||
| + | /* Navbar stuff | ||
| + | Dont use DIR here, the Dev scripts dont like it */ | ||
| + | require_once(' | ||
| + | </ | ||
| + | |||
| + | Replace the above code with this: | ||
| + | |||
| + | <code php> | ||
| + | /* Navbar stuff | ||
| + | Dont use DIR here, the Dev scripts dont like it */ | ||
| + | //GEO EDIT: add DIR here, so that it works with the bridge | ||
| + | require_once(DIR.'/ | ||
| + | </ | ||
| + | |||
| + | and then save the file. This corrects a file include path that cannot otherwise be accounted for from the GeoCore side of things, and will allow the bridge to function normally. | ||