[geeklog-cvs] Geeklog-1.x/public_html/docs links.html, 1.5, 1.6 plugin.html, 1.21, 1.22 staticpages.html, 1.16, 1.17

Dirk Haun dhaun at qs1489.pair.com
Sun May 11 12:40:02 EDT 2008


Update of /cvsroot/geeklog/Geeklog-1.x/public_html/docs
In directory qs1489.pair.com:/tmp/cvs-serv42764

Modified Files:
	links.html plugin.html staticpages.html 
Log Message:
More references to config.php eliminated


Index: links.html
===================================================================
RCS file: /cvsroot/geeklog/Geeklog-1.x/public_html/docs/links.html,v
retrieving revision 1.5
retrieving revision 1.6
diff -C2 -d -r1.5 -r1.6
*** links.html	10 May 2008 15:02:14 -0000	1.5
--- links.html	11 May 2008 16:40:00 -0000	1.6
***************
*** 31,35 ****
      Please note that <code>$_CONF['<a
      href="config.html#desc_loginrequired">loginrequired</a>']</code> in
!     <tt>config.php</tt> takes precedence over this setting. So when
      <code>'loginrequired'</code> is set to 1, anonymous users can not access
      the links section even when <code>'linksloginrequired'</code> is set
--- 31,35 ----
      Please note that <code>$_CONF['<a
      href="config.html#desc_loginrequired">loginrequired</a>']</code> in
!     Geeklog's main configuration takes precedence over this setting. So when
      <code>'loginrequired'</code> is set to 1, anonymous users can not access
      the links section even when <code>'linksloginrequired'</code> is set

Index: staticpages.html
===================================================================
RCS file: /cvsroot/geeklog/Geeklog-1.x/public_html/docs/staticpages.html,v
retrieving revision 1.16
retrieving revision 1.17
diff -C2 -d -r1.16 -r1.17
*** staticpages.html	5 Aug 2007 09:33:02 -0000	1.16
--- staticpages.html	11 May 2008 16:40:00 -0000	1.17
***************
*** 127,135 ****
  <p align="center"><tt>http://yoursite/staticpages/index.php/about</tt></p>
  
! <p>To make use of URL rewriting, you will need to enable it in Geeklog's <tt>config.php</tt> file by setting</p>
! 
! <p><code>$_CONF['url_rewrite'] = true;</code></p>
! 
! <p>The Static Pages plugin is currently the only plugin known to make use of this feature.</p>
  
  <h3><a name="delete">Deleting pages with their owner</a></h3>
--- 127,131 ----
  <p align="center"><tt>http://yoursite/staticpages/index.php/about</tt></p>
  
! <p>To make use of URL rewriting, you will need to set the option "Enable URL Rewriting" to True in Geeklog's Configuration admin panel.</p>
  
  <h3><a name="delete">Deleting pages with their owner</a></h3>

Index: plugin.html
===================================================================
RCS file: /cvsroot/geeklog/Geeklog-1.x/public_html/docs/plugin.html,v
retrieving revision 1.21
retrieving revision 1.22
diff -C2 -d -r1.21 -r1.22
*** plugin.html	5 Aug 2007 09:33:02 -0000	1.21
--- plugin.html	11 May 2008 16:40:00 -0000	1.22
***************
*** 388,396 ****
      <tr>
          <td valign="top" class="codeheader">plugin_chkVersion_<plugin name></td>
!         <td valign="top" class="code">Plugins should implement this function and return the code version. Plugins should use a variable in the plugins config.php for the code version which allows the developer to easily update it before releasing a new version. As of Geeklog 1.3.10, this API function is called in the plugin Editor to show the version of the current installed version and plugin code version. The plugin installed version is pulled from the plugins table and should be updated as part of the plugin install or future updates. This API function allows the site admin to know if the current plugin code is newer then the installed version. Plugin developers can read the installed version from the plugins table and determine automatically if any SQL updates are required or atleast update the plugin record to be the same as the code version.</td>
      </tr>
      <tr>
          <td valign="top" class="codeheader">plugin_runScheduledTask_<plugin name></td>
!         <td valign="top" class="code">This function allows plugin developers to schedule a task to be run. This API will only be called when someone accesses the site but should be sufficient for most plugins that want to schedule some maintenance process or clean-up routine. The interval this API is called is set in the site's config.php and all plugins that have this function will then be called.</td>
      </tr>
  
--- 388,396 ----
      <tr>
          <td valign="top" class="codeheader">plugin_chkVersion_<plugin name></td>
!         <td valign="top" class="code">Plugins should implement this function and return the code version. Plugins should use a variable in the plugin's functions.inc for the code version which allows the developer to easily update it before releasing a new version. As of Geeklog 1.3.10, this API function is called in the plugin Editor to show the version of the current installed version and plugin code version. The plugin installed version is pulled from the plugins table and should be updated as part of the plugin install or future updates. This API function allows the site admin to know if the current plugin code is newer then the installed version. Plugin developers can read the installed version from the plugins table and determine automatically if any SQL updates are required or atleast update the plugin record to be the same as the code version.</td>
      </tr>
      <tr>
          <td valign="top" class="codeheader">plugin_runScheduledTask_<plugin name></td>
!         <td valign="top" class="code">This function allows plugin developers to schedule a task to be run. This API will only be called when someone accesses the site but should be sufficient for most plugins that want to schedule some maintenance process or clean-up routine. The interval this API is called is set in the site's configuration and all plugins that have this function will then be called.</td>
      </tr>
  
***************
*** 487,494 ****
  
  <dl>
! <dt>config.php:</dt><dd>configuration page for your plugin.  We'd
!    prefer you to  data-drive most the values if possible but using config.php
!    is fine.   This file can be called whatever you want...you are not
!  restricted.</dd>
  <dt>functions.inc:</dt><dd>this is the file where you implement the Geeklog
     API and where your plugin code should reside.  It MUST be named this
--- 487,496 ----
  
  <dl>
! <dt>config.php:</dt><dd>configuration file for your plugin.  We'd suggest
!     that you try and use Geeklog's built-in configuration admin panel (as of
!     Geeklog 1.5) if at all possible instead, since it makes things much easier
!     for the users of your plugin. The Geeklog Wiki has some more information
!     on <a href="http://wiki.geeklog.net/wiki/index.php/PluginConfiguration">how
!     to use the configuration for a plugin</a>.</dd>
  <dt>functions.inc:</dt><dd>this is the file where you implement the Geeklog
     API and where your plugin code should reside.  It MUST be named this




More information about the geeklog-cvs mailing list