| 1 |
/* $Id: README.txt,v 1.15 2008/11/03 22:33:46 sun Exp $ */ |
/* $Id: README.txt,v 1.16 2009/05/17 15:25:56 sun Exp $ */ |
| 2 |
|
|
| 3 |
-- SUMMARY -- |
-- SUMMARY -- |
| 4 |
|
|
| 64 |
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, |
| 65 |
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. |
| 66 |
|
|
| 67 |
* To properly logout users from vBulletin and Drupal, you should replace the |
To properly login, logout, and synchronize users between vBulletin and Drupal, |
| 68 |
logout link in your vBulletin template with a link pointing to '/logout' |
|
| 69 |
(i.e. Drupal's logout URL), so the user is logged off from both systems. |
* open vBulletin's includes/config.php file and |
| 70 |
|
|
| 71 |
However, if you are using the singlesignon module, or your users are reporting |
- ensure that, when connecting via MySQLi, the 'charset' option is configured |
| 72 |
login issues (f.e. being logged in in the forums, but not in Drupal), then you |
as following: |
| 73 |
should replace all logout links throughout Drupal and vBulletin to point to |
|
| 74 |
'drupalvb/logout', which performs additional actions to ensure that a user is |
$config['Mysqli']['charset'] = 'utf8'; |
| 75 |
properly logged out. |
|
| 76 |
|
- append the following to disable password MD5-hashing via JavaScript: |
| 77 |
* To login users concurrently in Drupal and vBulletin, you should remove the |
|
| 78 |
user login form in your vBulletin template and point users to Drupal's |
/** |
| 79 |
login page. |
* DrupalvB: Disable MD5-hashing of passwords via JavaScript. |
| 80 |
|
*/ |
| 81 |
Alternatively, you can also alter the "action" attribute of the user login |
define('DISABLE_PASSWORD_CLEARING', TRUE); |
| 82 |
forms in your vBulletin forum templates to submit those forms to |
|
| 83 |
'drupalvb/login'. However, in this case you also have to ensure that |
* log in to vBulletin's AdminCP, go to |
| 84 |
vBulletin's JavaScript to md5-hash the typed password are not applied to the |
|
| 85 |
password form field. |
Styles & Templates >> Replacement Variable Manager |
| 86 |
|
|
| 87 |
|
and add the following replacement variables for your template: |
| 88 |
|
|
| 89 |
|
- login.php?do=login => /drupalvb/login |
| 90 |
|
|
| 91 |
|
- login.php?do=logout => /drupalvb/logout? |
| 92 |
|
|
| 93 |
|
(The trailing question mark is required.) |
| 94 |
|
|
| 95 |
|
- login.php?do=lostpw => /user/password |
| 96 |
|
|
| 97 |
|
- register.php => /user/register |
| 98 |
|
|
| 99 |
|
Optionally, if http://drupal.org/project/me is installed or a custom redirect |
| 100 |
|
has been implemented, you can also add (or similar): |
| 101 |
|
|
| 102 |
|
- profile.php?do=editpassword => /user/me/edit |
| 103 |
|
|
| 104 |
|
|
| 105 |
* 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 |
| 106 |
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 |
| 107 |
domains. |
domains. |
| 108 |
|
|
| 109 |
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 |
| 118 |
|
|
| 119 |
select your domain without the subdomain (i.e. example.com), and save. |
select your domain without the subdomain (i.e. example.com), and save. |
| 120 |
|
|
| 121 |
In Drupal settings.php, find the section about cookie domain determination |
In Drupal's settings.php, find the section about cookie domain determination |
| 122 |
(around line 150), and un-comment the following line (replacing 'example.com' |
(around line 150), and un-comment the following line (replacing 'example.com' |
| 123 |
with your domain): |
with your domain): |
| 124 |
|
|