<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>http://gwiki3.thatlinuxbox.com/index.php?action=history&amp;feed=atom&amp;title=PLG_getDocumentationUrl</id>
		<title>PLG getDocumentationUrl - Revision history</title>
		<link rel="self" type="application/atom+xml" href="http://gwiki3.thatlinuxbox.com/index.php?action=history&amp;feed=atom&amp;title=PLG_getDocumentationUrl"/>
		<link rel="alternate" type="text/html" href="http://gwiki3.thatlinuxbox.com/index.php?title=PLG_getDocumentationUrl&amp;action=history"/>
		<updated>2026-04-06T10:23:32Z</updated>
		<subtitle>Revision history for this page on the wiki</subtitle>
		<generator>MediaWiki 1.27.5</generator>

	<entry>
		<id>http://gwiki3.thatlinuxbox.com/index.php?title=PLG_getDocumentationUrl&amp;diff=4922&amp;oldid=prev</id>
		<title>Dirk: New plugin API function: PLG_getDocumentationUrl</title>
		<link rel="alternate" type="text/html" href="http://gwiki3.thatlinuxbox.com/index.php?title=PLG_getDocumentationUrl&amp;diff=4922&amp;oldid=prev"/>
				<updated>2009-04-11T17:11:01Z</updated>
		
		<summary type="html">&lt;p&gt;New plugin API function: PLG_getDocumentationUrl&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;In some situations, Geeklog will need a link to a plugin's documentation. The following plugin API function provides this information:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;function PLG_getDocumentationUrl($type, $file)&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Where &amp;lt;code&amp;gt;$type&amp;lt;/code&amp;gt; is the internal name of the plugin (e.g. &amp;lt;tt&amp;gt;'spamx'&amp;lt;/tt&amp;gt;) and &amp;lt;code&amp;gt;$file&amp;lt;/code&amp;gt; is a name for the part of the documentation being requested.&lt;br /&gt;
&lt;br /&gt;
On the plugin side, this would be implemented as&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;function plugin_getdocumentationurl_foo($file)&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Documentation Links ==&lt;br /&gt;
&lt;br /&gt;
Currently, &amp;lt;code&amp;gt;$file&amp;lt;/code&amp;gt; can be one of the following:&lt;br /&gt;
* &amp;lt;tt&amp;gt;'index'&amp;lt;/tt&amp;gt; - a link to the index page of the plugin's documentation&lt;br /&gt;
* &amp;lt;tt&amp;gt;'config'&amp;lt;/tt&amp;gt; - a link to the part of the plugin's documentation where the configuration options are explained (see below for details)&lt;br /&gt;
&lt;br /&gt;
We may want to add support for more values of &amp;lt;code&amp;gt;$file&amp;lt;/code&amp;gt; in the future, e.g. &amp;lt;tt&amp;gt;'help'&amp;lt;/tt&amp;gt; to link to the plugin's help, etc.&lt;br /&gt;
&lt;br /&gt;
== Conventions ==&lt;br /&gt;
&lt;br /&gt;
* When the plugin does not offer the file type requested, it should return &amp;lt;code&amp;gt;false&amp;lt;/code&amp;gt; or an empty string.&lt;br /&gt;
* The URLs do not have to be in the same directory or even on the same site.&lt;br /&gt;
* The caller should not make any assumptions about the URLs.&lt;br /&gt;
* The documentation doesn't have to be provided as static HTML pages - it could just as well be created dynamically, i.e. link to a .php script.&lt;br /&gt;
&lt;br /&gt;
=== Config Links ===&lt;br /&gt;
&lt;br /&gt;
Geeklog will request a file type &amp;lt;tt&amp;gt;'config'&amp;lt;/tt&amp;gt; to link to a description of the plugin's configuration options from the Configuration admin panel (the &amp;lt;tt&amp;gt;(?)&amp;lt;/tt&amp;gt; links next to the configuration options).&lt;br /&gt;
&lt;br /&gt;
Geeklog will attach an anchor of the form &amp;lt;tt&amp;gt;#desc_''optionname''&amp;lt;/tt&amp;gt; to the supplied URL, assuming that such an anchor exists on the page so that the user will be taken directly to the description of the option in question.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Plugin Development]]&lt;/div&gt;</summary>
		<author><name>Dirk</name></author>	</entry>

	</feed>