| 1 |
/* $Id: README.txt,v 1.8.4.8 2009/05/17 15:26:00 sun Exp $ */ |
/* $Id: README.txt,v 1.8.4.8.2.1 2009/05/29 10:22:50 sun Exp $ */ |
| 2 |
|
|
| 3 |
-- SUMMARY -- |
-- SUMMARY -- |
| 4 |
|
|
| 102 |
you do not, all paths need to be prefixed with 'index.php?q='. Of course, |
you do not, all paths need to be prefixed with 'index.php?q='. Of course, |
| 103 |
all paths also need to be prefixed with the proper base path of your site. |
all paths also need to be prefixed with the proper base path of your site. |
| 104 |
|
|
| 105 |
* To properly logout users from vBulletin and Drupal, you should replace the |
To properly login, logout, and synchronize users between vBulletin and Drupal, |
| 106 |
logout link in your vBulletin template with a link pointing to '/logout' |
|
| 107 |
(i.e. Drupal's logout URL), so the user is logged off from both systems. |
* open vBulletin's includes/config.php file and |
| 108 |
|
|
| 109 |
However, if you are using the singlesignon module, or your users are reporting |
- ensure that, when connecting via MySQLi, the 'charset' option is configured |
| 110 |
login issues (f.e. being logged in in the forums, but not in Drupal), then you |
as following: |
| 111 |
should replace all logout links throughout Drupal and vBulletin to point to |
|
| 112 |
'drupalvb/logout', which performs additional actions to ensure that a user is |
$config['Mysqli']['charset'] = 'utf8'; |
| 113 |
properly logged out. |
|
| 114 |
|
- append the following to disable password MD5-hashing via JavaScript: |
| 115 |
* To login users concurrently in Drupal and vBulletin, you should remove the |
|
| 116 |
user login form in your vBulletin template and point users to Drupal's |
/** |
| 117 |
login page. |
* DrupalvB: Disable MD5-hashing of passwords via JavaScript. |
| 118 |
|
*/ |
| 119 |
Alternatively, you can also alter the "action" attribute of the user login |
define('DISABLE_PASSWORD_CLEARING', TRUE); |
| 120 |
forms in your vBulletin forum templates to submit those forms to |
|
| 121 |
'drupalvb/login'. However, in this case you also have to ensure that |
* log in to vBulletin's AdminCP, go to |
| 122 |
vBulletin's JavaScript to md5-hash the typed password are not applied to the |
|
| 123 |
password form field. |
Styles & Templates >> Replacement Variable Manager |
| 124 |
|
|
| 125 |
|
and add the following replacement variables for your template: |
| 126 |
|
|
| 127 |
|
- login.php?do=login => /drupalvb/login |
| 128 |
|
|
| 129 |
|
- login.php?do=logout => /drupalvb/logout? |
| 130 |
|
|
| 131 |
|
(The trailing question mark is required.) |
| 132 |
|
|
| 133 |
|
- login.php?do=lostpw => /user/password |
| 134 |
|
|
| 135 |
|
- register.php => /user/register |
| 136 |
|
|
| 137 |
|
Optionally, if http://drupal.org/project/me is installed or a custom redirect |
| 138 |
|
has been implemented, you can also add (or similar): |
| 139 |
|
|
| 140 |
|
- profile.php?do=editpassword => /user/me/edit |
| 141 |
|
|
| 142 |
|
|
| 143 |
* If you want to run your forums on a subdomain, f.e. forums.example.com rather |
* If you want to run your forums on a subdomain, f.e. forums.example.com rather |
| 144 |
than example.com/forums, you need to use a common cookie domain for both |
than example.com/forums, then you need to use a common cookie domain for both |
| 145 |
domains. |
domains. |
| 146 |
|
|
| 147 |
WARNING: A wrongly defined cookie domain can lead to a completely broken user |
WARNING: A wrongly defined cookie domain can lead to a completely broken user |
| 156 |
|
|
| 157 |
select your domain without the subdomain (i.e. example.com), and save. |
select your domain without the subdomain (i.e. example.com), and save. |
| 158 |
|
|
| 159 |
In Drupal settings.php, find the section about cookie domain determination |
In Drupal's settings.php, find the section about cookie domain determination |
| 160 |
(around line 150), and un-comment the following line (replacing 'example.com' |
(around line 150), and un-comment the following line (replacing 'example.com' |
| 161 |
with your domain): |
with your domain): |
| 162 |
|
|