From e7434df3a18849bfcbb50f9a06b3b00d0fe62e74 Mon Sep 17 00:00:00 2001
From: Roland Gruber <post@rolandgruber.de>
Date: Mon, 21 Apr 2014 10:32:00 +0000
Subject: [PATCH] made can_manage() abstract in baseModule to save memory

---
 lam/docs/devel/upgrade.htm        | 13 ++++++++++++-
 lam/docs/manual-sources/howto.xml | 19 ++++++++++++++++---
 2 files changed, 28 insertions(+), 4 deletions(-)

diff --git a/lam/docs/devel/upgrade.htm b/lam/docs/devel/upgrade.htm
index aa14ad4a..215a1f78 100644
--- a/lam/docs/devel/upgrade.htm
+++ b/lam/docs/devel/upgrade.htm
@@ -19,6 +19,7 @@
 
 
 
+
 
 
 
@@ -39,7 +40,17 @@ This is a list of API changes for all LAM releases.
 
 <br>
 
-<h2>4.2 -&gt; 4.3</h2><span style="font-weight: bold;">Ldap::new_rand()</span> was replaced by <span style="font-weight: bold;">getRandomNumber()</span> in lib/account.inc.<br>
+<h2>4.5 -&gt; 4.6</h2>The valid account types for each module must now
+be set in can_manage(). This function is abstract in base module.
+Setting the account type via meta data is no longer supported.<br>
+<br>
+Example:<br>
+<pre>&nbsp;&nbsp;&nbsp; public function can_manage() {</pre>
+<pre>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; return in_array($this-&gt;get_scope(), array('user', 'host'));</pre>
+<pre>&nbsp;&nbsp;&nbsp; }</pre>
+<br>
+<h2>4.2 -&gt; 4.3</h2>
+<span style="font-weight: bold;">Ldap::new_rand()</span> was replaced by <span style="font-weight: bold;">getRandomNumber()</span> in lib/account.inc.<br>
 Module interface:<br>
 <ul>
   <li><span style="font-weight: bold;">preModifySelfService/postModifySelfService:</span> new parameter <span style="font-style: italic;">$newAccount</span>. The user self registration now supports preCreate/postCreate events.<br>
diff --git a/lam/docs/manual-sources/howto.xml b/lam/docs/manual-sources/howto.xml
index d0de880d..db56c326 100644
--- a/lam/docs/manual-sources/howto.xml
+++ b/lam/docs/manual-sources/howto.xml
@@ -1078,7 +1078,7 @@ Have fun!
         of the passwords.</para>
       </section>
 
-      <section>
+      <section id="conf_logging">
         <title>Logging</title>
 
         <para>LAM can log events (e.g. user logins). You can use system
@@ -1089,7 +1089,8 @@ Have fun!
 
         <para>The PHP error reporting is only for developers. By default LAM
         does not show PHP notice messages in the web pages. You can select to
-        use the php.ini setting here.</para>
+        use the php.ini setting here or printing all errors and
+        notices.</para>
 
         <screenshot>
           <mediaobject>
@@ -9485,7 +9486,7 @@ a.lamLogo {
       </screenshot>
 
       <para><literallayout>
-</literallayout><emphasis role="bold">Logging:</emphasis></para>
+</literallayout><emphasis role="bold">LDAP Logging:</emphasis></para>
 
       <para>If your schema is correct you can turn on LDAP logging to get more
       detailed error messages from your LDAP server.</para>
@@ -9510,6 +9511,18 @@ a.lamLogo {
 
       <para>After changing the configuration please restart OpenLDAP. It
       usually uses /var/log/syslog for log output.</para>
+
+      <literallayout>
+</literallayout>
+
+      <para><emphasis role="bold">PHP logging</emphasis></para>
+
+      <para>Sometimes it can help to enable PHP logging inside LAM. You can do
+      this in the <link linkend="conf_logging">logging area</link> of LAM's
+      main configuration. Set the logging option to "all" and check if there
+      are any messages printed in your browser window. Please note that not
+      every notice message is an error but it may help to find the
+      problem.</para>
     </section>
 
     <section>