From bb8b0d7fe03f64a27c098f716ff5d1f3761aba38 Mon Sep 17 00:00:00 2001
From: "lpsolit%gmail.com" <>
Date: Tue, 21 Nov 2006 01:33:48 +0000
Subject: [PATCH] Docs for bug 233962: UserInGroup() no longer takes a second
 parameter - Patch by me, r=Colin

---
 docs/xml/customization.xml | 17 +++++++++++++++--
 1 file changed, 15 insertions(+), 2 deletions(-)

diff --git a/docs/xml/customization.xml b/docs/xml/customization.xml
index a64a8d7c46..609539ffe5 100644
--- a/docs/xml/customization.xml
+++ b/docs/xml/customization.xml
@@ -731,8 +731,21 @@
       <filename>data/versioncache</filename> for the list called 
       <filename>@::log_columns</filename>. If you need help writing custom
       rules for your organization, ask in the newsgroup.
-    </para>    
-  </section>   
+    </para>
+
+    <section id="cust-group-check">
+      <title>Modification in UserInGroup()</title>
+
+      <para>
+        The <filename>UserInGroup()</filename> function in the
+        <filename>globals.pl</filename> file only accepts
+        one argument since 2.17.5: the name of a group. This check
+        is now always done against the current user, and a second
+        argument specifying the user ID to check this group against
+        is no longer valid and an error is thrown if you try to.
+      </para>
+    </section>
+  </section>
   
   <section id="dbmodify">
     <title>Modifying Your Running System</title>
-- 
2.47.3