Index: README.txt
===================================================================
RCS file: /cvs/drupal-contrib/contributions/modules/drupalvb/README.txt,v
retrieving revision 1.14
diff -u -p -r1.14 README.txt
--- README.txt	15 Oct 2008 02:31:03 -0000	1.14
+++ README.txt	3 Nov 2008 22:31:37 -0000
@@ -45,6 +45,9 @@ Bug reports, feature suggestions and lat
 * After installing vBulletin, copy config.php from your vBulletin includes/
   directory into DrupalvB's module folder.
 
+  Please note that you have to update this copy of config.php whenever the
+  original file is altered!
+
 
 -- CONFIGURATION --
 
@@ -57,29 +60,47 @@ Bug reports, feature suggestions and lat
 
 -- IMPLEMENTATION --
 
+Note: The following steps assume that you are using clean URLs in Drupal.  If
+      you do not, all paths need to be prefixed with 'index.php?q='.  Of course,
+      all paths also need to be prefixed with the proper base path of your site.
+
 * To properly logout users from vBulletin and Drupal, you should replace the
-  logout link in your vBulletin template with a link pointing to '/logout'
+  logout link in your vBulletin template with a link pointing to 'logout'
   (i.e. Drupal's logout URL), so the user is logged off from both systems.
 
+  However, if you are using the singlesignon module, or your users are reporting
+  login issues (f.e. being logged in in the forums, but not in Drupal), then you
+  should replace all logout links throughout Drupal and vBulletin to point to
+  'drupalvb/logout', which performs additional actions to ensure that a user is
+  properly logged out.
+
 * To login users concurrently in Drupal and vBulletin, you should remove the
   user login form in your vBulletin template and point users to Drupal's
   login page.
 
+  Alternatively, you can also alter the "action" attribute of the user login
+  forms in your vBulletin forum templates to submit those forms to
+  'drupalvb/login'.  However, in this case you also have to ensure that
+  vBulletin's JavaScript to md5-hash the typed password are not applied to the
+  password form field.
 
--- CUSTOMIZATION --
 
 * If you want to run your forums on a subdomain, f.e. forums.example.com rather
   than example.com/forums, you need to use a common cookie domain for both
   domains.
 
-  WARNING: Advanced users only. This may render your site unusable.
+  WARNING: A wrongly defined cookie domain can lead to a completely broken user
+           authentication, both in Drupal and vBulletin.  If the cookie domain
+           is set to a wrong value, all users are immediately logged out, and
+           can no longer login, including super administrators!
 
   In vBulletin, go to
 
     vBulletin Options >> Expand Setting Groups
-    >> Cookies and HTTP Header Options >> Cookie Domain >> Edit Settings,
+    >> Cookies and HTTP Header Options >> Cookie Domain >> Edit Settings
 
   select your domain without the subdomain (i.e. example.com), and save.
+
   In Drupal settings.php, find the section about cookie domain determination
   (around line 150), and un-comment the following line (replacing 'example.com'
   with your domain; without code tags):