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 21:47] jonyo |
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 ===== | ||
| Follow the steps below to disable user registrations. | Follow the steps below to disable user registrations. | ||
| - | - Within the VBulletin admin, go to **vBulletin Options > vBulletin Options**, and select **User Registration Options**. < | + | - Within the VBulletin admin, go to **vBulletin Options > vBulletin Options**, and select **User Registration Options**. < |
| - For the setting **Allow New User Registrations** select **no**. < | - For the setting **Allow New User Registrations** select **no**. < | ||
| - In the admin, go to **Languages & Phrases > Search in Phrases**. < | - In the admin, go to **Languages & Phrases > Search in Phrases**. < | ||
| - Use the tool to search for " | - Use the tool to search for " | ||
| - | - Click **edit** for the phrase found, and change the text to reflect a more appropriate message regarding the location of the registration within the Geo installation. | + | - Click **edit** for the phrase found, and change the text to reflect a more appropriate message regarding the location of the registration within the Geo installation. |
| - | - Save the changes. | + | - Save the changes. |
| - | We will be working to update the rest of the documentation, | ||
| - | ===== Legacy Documentation | + | ===== Convert Logout Links ===== |
| - | Below are the //old// integration instructions specific for vBulletin. They are provided | + | Within |
| + | index.php?a=17 | ||
| - | < | + | You would search for " |
| - | BASIC SETUP | + | |
| - | %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% | + | Logout link in language/ |
| + | - In admin panel at **Languages & Phrases > Search in Phrases**, for the text **log out**, then click //find//. < | ||
| + | - Click **edit** next to the entry that is found for **logout_error**. < | ||
| + | - Find the part of the text that is linking to the log out, it will be something like: <code html>< | ||
| + | Change the URL logout link to point to the logout page in the Geo software, so it looks something like this((change **example.php/ | ||
| + | <code html>< | ||
| + | - Save the changes. | ||
| + | < | ||
| + | - In admin panel at **Languages & Phrases > Search in Phrases**, for the text **log out**, then click //find//. < | ||
| + | - Click **edit** next to the entry that is found for **nopermission_loggedin**. < | ||
| + | - Find the part of the text that is linking to the log out, it will be something like: <code html>< | ||
| + | Change the URL logout link to point to the logout page in the Geo software, so it looks something like this((change **example.php/ | ||
| + | <code html>< | ||
| + | < | ||
| + | - Save the changes. < | ||
| + | - Repeat for any other phrases that are found, that contain links to log out. This does not include any entries that just contain the "log out" text but no <a ...> tag that links to log out. < | ||
| - | - Within | + | Logout link in templates: |
| + | | ||
| + | - Double-click on the first found template **FORUMHOME**. < | ||
| + | - In that template, find the logout link, it will be something like this: <code html>< | ||
| + | Change the URL logout link, so it looks something like this((change **example.php/ | ||
| + | <code html>< | ||
| + | Then save the changes. | ||
| + | < | ||
| + | - In admin panel at **Styles & Templates > Search in Templates**, | ||
| + | - Double-click on the found template **navbar**. < | ||
| + | - In that template, find the logout link, it will be something like this: <code html>< | ||
| + | Change the URL logout link, so it looks something like this((change **example.php/ | ||
| + | <code html>< | ||
| + | Then save the changes. | ||
| + | < | ||
| + | - Repeat for any other places that found a link to log out, to replace the **href value** with a link to the logout page within the Geo software. < | ||
| - | - Select No for allowing new registration. | + | We will be working to update the rest of the documentation, |
| - | - Within Languages & Phrases, search for | + | ===== Convert Registration Links ===== |
| - | | + | You can leave all the registration |
| - | + | ||
| - | - Change this to reflect a more appropriate message regarding | + | |
| - | registration within the Geo installation. | + | |
| - | + | ||
| - | - This is all that is required to force registrations | + | |
| - | Geo installation. | + | |
| - | %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% | + | If you would prefer a 1-click solution where all registration links point to Geo installation however, you can change all the registration links to " |
| + | You would search for " | ||
| - | ADVANCED SETUP | + | ===== Convert Log-in Links ===== |
| + | Within the vBulletin text, you will need to change all the log-in links to " | ||
| + | index.php? | ||
| - | %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% | + | You would search for " |
| - | - There is no way to consistently keep modifications that will work within | + | ===== Troubleshooting, |
| - | Vbulletin code. | + | The following are things |
| - | login, update user info, register and logout users. | + | |
| - | will have to make a few text(phrase) and template changes to point login, logout | + | |
| - | and register links back to the Geodesic Solutions installation. | + | |
| - | %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% | + | - If you see an error to the effect of " |
| + | - There is currently no way to modify Vbulletin profile information settings | ||
| + | through the bridge or current Geodesic Solutions installations. < | ||
| + | - No password history support. < | ||
| + | - No ban email support through Vbulletin. | ||
| + | the version and edition of Geodesic Solutions Software you have for any email banning facility that can be used. < | ||
| + | - Only the Geodesic Solutions installation email verification system 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. | ||
| + | - User removal in Geodesic software will not remove the user in vBulletin as a precaution, as any time a user is removed from a Geo installation, | ||
| + | - If the " | ||
| + | - 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' | ||
| - | Search | + | ====== Important Configuration |
| - | section of the vbulletin admin. | + | |
| - | - logout_missing_userid | + | |
| - | - nopermission_loggedin | + | |
| - | ############################################### | + | 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 |
| - | For logout_missing_userid | + | |
| - | An error occurred while attempting to log you out. <a href=" | + | Open the file **includes/ |
| - | do=logout& | + | |
| - | A sample change would be: | + | <code php> |
| + | /* Navbar stuff | ||
| + | Dont use DIR here, the Dev scripts dont like it */ | ||
| + | require_once(' | ||
| + | </ | ||
| - | For Auctions and root file of auctions.php: | + | Replace the above code with this: |
| - | An error occurred while attempting to log you out. <a href=" | + | |
| - | Click here to logout.</ | + | |
| - | For Classifieds and root file of classifieds.php: | + | < |
| - | An error occurred while attempting to log you out. <a href=" | + | /* Navbar stuff |
| - | Click here to logout.</a> | + | 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.'/includes/functions_navigation.php'); | ||
| + | </code> | ||
| - | NOTE: If the root file is index.php or something else that you have set change the links above accordingly. | + | and then save the file. This corrects |
| - | ############################################### | + | |
| - | + | ||
| - | ############################################### | + | |
| - | For nopermission_loggedin the text will be something similar to: | + | |
| - | + | ||
| - | < | + | |
| - | <ol> < | + | |
| - | features or some other privileged system?</ | + | |
| - | activation.</ | + | |
| - | <a href=" | + | |
| - | + | ||
| - | For Auctions | + | |
| - | < | + | |
| - | <ol> < | + | |
| - | features or some other privileged system?</ | + | |
| - | activation.</ | + | |
| - | <a href=" | + | |
| - | + | ||
| - | For Classifieds and root file of classifieds.php: | + | |
| - | < | + | |
| - | <ol> < | + | |
| - | features or some other privileged system?</ | + | |
| - | activation.</ | + | |
| - | <a href=" | + | |
| - | + | ||
| - | NOTE: If the root file is index.php or something else that you have set change the links above accordingly. | + | |
| - | ############################################### | + | |
| - | + | ||
| - | %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% | + | |
| - | + | ||
| - | %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% | + | |
| - | + | ||
| - | Search in Templates for: | + | |
| - | + | ||
| - | There will be three parts to Customize: FORUMHOME, navbar, and username_loggedin | + | |
| - | + | ||
| - | ############################################### | + | |
| - | - For FORUMHOME click [Customize] | + | |
| - | + | ||
| - | - Within the text area look for the following code: | + | |
| - | <!-- member logout --> | + | |
| - | <td align=" | + | |
| - | <phrase 1=" | + | |
| - | <!-- end member logout --> | + | |
| - | - Change it accordingly (Below is only a sample for auctions so apply necessary root file names per your product): | + | |
| - | <!-- member logout --> | + | |
| - | <td align=" | + | |
| - | <phrase 1=" | + | |
| - | <!-- end member logout --> | + | |
| - | ############################################### | + | |
| - | ############################################### | + | |
| - | - For navbar click [Customize] | + | |
| - | + | ||
| - | - Within the text area look for the following code: | + | |
| - | < | + | |
| - | onclick=" | + | |
| - | - Change it accordingly (Below is only a sample for auctions so apply necessary root file names per your product): | + | |
| - | < | + | |
| - | - Within the same text area look for the following code: | + | |
| - | <if condition=" | + | |
| - | <td class=" | + | |
| - | </ | + | |
| - | - Change it accordingly (Below is only a sample for auctions so apply necessary root file names per your product): | + | |
| - | <if condition=" | + | |
| - | <td class=" | + | |
| - | </ | + | |
| - | ############################################### | + | |
| - | ############################################### | + | |
| - | - For username_loggedin click [Customize] | + | |
| - | + | ||
| - | - Within the text area look for the following code: | + | |
| - | <span class=" | + | |
| - | - Change it accordingly (Below is only a sample for auctions so apply necessary root file names per your product): | + | |
| - | <span class=" | + | |
| - | ############################################### | + | |
| - | + | ||
| - | + | ||
| - | + | ||
| - | %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% | + | |
| - | + | ||
| - | %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% | + | |
| - | + | ||
| - | ***Apply the same exact steps as above for log in and register.*** | + | |
| - | + | ||
| - | %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% | + | |
| - | + | ||
| - | + | ||
| - | - The advanced scenario would be to only use one Geodesic Solutions software | + | |
| - | installation as the lead or dominant installation. | + | |
| - | register, user info update and logout | + | |
| - | to these facilities within | + | |
| - | lead or dominant installation would insure the most reliable relationship | + | |
| - | between all installations connected by the bridge. However, most seem to want registration | + | |
| - | to be centralized | + | |
| - | a much simpler set up. | + | |
| - | + | ||
| - | - There is currently no way to modify Vbulletin profile information settings | + | |
| - | through the bridge or current Geodesic Solutions installations. | + | |
| - | + | ||
| - | - No password history support. | + | |
| - | + | ||
| - | - No ban email support through Vbulletin. | + | |
| - | checked against the Geodesic Solutions installation for duplication. | + | |
| - | the version of Geodesic Solutions Software you have will that versions email | + | |
| - | banning facility be used. | + | |
| - | + | ||
| - | - Only the Geodesic Solutions installation email verification system 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. | + | |
| - | this within | + | |
| - | done for each individual installation connected by the bridge. | + | |
| - | </ | + | |