[geeklog-cvs] geeklog-1.3/public_html/docs history,1.238,1.239

dhaun at iowaoutdoors.org dhaun at iowaoutdoors.org
Tue Sep 21 07:54:13 EDT 2004


Update of /var/cvs/geeklog-1.3/public_html/docs
In directory www:/tmp/cvs-serv29317/public_html/docs

Modified Files:
	history 
Log Message:
Updated list of changes


Index: history
===================================================================
RCS file: /var/cvs/geeklog-1.3/public_html/docs/history,v
retrieving revision 1.238
retrieving revision 1.239
diff -C2 -d -r1.238 -r1.239
*** history	18 Sep 2004 19:08:18 -0000	1.238
--- history	21 Sep 2004 11:54:11 -0000	1.239
***************
*** 4,7 ****
--- 4,21 ----
  ------------
  
+ - Plugins can now offer their own tags to allow easy linking to their content.
+   These tags take the form [name:id link text], where 'name' is a name
+   associated with the plugin, 'id' is a unique id referring to one of the
+   objects under the plugin's control, and 'link text' is text used in the <a>
+   tag that Geeklog creates from these tags.
+   Built-in tags are [story:] to link to a story and [event:] to link to an
+   event [Blaine, Dirk]
+   Example: [story:email-bug About the email bug] would be translated into
+   <a href="http://example.com/article.php/email-bug">About the email bug</a>
+ - portal.php now sends a 301 HTTP status code for the links instead of a 302.
+   While a 302 status code would actually make more sense, Google does have a
+   tendency to list search results with the URL of the portal script but with
+   the content of the linked site, thus giving the impression that the content
+   is actually located on another site. Sending a 301 avoids this problem [Dirk]
  - Group Admins should not even see the groups of which they are not a member
    (bug #280) [Dirk]




More information about the geeklog-cvs mailing list