+++ /dev/null
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">\r
-<html xmlns="http://www.w3.org/1999/xhtml">\r
-<head>\r
- <!-- $Id: custominstall.html,v 1.4 2005-03-19 07:28:32 kimitake Exp $ -->\r
- <title>Nucleus - Custom Install Scripts</title>\r
- <link rel="stylesheet" type="text/css" href="styles/manual.css" />\r
-</head>\r
-<body>\r
-\r
-<div class="heading">\r
-Customized Install Scripts\r
-</div>\r
-\r
-<p class="note">Note: this functionality is only available in versions > v2.2.</p>\r
-\r
-<h1>Introduction</h1>\r
-\r
-<p>\r
-<a href="index.html">Back to the developer docs index</a>\r
-</p>\r
-\r
-<p>\r
-This document contains information on how to customize the Nucleus install script. It can be customized in two ways:\r
-</p>\r
-\r
-<ol>\r
- <li>Automatically install skins</li>\r
- <li>Automatically install plugins</li>\r
-</ol>\r
-\r
-<h1>Configurations</h1>\r
-\r
-<p>Open up the <code>install.php</code> script and locate the following piece of code:</p>\r
-\r
-<pre><code> // array with names of plugins to install. Plugin files must be present in the nucleus/plugin/\r
- // directory.\r
- //\r
- // example:\r
- // array('NP_TrackBack', 'NP_MemberGoodies')\r
- $aConfPlugsToInstall = array();\r
-\r
-\r
- // array with skins to install. skins must be present under the skins/ directory with\r
- // a subdirectory having the same name that contains a skinbackup.xml file\r
- //\r
- // example:\r
- // array('base','rsd')\r
- $aConfSkinsToImport = array();</code></pre>\r
-\r
-<p>This code is all you need to change: list the names of the plugins and skins you want to auto-install in the arrays.</p>\r
-\r
-<h1>Including the files</h1>\r
-\r
-<p>Next to changing the configuration, you'll need to add the files to the zipfile distribution.</p>\r
-\r
-<h2>Plugins</h2>\r
-\r
-<p>For plugins, place the files in the <code>nucleus/plugins/</code> directory. Just as when you would install a plugin manually.</p>\r
-\r
-<p>For skins, place them as directories under <code>skins/</code>, just as you would do when importing a skin manually. Don't forget to put the <code>skinimport.xml</code> file in there.</p>\r
-\r
-<h1>Don't forget</h1>\r
-\r
-<p>Don't forget to test your customized install script before distributing it.</p>\r
-\r
-</body>\r
-</html>
\ No newline at end of file
+++ /dev/null
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">\r
-<html xmlns="http://www.w3.org/1999/xhtml">\r
-<head>\r
- <!-- $Id: index.html,v 1.4 2005-03-19 07:28:32 kimitake Exp $ -->\r
- <title>Nucleus - Development Documentation</title>\r
- <link rel="stylesheet" type="text/css" href="styles/manual.css" />\r
-</head>\r
-<body>\r
-\r
-<div class="heading">\r
-Developer Docs\r
-</div>\r
-\r
-<h1>Introduction</h1>\r
-\r
-<p>\r
-This document contains information about Nucleus that is only relevant to developers.\r
-</p>\r
-\r
-<h1>Table of Contents</h1>\r
-\r
-<ul>\r
- <li><a href="xmlrpc.html">XML-RPC interfaces</a></li>\r
- <li><a href="plugins.html">Nucleus Plugin API</a></li>\r
- <li><a href="custominstall.html">Customized Install Scripts</a></li>\r
- <li><a href="sqltables.html">Database Structure</a></li>\r
-</ul>\r
-\r
-</body>\r
-</html>
\ No newline at end of file
+++ /dev/null
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">\r
-<html xml:lang="jp" xmlns="http://www.w3.org/1999/xhtml">\r
-<head>\r
- <!-- $Id: plugins.html,v 1.4 2005-03-16 08:05:24 kimitake Exp $ -->\r
- <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">\r
- <title>Nucleus - プラグイン API</title>\r
- <link rel="stylesheet" type="text/css" href="styles/manual.css" />\r
- <style type="text/css">\r
- /* refence parameters (greenish) */\r
- .ref {\r
- background-color: #afa; \r
- color: #000;\r
- }\r
- \r
- /* object parameters */\r
- .obj {\r
- color: #00f;\r
- }\r
- .obj:after {\r
- content: " (object)";\r
- }\r
- \r
- /* read-only parameters (non-ref; reddish) */\r
- .ro {\r
- background-color: #faa;\r
- color: #000;\r
- }\r
- </style>\r
-</head>\r
-<body>\r
-\r
-<p class="heading"> </p>\r
-<div class="heading">\r
-プラグイン API\r
-<i>2005年3月5日</i>\r
-</div>\r
-\r
-<div class="note-trans"><strong>訳者注：</strong> \r
- <ul>\r
- <li>このドキュメントの原文は以下のURLにあります。<br />\r
- <a href="http://nucleuscms.org/documentation/devdocs/plugins.html">http://nucleuscms.org/documentation/devdocs/plugins.html</a></li>\r
- <li>誤訳にお気づきの方は<a href="http://japan.nucleuscms.org/bb/viewforum.php?f=7">こちら</a>へご連絡いただけると助かります。</li>\r
- </ul>\r
-</div>\r
-\r
-<div class="note"><strong>注：</strong> \r
- <ul>\r
- <li>このドキュメントは基本的なプラグインの書き方についての情報を提供しています。さらに質問がある方は <a href="http://forum.nucleuscms.org/viewforum.php?f=10">Plugin\r
- Development Forum</a> （<a href="http://japan.nucleuscms.org/bb/viewforum.php?f=5">日本語フォーラム</a>）をご覧ください。</li>\r
- <li>Nucleusバージョン1.5以降に導入されたメソッドとイベントには、導入時のバージョン情報を付記しています。それらの機能を利用するときは、<code>getMinNucleusVersion</code> を適切に設定するのを忘れないでください。</li>\r
- </ul>\r
-</div>\r
-\r
-<h1>はじめに</h1>\r
-\r
-<p>\r
-<a href="./index.html">開発者向けドキュメントの目次へ戻る</a>\r
-</p>\r
-\r
-<p>\r
-このドキュメントはNucleusプラグインの作り方についての解説です。 \r
-</p>\r
-\r
-<h1><a name="toc"></a><a name="top"></a>目次</h1>\r
-\r
-<ul>\r
- <li><a href="#introduction">イントロダクション</a></li>\r
- <li><a href="#firstplug">はじめてプラグインを書いてみる</a></li>\r
- <li><a href="#nucleusplugin"><code>NucleusPlugin</code> クラスの概要</a></li>\r
- <li><a href="#skinvars"><code><%plugin(...)%></code> スキン変数</a></li>\r
- <li><a href="#templatevars"><code><%plugin(...)%></code> テンプレート変数</a></li> \r
- <li><a href="#actions"><code>action.php</code> を使ったアクション</a></li>\r
- <li><a href="#events">イベントとイベント登録の仕方</a></li>\r
- <li><a href="#options">オプションを保存する</a></li>\r
- <li><a href="#tables">データベース・テーブル</a></li>\r
- <li><a href="#admin">プラグイン管理エリアの提供</a></li>\r
- <li><a href="#help">ヘルプページの提供</a></li>\r
- <li><a href="#dependency">プラグイン依存チェック</a></li>\r
-<!-- <li><a href="#parser">Using the <code>PARSER</code> class</a></li>\r
- <li><a href="#"></a></li>\r
- <li><a href="#"></a></li>\r
- <li><a href="#"></a></li>\r
- <li><a href="#"></a></li>-->\r
-</ul>\r
-\r
-<h1>イントロダクション <a name="introduction" href="#top" class="toplink"><img src="../icon-up.gif" width="15" height="15" alt="back to top" /></a></h1>\r
-\r
-<p>\r
-Nucleusプラグインによって、誰もがNucleusの提供する機能を、Nucleus内部のPHPコードを変更することなく拡張することができます。プラグインはあるメソッドを実装したシンプルなPHPスクリプトで、Nucleusユーザー同士で簡単に交換することができます。インストールは簡単で、プラグインディレクトリにファイルをアップし、Nucleusにそれを認識させるだけです。\r
-</p>\r
-\r
-<p>\r
-プラグインの利点は以下のとおりです。</p>\r
-\r
-<ul>\r
- <li>実装について詳しくしらなくてもNucleusフレームワークに簡単に機能を追加できる</li>\r
- <li>必要なプラグインだけをインストールでき、ページ生成にかかる時間を節約できる</li>\r
-</ul>\r
-\r
-<p>\r
-すべてのプラグインファイルは <code>config.php</code> に記述されたディレクトリに置く必要があります。一般的に、それは <code>/your/path/nucleus/plugins/</code> になるでしょう。プラグインファイル名は <code>NP<i>_name</i>.php</code> という形式を用いることにより認識されます。プラグインによっては、追加ファイルを格納する同名のサブディレクトリや、管理エリアを必要とします。</p>\r
-\r
-<div class="note">\r
-<b>注：</b> プラグイン名は大文字・小文字を識別しますので、<code>Np_</code> や <code>np_</code> ではなく、<code>NP_</code> で始まることに気をつけてください。またプラグインがサブディレクトリを使用する場合は、サブディレクトリの名称は<em>すべて小文字にします</em>。</div>\r
-\r
-\r
-\r
-\r
-<h1>はじめてプラグインを書いてみる<a name="firstplug" href="#top" class="toplink"><img src="../icon-up.gif" width="15" height="15" alt="back to top" /></a></h1>\r
-\r
-<p>\r
-では、シンプルなプラグインを書いてみましょう。基本的にプラグインは、あらかじめ定義された <code>NucleusPlugin</code> クラスを継承したPHPクラスです。以下は<code>HelloWorld</code>プラグインの例です。</p>\r
-\r
-<pre class="example"><code><?\r
-\r
-class NP_HelloWorld extends NucleusPlugin {\r
-\r
- // プラグインの名前\r
- function getName() {\r
- return 'Hello World'; \r
- }\r
- \r
- // プラグインの作者\r
- function getAuthor() { \r
- return 'Wouter Demuynck'; \r
- }\r
- \r
- // プラグインのサイトURL\r
- // mailto:foo@bar.com の形式も可\r
- function getURL() \r
- {\r
- return '../../index.html'; \r
- }\r
- \r
- // プラグインのバージョン\r
- function getVersion() {\r
- return '1.0'; \r
- }\r
- \r
- // インストール済みのプラグインリストに表示される説明文\r
- function getDescription() { \r
- return 'Just a sample plugin.';\r
- }\r
-\r
- function doSkinVar($skinType) {\r
- echo 'Hello World!';\r
- }\r
- \r
-}\r
-?></pre>\r
-\r
-<ol>\r
- <li>\r
- このコードをコピーし、 <code>NP_HelloWorld.php</code> と名づけて保存し、プラグインディレクトリに置きます。<em>最後の <code>?></code> の後や、最初の <code><?</code> の前にスペースがないことを確認しましょう</em>。ところでNP は "Nucleus Plugin" って意味ですよ :-)\r
- </li>\r
- <li>Nucleusの管理画面を開き、<em>Nucleusの管理＞プラグインの管理</em>にいきます。</li>\r
- <li><em>HelloWorld</em> プラグインがインストール可能な状態になっているはずですので、インストールします。すべてがうまくいけば、インストール済みプラグインリストに追加されます。</li>\r
- <li>スキンを編集し、実際のページに表示する箇所に次の文を挿入します。\r
- <pre class="example"><code><%plugin(HelloWorld)%></code></pre>\r
- 注意：カッコ内の名称 (HelloWorld) は大文字小文字を識別します！</li>\r
- <li>さて、編集したスキンから生成されるページを見てみましょう。プラグイン変数を追加した場所に "Hello\r
- World" と見えますね？</li>\r
-</ol>\r
-\r
-<p>ここまではそれほど難しくなかったと思います。さらに読み進めて理解してください。</p>\r
-\r
-\r
-<h1>NucleusPlugin クラスの概要 <a name="nucleusplugin" href="#top" class="toplink"><img src="../icon-up.gif" width="15" height="15" alt="back to top" /></a></h1>\r
-\r
-<p>すべてのプラグインは、<code>NucleusPlugin</code> というPHPクラスを継承しなければなりません。難しそうに聞こえても心配ご無用、大丈夫です。このPHPクラスの継承によって、プラグインに必要なメソッドだけを実装でき、いくつかの補助ファンクションにアクセスでき、つまりはあなたの人生はよりラクになります。</p>\r
-\r
-<p>下記は <code>NucleusPlugin</code> が提供する、再実装可能なメソッドの概要です。このクラス自身のソースコードを見たければ、<code>nucleus/libs/PLUGIN.php</code>にあります。</p>\r
-\r
-<table summary="An overview of the redefinable methods in the class NucleusPlugin">\r
- <caption>\r
- <code>NucleusPlugin</code> クラスの概要（再定義可能なメソッド）\r
- </caption>\r
- <tr>\r
- <th>メソッド名</th><th>説明</th>\r
- </tr>\r
- <tr>\r
- <td><code>getName()</code></td>\r
- <td>プラグイン名を返します。インストール済みプラグインリストに表示されます。デフォルトの実装では <code>Undefined</code> を返すため、必ず再定義されないといけません。</td> \r
- </tr>\r
- <tr>\r
- <td><code>getAuthor()</code></td>\r
- <td>プラグインの作者名を返します。インストール済みプラグインリストに表示されます。デフォルトの実装では <code>Undefined</code> を返すため、必ず再定義されないといけません。</td> \r
- </tr>\r
- <tr>\r
- <td><code>getURL()</code></td>\r
- <td>プラグインをダウンロード可能な、またはプラグインの追加情報のあるサイトのURLを返します。そのようなサイトがない場合は作者のメールアドレスへの mailto:リンクが適切です。デフォルトの実装では <code>Undefined</code> を返すため、必ず再定義されないといけません。</td> \r
- </tr>\r
- <tr>\r
- <td><code>getDescription()</code></td>\r
- <td>プラグインに関する説明文（長文）を返します。インストール済みプラグインリストに表示されます。デフォルトの実装では <code>Undefined</code> を返します。</td> \r
- </tr>\r
- <tr>\r
- <td><code>getVersion()</code></td>\r
- <td>プラグインの現在のバージョンを返します。デフォルトは <code>0.0</code> を返します。</td> \r
- </tr>\r
- <tr>\r
- <td><code>getMinNucleusVersion()</code></td>\r
- <td>(v2.0b) 最低限必要なNucleusのバージョンを返します。デフォルトは <code>155</code> (v1.55)を返します。後に導入されたプラグイン関連機能を利用している場合は、このファンクションを実装するようお願いします（例： v2.0 => 200）。ただし、Nucleus v1.55 はこのファンクションを使用しないため、新機能を利用したプラグインが（対応する前のシステムに）インストールされる可能性が残っています。</td>\r
- </tr>\r
- <tr>\r
- <td><code>getMinNucleusPatchLevel()</code></td>\r
- <td>(v3.1) 最低限必要なNucleusのバージョン(<code>getMinNucleusVersion</code>)での、最低限必要なパッチレベルを返します。デフォルトは <code>0</code> を返します。このファンクションは主に新しいプラグインの機能がNucleusの最新版のパッチによって可能になる場合に用いられます。</td>\r
- </tr>\r
- <tr>\r
- <td><code>init()</code></td>\r
- <td>プラグインを初期化します。このメソッドはプラグインオブジェクトが生成された直後に呼び出され、<code>plugid</code>属性がセットされます。デフォルトではこのメソッドは何もしません。</td>\r
- </tr>\r
- <tr>\r
- <td><code>doSkinVar($skinType)</code></td>\r
- <td><code><%plugin(...)%></code> スキン変数によってプラグインが呼び出されたときにこのメソッドが呼ばれます。<code>$skinType</code> パラメータはプラグインが呼ばれた場所のスキンタイプに該当します（<code>item</code>,\r
- <code>archive</code>, ...）。パラメータが一つしかないことに混乱しないでください。複数パラメータを渡すことも<strong>可能</strong>です。<a href="#skinvars"><code>doSkinVar</code> メソッドの実装に関する詳細情報はこちら</a>。デフォルトではこのメソッドはなにも出力しません。</td> \r
- </tr>\r
- <tr>\r
- <td><code>doTemplateVar(&$item)</code></td>\r
- <td>基本的に <code>doSkinVar</code> と同じですが、今度は<em>テンプレート</em>内（<code>item\r
- header/body/footer</code> と <code>dateheader/footer</code>）での<code><%plugin(...)%></code> 変数からの呼び出しになります。デフォルトではこのメソッドはテンプレートをスキンタイプとみなして\r
- <code>doSkinVar</code> メソッドに処理を渡します。<a href="#templatevars"><code>doTemplateVar</code> メソッドの実装に関する詳細情報はこちら</a></td> \r
- </tr>\r
- <tr>\r
- <td><code>doTemplateCommentsVar(&$item, &$comment)</code></td>\r
- <td>(v2.0b) 基本的に <code>doSkinVar</code> と同じですが、今度は<em>テンプレート</em>内（コメント部分）での<code><%plugin(...)%></code> 変数からの呼び出しになります。デフォルトではこのメソッドはテンプレートをスキンタイプとみなして\r
- <code>doSkinVar</code> メソッドに処理を渡します。<a href="#templatevars"><code>doTemplateCommentsVar</code> \r
- メソッドの実装に関する詳細情報はこちら</a></td> \r
- </tr> \r
- <tr>\r
- <td><code>doAction($type)</code></td>\r
- <td>プラグインがユーザーインタラクションを求めたとき、 <code>action.php</code>を介してこのメソッドがそれを与えます。.\r
- これはNucleus自身が新しいコメントや投票を処理するのに使用するスクリプトです。正しいパラメータを用いることで、プラグインからの\r
- <code>doAction</code> メソッドを呼び出せます。<code>$type</code> はオプションのメッセージタイプに該当します。<code>doAction</code> メソッド内で、リクエストからの追加の変数にアクセスできます。デフォルトではこのメソッドがエラーメッセージをトリガーすると<code>'No\r
- Such Action'</code>という文字列を返します。<a href="#actions"><code>doAction</code> に関する詳細情報はこちら</a></td> \r
- </tr>\r
- <tr>\r
- <td><code>install()</code></td>\r
- <td>このメソッドはプラグインがインストールされた際に呼ばれます。データベース・テーブルの生成やプラグインオプションの生成などの初期化作業を行うことができます。デフォルトではこのメソッドは何もしません。</td>\r
- </tr>\r
- <tr>\r
- <td><code>unInstall()</code></td>\r
- <td>プラグインがアンインストールされた際に呼ばれます。この時点でデータベースに作られたプラグイン情報を消去すると良いです。デフォルトではこのメソッドは何もしません。</td>\r
- </tr>\r
- <tr>\r
- <td><code>getEventList()</code></td>\r
- <td>プラグインはイベント登録が可能です。イベントはNucleusが何かアクションを起こすたびに生成されます。たとえば、<code>AddItem</code> イベントは、このイベントを登録しているすべてのプラグインを呼び出します。呼び出されるメソッドは <code>event_AddItem($params)</code>になります。 <code>$params</code> パラメータは、例えば <code>AddItem</code> の <code>itemid</code> のような、情報フィールドを複数持つ連想配列です。デフォルトではどのイベントにも登録されていないことを示す空の配列を返します。<a href="#events">イベントに関する詳細情報\r
- はこちら</a></td> \r
- </tr>\r
- <tr>\r
- <td><code>getTableList()</code></td>\r
- <td>このメソッドはプラグインが生成したデータベース・テーブルの配列を返します。これはNucleusが提供するバックアップ機能で利用されるので、プラグインテーブルをバックアップに含めることができます。デフォルトでは空の配列を返します。</td>\r
- </tr>\r
- <tr>\r
- <td><code>hasAdminArea()</code></td>\r
- <td>プラグインが独自の管理エリアをもつ場合 1 を、そうでない場合 0 を返します。デフォルトでは <code>0</code> を返します。</td>\r
- </tr>\r
- <tr>\r
- <td><code>getPluginDep()</code></td>\r
- <td>(v3.2) プラグイン名の配列を返します。Nucleusはこれらのプラグインが前もってインストールされてない場合、プラグインのインストールを拒否します。デフォルトでは空の配列が返されます。<a href="#dependency">プラグイン依存に関する詳細情報はこちら</a></td>\r
- </tr>\r
-</table>\r
-\r
-<p>実装可能なメソッドの次は、<code>NucleusPlugin</code> クラスが提供する、再実装<strong>すべきでない</strong>幾つかの特殊メソッドです。これらはプラグイン内で、<code>$this->functionName()</code>シンタックスを利用して呼び出します。</p>\r
-\r
-<table summary="An overview of the auxiliary methods in the class NucleusPlugin. You should NOT redefine these">\r
- <caption>\r
- <code>NucleusPlugin</code> クラスの概要（再定義不可能なメソッド）\r
- </caption>\r
- <tr>\r
- <th>メソッド名</th>\r
- <th>説明</th>\r
- </tr>\r
- <tr>\r
- <td>\r
- <code>createOption(...)</code>\r
- <br /><code>createBlogOption(...)</code>(v2.2)\r
- <br /><code>createCategoryOption(...)</code>(v2.2)\r
- <br /><code>createMemberOption(...)</code>(v2.2)\r
- <br /><code>createItemOption(...)</code>(v3.2)\r
- </td>\r
- <td><a href="#options" title="More info on options">新しいオプションを生成します。</a></td> \r
- </tr>\r
- <tr>\r
- <td>\r
- <code>deleteOption(...)</code>\r
- <br /><code>deleteBlogOption(...)</code>(v2.2)\r
- <br /><code>deleteCategoryOption(...)</code>(v2.2)\r
- <br /><code>deleteMemberOption(...)</code>(v2.2)\r
- <br /><code>deleteItemOption(...)</code>(v3.2)\r
- </td>\r
- <td><a href="#options" title="More info on options">オプションを削除します。</a></td> \r
- </tr>\r
- <tr>\r
- <td>\r
- <code>setOption(...)</code>\r
- <br /><code>setBlogOption(...)</code>(v2.2)\r
- <br /><code>setCategoryOption(...)</code>(v2.2)\r
- <br /><code>setMemberOption(...)</code>(v2.2) \r
- <br /><code>setItemOption(...)</code>(v3.2)\r
- </td>\r
- <td><a href="#options" title="More info on options">オプションに値をセットします。</a></td> \r
- </tr>\r
- <tr>\r
- <td>\r
- <code>getOption(...)</code>\r
- <br /><code>getBlogOption(...)</code>(v2.2)\r
- <br /><code>getCategoryOption(...)</code>(v2.2)\r
- <br /><code>getMemberOption(...)</code>(v2.2) \r
- <br /><code>getItemOption(...)</code>(v3.2)\r
- </td>\r
- <td><a href="#options" title="More info on options">オプションの値を取得します。</a></td> \r
- </tr>\r
- <tr>\r
- <td>\r
- <code>getAllBlogOptions(...)</code>(v2.2)\r
- <br /><code>getAllCategoryOptions(...)</code>(v2.2)\r
- <br /><code>getAllMemberOptions(...)</code>(v2.2) \r
- <br /><code>getAllItemOptions(...)</code>(v3.2)\r
- </td>\r
- <td><a href="#options" title="More info on options">与えられたオプションにより、すべての値（コンテクストごとの一つの値）の連想配列を返します。</a></td> \r
- </tr> \r
- <tr>\r
- <td>\r
- <code>getBlogOptionTop(...)</code>(v3.2)\r
- <br /><code>getMemberOptionTop(...)</code>(v3.2)\r
- <br /><code>getCategoryOptionTop(...)</code>(v3.2)\r
- <br /><code>getItemOptionTop(...)</code>(v3.2)\r
- </td>\r
- <td><a href="#options" title="More info on options">与えられたオプションにより、すべての値のうちの最初の値を返します。</a></td>\r
- </tr>\r
- <tr>\r
- <td><code>getID()</code></td>\r
- <td>このプラグインのIDを返します（このIDはNucleus内部で利用されるものです）。</td> \r
- </tr>\r
- <tr>\r
- <td><code>getAdminURL()</code></td>\r
- <td>プラグインの管理エリアが置かれたURLを返します（そのような管理エリアがない場合は、この情報は無効です）。</td> \r
- </tr>\r
- <tr>\r
- <td><code>getDirectory()</code></td>\r
- <td>プラグインの追加ファイルが格納されたサーバーのファイルシステムのパスを返します（そのようなファイルがない場合は、この情報は無効です）。結果は"<code>.../nucleus/plugins/<em>plugname</em>/</code>"のようになります。</td> \r
- </tr>\r
- <tr>\r
- <td><code>getShortName()</code></td>\r
- <td>"NP_"部分を省き、全てを小文字にしたプラグインのクラス名を返します。この情報は <code>getAdminURL</code> と <code>getDirectory</code> で使用されます。</td> \r
- </tr>\r
-\r
-</table>\r
-\r
-<h1>スキン変数<a name="skinvars" href="#top" class="toplink"><img src="../icon-up.gif" width="15" height="15" alt="back to top" /></a></h1>\r
-\r
-<h2>解説</h2>\r
-\r
-<p>\r
-独自のスキン変数を生成し、<code><%plugin(<em>PlugName,parameters</em>)%></code> または <code><%PlugName(parameters)%></code>で呼び出すことが出来ます（すでに存在するスキン変数とかぶらない場合）。パラメータはカンマ区切りです。</p>\r
-\r
-<p>\r
-スキン変数を扱うには、<code>doSkinVar</code> メソッドを実装する必要があります。いくつかの例を以下に示します。</p>\r
-\r
-<pre class="example"><code>function doSkinVar($skinType)\r
-function doSkinVar($skinType, $param1, $param2)\r
-function doSkinVar($skinType, $skinVar, $param1, $param2)\r
-function doSkinVar($skinType, $skinVar, $param1 = 'default value')</code></pre>\r
-\r
-<ul>\r
- <li><code>$skinType</code> パラメータは、'index', 'item', 'archive', 'archivelist', 'member', 'error',\r
- 'search', 'imagepopup', <a href="#templatevars" title="Information on templatevars">'template'</a>のうちの一つを取ります</li>\r
- <li><code>$skinVar</code> は、スキン変数のタイプとして解釈される実質的に最初のパラメータになります（例：<code><%plugin(PlugName,VarType)%></code>）。</li>\r
- <li><code>doSkinVar()</code>（パラメータ無し）を使い、PHPファンクションの<code>func_get_args()</code>を用いてパラメータを取得することができます。引数の数の異なる、タイプの違うスキン変数を扱うときに便利です。</li>\r
-</ul>\r
-\r
-<h2>ノート</h2>\r
-\r
-<ul>\r
- <li>(v2.0b) グローバル変数としてパースされている <code>$currentSkinName</code> を使ってスキンの名前を取得できます。</li>\r
-</ul>\r
-\r
-\r
-\r
-\r
-<h1>テンプレート変数<a name="templatevars" href="#top" class="toplink"><img src="../icon-up.gif" width="15" height="15" alt="back to top" /></a></h1>\r
-\r
-<h2>解説</h2>\r
-\r
-<p>\r
-テンプレートプラグイン変数はスキンプラグイン変数と同様に働きますが以下の2点が異なります。</p>\r
-\r
-<ol>\r
- <li>スキン内ではなくテンプレート内から呼ばれます。</li>\r
- <li>$skinTypeパラメータを取りません。代わりに現在パースされているアイテムやコメントの情報付きの追加パラメータを取ります。\r
- <ul>\r
- <li><code>doTemplateVar</code> メソッドは <code>&$item</code> パラメータを取ります。</li>\r
- <li><code>doTemplateCommentsVar</code> メソッドは <code>&$item</code> と <code>&$comment</code> パラメータを取ります。</li>\r
- </ul>\r
- <strong>&マークに注意！</strong>\r
- </li>\r
-</ol>\r
- \r
-<p>テンプレート変数はスキン変数と同じ要領で呼ばれます（<code><%plugin(PlugName,parameters)%></code> または <code><%PlugName(parameters)%></code>）。</p>\r
-\r
-<p>\r
-デフォルトでは、全てのテンプレート変数は'<code>template</code>'を<code>skintype</code>パラメータとして、<code>doSkinVar</code> メソッドに渡ります。</p>\r
-\r
-<p>\r
-独自の実装を提供したい場合は、<code>doTemplateVar</code> メソッドや <code>doTemplateCommentsVar</code> メソッドを再定義する必要があります。<code>skintype</code>パラメータが無くなる以外はdoSkinVarと同様に働きます。</p>\r
-\r
-<pre class="example"><code>function doTemplateVar(&$item)\r
-function doTemplateVar(&$item, $param1, $param2)\r
-function doTemplateVar(&$item, $type, $param1, $param2)\r
-function doTemplateVar(&$item, $type, $param1 = 'default value')\r
-function doTemplateCommentsVar(&$item, &$comment)\r
-function doTemplateCommentsVar(&$item, &$comment, $param1, $param2)\r
-function doTemplateCommentsVar(&$item, &$comment, $type, $param1, $param2)\r
-function doTemplateCommentsVar(&$item, &$comment, $type, $param1 = 'default value')</code></pre>\r
-\r
-<h2>ノート</h2>\r
-\r
-<ul>\r
- <li>(v2.0b) グローバル変数として内部で利用される <code>$currentSkinName</code> を使ってテンプレートの名前を取得できます。</li>\r
-</ul>\r
-\r
-\r
-\r
-\r
-<h1>アクション<a name="actions" href="#top" class="toplink"><img src="../icon-up.gif" width="15" height="15" alt="back to top" /></a></h1>\r
-\r
-<p>プラグインは <code>action.php</code> を通してアクションを行うことができ、同様のスクリプトがコメントや投票の受け取りにも使用されてます。GETまたはPOSTのどちらかを通して呼び出せます。必要なパラメータは\r
-<code>action</code>（'plugin'と指定）、<code>name</code>（プラグイン名）、<code>type</code>（リクエストされたアクションの種類）です。</p>\r
-\r
-<p>これらのアクションを有効にするために、<code>doAction($actionType)</code> メソッドをプラグイン内で実装する必要があります。リクエストからの追加パラメータは\r
-<code>requestVar('<em>name</em>')</code> で取得できます（<code>requestVar</code> はPHPが付加する magic_quotes_gpc に配慮しています）。</p>\r
-\r
-<p>\r
-<code>doAction</code> メソッドが文字列を返すとき、エラーとして解釈され、エラーメッセージが表示されます。</p>\r
-\r
-\r
-\r
-\r
-\r
-\r
-<h1>イベント<a name="events" href="#top" class="toplink"><img src="../icon-up.gif" width="15" height="15" alt="back to top" /></a></h1>\r
-\r
-<p>\r
-Nucleusプラグインはなにか重要なことが起きたときに発生するイベントに登録可能です。プラグインはイベント発生の際にアクションを実行したり、テキストを出力したりできます。</p>\r
-\r
-<h2>例</h2>\r
-\r
-<p>\r
-下記は <code>PreAddComment</code> イベント（blogにコメントが追加される直前に生成されるイベント）にプラグインが登録する例です。</p>\r
-\r
-<pre class="example"><code>class NP_Acronyms extends NucleusPlugin {\r
- ...\r
- function getEventList() { return array('PreAddComment'); }\r
- ...\r
- function event_PreAddComment(&$data) {\r
- // 頭字語 HTML を置き換え\r
- $data['comment']['body'] = \r
- strreplace('HTML',\r
- '<acronym title="HyperText Markup Language">HTML</acronym>',\r
- $data['comment']['body']);\r
- }\r
-}\r
-</code></pre>\r
-\r
-<p>このプラグインはコメント中の'HTML'というテキストを'<code><acronym title="HyperText\r
-Markup Language">HTML</acronym></code>'に置き換えます。acronymタグはHTMLタグで、頭字語についての追加情報を提供します。</p>\r
-\r
-<h2>イベント登録の仕方</h2>\r
-\r
-<p>イベント登録に必要なステップは以下になります。</p>\r
-\r
-<ol>\r
- <li><code>getEventList</code> メソッドから返る配列にイベント名を追加します。</li>\r
- <li><code>event_EventName($data)</code> という形でメソッドを生成し、この中でイベントを処理します。</li>\r
-</ol>\r
-\r
-<p>複数のプラグインが同じイベントに登録できます。管理エリアのプラグインリストの順序に従ってプラグインに通知が行きます。リストの上にあるプラグインほど早く通知されます。</p>\r
-\r
-<h2>パラメータ</h2>\r
-\r
-<p><code>event_EventName</code> メソッドはひとつだけ <code>$data</code> パラメータを持ち、それはイベントごとに内容が異なります。これは連想配列です。この連想配列に渡されたオブジェクトや配列は<strong>参照形式</strong>で渡されるため、これらに加えた変更は記憶されます。</p>\r
-\r
-<p>以下のイベントリストは、パラメータ変更がNucleusに知られるかどうかを示すために色を使い分けています。</p>\r
-\r
-<ul>\r
- <li><var class="ref">参照渡し（緑）</var>: この種のパラメータに変更を加えるとNucleusに知られます。</li>\r
- <li><var class="ro">値渡し（赤）</var>: プラグインイベントハンドラに渡される前に値がコピーされます。これらの変数への変更は自動的に破棄されます。.</li>\r
-</ul>\r
-\r
-<p>パラメータとして渡されるオブジェクトは<var class="obj">object</var>.として示されます。ほとんどのオブジェクトは参照渡しで、<var class="obj ref">object\r
-by ref</var>のように示されます。</p>\r
-\r
-<h2>イベントリスト</h2>\r
-\r
-<table summary="An overview of events to which a Nucleus Plugin can subscribe, and what parameters are passed along to the method that handles the event">\r
- <caption>\r
- プラグインが登録できるイベント</caption>\r
- <tr>\r
- <th>名前</th>\r
- <th>いつ</th>\r
- <th>パラメータ</th>\r
- </tr>\r
- <tr>\r
- <td>PreSkinParse</td>\r
- <td>スキンのパースの直前</td>\r
- <td><dl>\r
- <dt class="obj ref">skin</dt>\r
- <dd>パースする<code>SKIN</code>オブジェクト</dd>\r
- <dt class="ro">type</dt>\r
- <dd>スキンタイプ（'index', 'item', 'archive', 'archivelist',\r
- 'member', 'error', 'search', 'imagepopup', 'fileparser'のいずれか）</dd>\r
- </dl></td> \r
- </tr>\r
- <tr>\r
- <td>PostSkinParse</td>\r
- <td>スキンのパースの直後</td>\r
- <td><dl>\r
- <dt class="obj ref">skin</dt>\r
- <dd>パースする<code>SKIN</code>オブジェクト</dd>\r
- <dt class="ro">type</dt>\r
- <dd>スキンタイプ（'index', 'item', 'archive', 'archivelist', 'member', 'error', 'search',\r
- 'imagepopup', 'fileparser'のいずれか）</dd>\r
- </dl></td> \r
- </tr>\r
- <tr>\r
- <td>PreItem</td>\r
- <td>アイテムのパース前、ただしアイテムヘッダーのパース後</td>\r
- <td><dl>\r
- <dt class="ref obj">blog</dt>\r
- <dd><code>BLOG</code> オブジェクト</dd>\r
- <dt class="ref obj">item</dt>\r
- <dd>アイテムデータを持つオブジェクト</dd>\r
- </dl></td> \r
- </tr>\r
- <tr>\r
- <td>PostItem</td>\r
- <td>アイテムのパース後、ただしアイテムフッターのパース前</td>\r
- <td><dl>\r
- <dt class="ref obj">blog</dt>\r
- <dd><code>BLOG</code> オブジェクト</dd>\r
- <dt class="ref obj">item</dt>\r
- <dd>アイテムデータを持つオブジェクト</dd>\r
- </dl></td> \r
- </tr>\r
- <tr>\r
- <td>PreComment</td>\r
- <td>コメントの表示前</td>\r
- <td><dl>\r
- <dt class="ref">comment</dt>\r
- <dd>コメントデータを持つ連想配列</dd>\r
- </dl></td> \r
- </tr>\r
- <tr>\r
- <td>PostComment</td>\r
- <td>コメントの表示後</td>\r
- <td><dl>\r
- <dt class="ref">comment</dt>\r
- <dd>コメントデータを持つ連想配列</dd>\r
- </dl></td> \r
- </tr>\r
- <tr>\r
- <td>PreDateHead</td>\r
- <td>日付ヘッダーのパース前</td>\r
- <td><dl>\r
- <dt class="obj ref">blog</dt>\r
- <dd><code>BLOG</code> オブジェクト</dd>\r
- <dt class="ro">timestamp</dt>\r
- <dd>日付ヘッダーのタイムスタンプ</dd>\r
- </dl></td> \r
- </tr>\r
- <tr>\r
- <td>PostDateHead</td>\r
- <td>日付ヘッダーのパース後</td>\r
- <td><dl>\r
- <dt class="obj ref">blog</dt>\r
- <dd><code>BLOG</code> オブジェクト</dd>\r
- <dt class="ro">timestamp</dt>\r
- <dd>日付ヘッダーのタイムスタンプ</dd>\r
- </dl></td> \r
- </tr>\r
- <tr>\r
- <td>PreDateFoot</td>\r
- <td>日付フッターのパース前</td>\r
- <td><dl>\r
- <dt class="ref obj">blog</dt>\r
- <dd><code>BLOG</code> オブジェクト</dd>\r
- <dt class="ro">timestamp</dt>\r
- <dd>日付フッターのタイムスタンプ</dd>\r
- </dl></td> \r
- </tr>\r
- <tr>\r
- <td>PostDateFoot</td>\r
- <td>日付フッターのパース後</td>\r
- <td><dl>\r
- <dt class="ref obj">blog</dt>\r
- <dd><code>BLOG</code> オブジェクト</dd>\r
- <dt class="ro">timestamp</dt>\r
- <dd>日付フッターのタイムスタンプ</dd>\r
- </dl></td> \r
- </tr> \r
- <tr>\r
- <td>LoginSuccess</td>\r
- <td>ログイン成功後</td>\r
- <td><dl>\r
- <dt class="obj ref">member</dt>\r
- <dd><code>MEMBER</code> オブジェクト</dd>\r
- </dl></td> \r
- </tr>\r
- <tr>\r
- <td>LoginFailed</td>\r
- <td>ログイン失敗後</td>\r
- <td><dl>\r
- <dt class="ro">username</dt>\r
- <dd>ログイン時に使われたユーザー名</dd>\r
- </dl></td> \r
- </tr>\r
- <tr>\r
- <td>Logout</td>\r
- <td>ログアウト後</td>\r
- <td><dl>\r
- <dt class="ro">username</dt>\r
- <dd>ログアウト時のユーザー名</dd>\r
- </dl></td> \r
- </tr>\r
- <tr>\r
- <td>PreBlogContent</td>\r
- <td>blogの内容がスキン変数を通して挿入される前</td>\r
- <td><dl>\r
- <dt class="obj ref">blog</dt>\r
- <dd><code>BLOG</code> オブジェクト</dd>\r
- <dt class="ro">type</dt>\r
- <dd>呼び出されたスキン変数 ('blog', 'otherblog', 'archive', 'archivelist', 'item', 'searchresults',\r
- 'othersearchresults', 'categorylist', 'otherarchive', 'otherarchivelist')</dd>\r
- </dl></td> \r
- </tr>\r
- <tr>\r
- <td>PostBlogContent</td>\r
- <td>blogの内容がスキン変数を通して挿入された後</td>\r
- <td><dl>\r
- <dt class="obj ref">blog</dt>\r
- <dd><code>BLOG</code> オブジェクト</dd>\r
- <dt class="ro">type</dt>\r
- <dd>呼び出されたスキン変数 ('blog', 'otherblog', 'archive', 'archivelist', 'item', 'searchresults',\r
- 'othersearchresults', 'categorylist', 'otherarchive', 'otherarchivelist')</dd>\r
- </dl></td> \r
- </tr>\r
- <tr>\r
- <td>PreAddComment</td>\r
- <td>コメントがデータベースに追加される前</td>\r
- <td><dl>\r
- <dt class="ref">comment</dt>\r
- <dd>コメントデータ（連想配列）</dd>\r
- </dl></td> \r
- </tr>\r
- <tr>\r
- <td>PostAddComment</td>\r
- <td>コメントがデータベースに追加された後</td>\r
- <td><dl>\r
- <dt class="ref">comment</dt>\r
- <dd>コメントデータ（連想配列）</dd>\r
- <dt class="ref">commentid</dt>\r
- <dd>コメントのID</dd>\r
- </dl></td> \r
- </tr>\r
- <tr>\r
- <td>PostRegister</td>\r
- <td>新規ユーザーの登録後</td>\r
- <td><dl>\r
- <dt class="obj ref">member</dt>\r
- <dd>新しい<code>MEMBER</code> オブジェクト</dd>\r
- </dl></td> \r
- </tr>\r
- <tr>\r
- <td>PostAddItem</td>\r
- <td>アイテムがデータベースに追加された後</td>\r
- <td><dl>\r
- <dt class="ro">itemid</dt>\r
- <dd>データベースに出来た新しい itemid</dd>\r
- </dl></td> \r
- </tr>\r
- <tr>\r
- <td>PreAddItem</td>\r
- <td>アイテムがデータベースに追加される直前</td>\r
- <td><dl>\r
- <dt class="ref">title</dt>\r
- <dd>タイトル</dd>\r
- <dt class="ref">body</dt>\r
- <dd>本文</dd>\r
- <dt class="ref">more</dt>\r
- <dd>拡張テキスト</dd>\r
- <dt class="ref obj">blog</dt>\r
- <dd><code>BLOG</code> オブジェクト</dd>\r
- <dt class="ref">authorid</dt>\r
- <dd>執筆者ID</dd>\r
- <dt class="ref">timestamp</dt>\r
- <dd>UNIX タイムスタンプ</dd>\r
- <dt class="ref">closed</dt>\r
- <dd>1 （コメント不可） or 0 （コメント可）</dd>\r
- <dt class="ref">draft</dt>\r
- <dd>1 （ドラフト） or 0 （非ドラフト）</dd>\r
- <dt class="ref">catid</dt>\r
- <dd>カテゴリーID</dd>\r
- </dl></td> \r
- </tr> \r
- <tr>\r
- <td>PreUpdateItem</td>\r
- <td>データベースにあるアイテムが更新される直前</td>\r
- <td><dl>\r
- <dt class="ro">itemid</dt>\r
- <dd>アイテム ID</dd>\r
- <dt class="ref">title</dt>\r
- <dd>タイトル</dd>\r
- <dt class="ref">body</dt>\r
- <dd>本文</dd>\r
- <dt class="ref">more</dt>\r
- <dd>拡張テキスト</dd>\r
- <dt class="ref obj">blog</dt>\r
- <dd><code>BLOG オブジェクト</code> object</dd>\r
- <dt class="ref">closed</dt>\r
- <dd>1 （コメント不可） or 0 （コメント可）</dd>\r
- <dt class="ref">catid</dt>\r
- <dd>カテゴリーID</dd>\r
- </dl></td> \r
- </tr>\r
- <tr>\r
- <td>PrepareItemForEdit</td>\r
- <td>アイテムをデータベースから取得した直後で、編集のためにユーザーに表示される前</td>\r
- <td><dl>\r
- <dt class="ref">item</dt>\r
- <dd>アイテムデータを持つ連想配列</dd>\r
- </dl></td> \r
- </tr>\r
- <tr>\r
- <td>PreUpdateComment</td>\r
- <td>コメントが更新され、データベースに保存される直前</td>\r
- <td><dl>\r
- <dt class="ref">body</dt>\r
- <dd>コメント本文</dd>\r
- </dl></td> \r
- </tr>\r
- <tr>\r
- <td>PrepareCommentForEdit</td>\r
- <td>コメントをデータベースから取得した直後で、編集のためにユーザーに表示される前</td>\r
- <td><dl>\r
- <dt class="ref">comment</dt>\r
- <dd>コメントデータ（連想配列）</dd>\r
- </dl></td> \r
- </tr>\r
- <tr>\r
- <td>PrePluginOptionsEdit</td>\r
- <td>\r
- (v2.0b) 'プラグインオプションの編集'フォームが生成される前\r
- <br />(v2.2) パラメータ追加\r
- <br />(v3.2) 各オプションにパラメータ追加\r
- </td>\r
- <td><dl>\r
- <dt class="ro">context</dt>\r
- <dd>(v2.2) <code>global</code>, <code>blog</code>, <code>member</code>, <code>item</code>, <code>category</code>のいずれか</dd>\r
- <dt class="ref">options</dt>\r
- <dd>次のインデックスをもつ連想配列： <code>name</code>, <code>value</code>, <code>oid</code>, <code>description</code>, <code>type</code>, <code>typeinfo</code>, <code>contextid</code>, <code>extra</code> 。追加オプションをここに加えることも可能（それらで何かの処理をするときはPostPluginOptionsUpdateの記述も必要）<br />\r
- <code>extra</code>フィールドを用いて、オプションに追加HTML（たとえばフォームのコントロール）を追加できます。もしそうする場合、 <code>extra</code> に追加する前に <code>pid</code> と <code>getID()</code> を比較し、さらに <code>name</code> をチェックすべきです。</dd>\r
- <dt class="ro">plugid</dt>\r
- <dd>プラグイン ID （これが気になるなら、<code>GetID()</code>を見ると理解できる）（コンテクストがglobalのときのみ存在）</dd>\r
- <dt class="ro">contextid</dt>\r
- <dd>コンテクスト ID (blogid, memberid, catid, itemid コンテクストによる)</dd>\r
- </dl></td> \r
- </tr> \r
- <tr>\r
- <td>PrePluginOptionsUpdate</td>\r
- <td>\r
- (v3.2) プラグインオプションが更新される前。（このイベントを使ってオプションの新しい値を評価したり変更したりできます）\r
- </td>\r
- <td><dl>\r
- <dt class="ro">context</dt>\r
- <dd>(v2.2) <code>global</code>, <code>member</code>, <code>blog</code>, <code>item</code>, <code>category</code>のいずれか</dd>\r
- <dt class="ro">plugid</dt>\r
- <dd>プラグイン ID （これが気になるなら、<code>GetID()</code>を見ると理解できる）</dd>\r
- <dt class="ro">optionname</dt>\r
- <dd>オプション名</dd>\r
- <dt class="ro">contextid</dt>\r
- <dd>コンテクスト ID (blogid, memberid, catid, itemid コンテクストによる)</dd>\r
- <dt class="ref">value</dt>\r
- <dd>そのオプションの新しい値</dd>\r
- </dl></td>\r
- </tr>\r
- <tr>\r
- <td>PostPluginOptionsUpdate</td>\r
- <td>\r
- (v2.0b) プラグインオプションの更新後<br />\r
- (v2.2) コンテクストによって異なるパラメータ</td>\r
- <td><dl>\r
- <dt class="ro">context</dt>\r
- <dd>(v2.2) <code>global</code>, <code>member</code>, <code>blog</code>, <code>item</code>, <code>category</code>のいずれか</dd>\r
- <dt class="ro">plugid</dt>\r
- <dd>プラグイン ID （これが気になるなら、<code>GetID()</code>を見ると理解できる）（globalコンテクスト）</dd>\r
- <dt class="ro">blogid</dt>\r
- <dd>(v2.2) blog ID (blog コンテクスト)</dd> \r
- <dt class="ref obj">blog</dt>\r
- <dd>(v2.2) BLOG オブジェクト (blog コンテクスト)</dd> \r
- <dt class="ro">memberid</dt>\r
- <dd>(v2.2) member ID (member コンテクスト)</dd> \r
- <dt class="ref obj">member</dt>\r
- <dd>(v2.2) MEMBER オブジェクト (member コンテクスト)</dd> \r
- <dt class="ro">catid</dt>\r
- <dd>(v2.2) category ID (category コンテクスト)</dd> \r
- <dt class="ro">itemid</dt>\r
- <dd>(v2.2) item ID (item コンテクスト)</dd>\r
- <dt class="ref obj">member</dt>\r
- <dd>(v2.2) ITEM オブジェクト (item コンテクスト)</dd>\r
- </dl></td> \r
- \r
- </tr> \r
- <tr>\r
- <td>PostAuthentication</td>\r
- <td>(v2.0b) ログイン処理の完了後。ページリクエストごとに発生</td>\r
- <td><dl>\r
- <dt class="ro">loggedIn</dt>\r
- <dd><code>$member->isLoggedIn()</code>の戻り値</dd>\r
- </dl></td> \r
- </tr> \r
- <tr>\r
- <td>PreAddItemForm</td>\r
- <td>(v2.0b) アイテム追加フォーム（ブックマークレットまたは管理エリア）が生成される直前</td>\r
- <td><dl>\r
- <dt class="ref">contents</dt>\r
- <dd>連想配列への参照。そのうちの'title',\r
- 'body', 'more'にはフォームフィールドへの初期値を与えることができます。複数のプラグイン間でこれらの値の変更を避けるには、処理後に'hasBeenSet'の値を1にセットします（かつ処理前にこの値をチェックするようにします）</dd>\r
- <dt class="ref obj">blog</dt>\r
- <dd><code>BLOG</code> オブジェクトへの参照</dd>\r
- </dl></td> \r
- </tr> \r
- <tr>\r
- <td>AddItemFormExtras</td>\r
- <td>(v2.0b) アイテム追加ページまたはブックマークレット内部のどこか。<code>template</code> ファイルの類を別に用意しなくても、ここでプラグインがカスタムフィールドを追加できる。</td>\r
- <td><dl>\r
- <dt class="ref obj">blog</dt>\r
- <dd><code>BLOG</code> オブジェクトへの参照</dd>\r
- </dl></td> \r
- </tr> \r
- <tr>\r
- <td>EditItemFormExtras</td>\r
- <td>\r
- (v2.0b) アイテム編集ページまたはブックマークレット内部のどこか。<code>template</code> ファイルの類を別に用意しなくても、ここでプラグインがカスタムフィールドを追加できる。<br />\r
- <br /> \r
- あまり多くのデータを追加しないこと。また以下のように<strong>正しいXHTML</strong>を生成してください。 <pre class="example"><code><h3>プラグイン名</h3>\r
-<p>追加フォームの内容</p></code></pre>\r
- このようにして、正しい構造を保ちつつ複数のプラグインがオプションを保持できます。またフィールド名の重複を避けるためにプレフィックスを用いてください（例 <code>plug_tb_url</code>）。</td>\r
- <td><dl>\r
- <dt class="ref obj">blog</dt>\r
- <dd><code>BLOG</code> オブジェクトへの参照</dd>\r
- <dt class="ro">variables</dt>\r
- <dd>\r
- (read-only) 編集されるアイテムに関する全ての情報を持つ連想配列： 'itemid',\r
- 'draft', 'closed', 'title', 'body', 'more', 'author', 'authorid',\r
- 'timestamp', 'karmapos', 'karmaneg', 'catid'\r
- </dd> \r
- <dt class="ro">itemid</dt>\r
- <dd>アイテム IDへのショートカット</dd>\r
- </dl></td> \r
- </tr> \r
- <tr>\r
- <td>BlogSettingsFormExtras</td>\r
- <td>(v2.0) blog設定ページにフォームを追加可能<br /><br /> \r
- あまり多くのデータを追加しないこと。また以下のように<strong>正しいXHTML</strong>を生成してください。 <pre class="example"><code><h4>プラグイン名</h4>\r
-<form method="post" action="..."><p>\r
-追加フォームの内容</p></form></code></pre>\r
- このようにして、正しい構造を保ちつつ複数のプラグインがオプションを保持できます。またフィールド名の重複を避けるためにプレフィックスを用いてください（例 <code>plug_tb_url</code>）。</td>\r
- <td><dl>\r
- <dt class="obj ref">blog</dt>\r
- <dd><code>BLOG</code> オブジェクトへの参照</dd>\r
- </dl></td> \r
- </tr>\r
- <tr>\r
- <td>PreDeleteItem</td>\r
- <td>(v2.0) アイテムがデータベースから削除される直前</td>\r
- <td><dl>\r
- <dt class="ro">itemid</dt>\r
- <dd>削除されるアイテムID</dd>\r
- </dl></td> \r
- </tr>\r
- <tr>\r
- <td>PostDeleteItem</td>\r
- <td>(v2.0) アイテムがデータベースから削除された直後</td>\r
- <td><dl>\r
- <dt class="ro">itemid</dt>\r
- <dd>削除されたアイテムID</dd>\r
- </dl></td> \r
- </tr>\r
- <tr>\r
- <td>PreDeleteCategory</td>\r
- <td>(v2.0) カテゴリーがデータベースから削除される直前</td>\r
- <td><dl>\r
- <dt class="ro">catid</dt>\r
- <dd>削除されるカテゴリー ID</dd>\r
- </dl></td> \r
- </tr>\r
- <tr>\r
- <td>PostDeleteCategory</td>\r
- <td>(v2.0) カテゴリーがデータベースから削除された直後</td>\r
- <td><dl>\r
- <dt class="ro">catid</dt>\r
- <dd>削除されたカテゴリー ID</dd>\r
- </dl></td> \r
- </tr> \r
- <tr>\r
- <td>PreDeleteBlog</td>\r
- <td>(v2.0) blogがデータベースから削除される直前</td>\r
- <td><dl>\r
- <dt class="ro">blogid</dt>\r
- <dd>削除されるblogID</dd>\r
- </dl></td> \r
- </tr>\r
- <tr>\r
- <td>PostDeleteBlog</td>\r
- <td>(v2.0) blogがデータベースから削除された直後</td>\r
- <td><dl>\r
- <dt class="ro">blogid</dt>\r
- <dd>削除されたblogID</dd>\r
- </dl></td> \r
- </tr> \r
- <tr>\r
- <td>PreDeleteMember</td>\r
- <td>(v2.0) メンバーがデータベースから削除される直前</td>\r
- <td><dl>\r
- <dt class="ref obj">member</dt>\r
- <dd><code>削除されるメンバーに関するMEMBER</code> オブジェクトへの参照</dd>\r
- </dl></td> \r
- </tr>\r
- <tr>\r
- <td>PostDeleteMember</td>\r
- <td>(v2.0) メンバーがデータベースから削除された直後</td>\r
- <td><dl>\r
- <dt class="ref obj">member</dt>\r
- <dd><code>削除されるメンバーに関するMEMBER</code> オブジェクトへの参照</dd>\r
- </dl></td> \r
- </tr> \r
- <tr>\r
- <td>PreDeleteTeamMember</td>\r
- <td>(v2.0) メンバーがweblogチームから削除される直前</td>\r
- <td><dl>\r
- <dt class="ref obj">member</dt>\r
- <dd><code>MEMBER</code> オブジェクトへの参照</dd>\r
- <dt class="ro">blogid</dt>\r
- <dd>blogID</dd>\r
- </dl></td> \r
- </tr>\r
- <tr>\r
- <td>PostDeleteTeamMember</td>\r
- <td>(v2.0) メンバーがweblogチームから削除された直後</td>\r
- <td><dl>\r
- <dt class="ref obj">member</dt>\r
- <dd><code>MEMBER</code> オブジェクトへの参照</dd>\r
- <dt class="ro">blogid</dt>\r
- <dd>blogID</dd>\r
- </dl></td> \r
- </tr>\r
- <tr>\r
- <td>PreDeleteComment</td>\r
- <td>(v2.0) コメントがデータベースから削除される直前</td>\r
- <td><dl>\r
- <dt class="ro">commentid</dt>\r
- <dd>削除されるコメントID</dd>\r
- </dl></td> \r
- </tr>\r
- <tr>\r
- <td>PostDeleteComment</td>\r
- <td>(v2.0) コメントがデータベースから削除された直後</td>\r
- <td><dl>\r
- <dt class="ro">commentid</dt>\r
- <dd>削除されたコメントID</dd>\r
- </dl></td> \r
- </tr> \r
- <tr>\r
- <td>ActionLogCleared</td>\r
- <td>(v2.0) アクションログが消去された後</td>\r
- <td>なし</td> \r
- </tr>\r
- <tr>\r
- <td>PreDeleteTemplate</td>\r
- <td>(v2.0) テンプレートがデータベースから削除される直前</td>\r
- <td><dl>\r
- <dt class="ro">templateid</dt>\r
- <dd>削除されるテンプレートID</dd>\r
- </dl></td> \r
- </tr>\r
- <tr>\r
- <td>PostDeleteTemplate</td>\r
- <td>(v2.0) テンプレートがデータベースから削除された直後</td>\r
- <td><dl>\r
- <dt class="ro">templateid</dt>\r
- <dd>削除されたテンプレートID</dd>\r
- </dl></td> \r
- </tr> \r
- <tr>\r
- <td>PreDeleteSkin</td>\r
- <td>(v2.0) スキンがデータベースから削除される直前</td>\r
- <td><dl>\r
- <dt class="ro">skinid</dt>\r
- <dd>削除されるスキンID</dd>\r
- </dl></td> \r
- </tr>\r
- <tr>\r
- <td>PostDeleteSkin</td>\r
- <td>(v2.0) スキンがデータベースから削除された直後</td>\r
- <td><dl>\r
- <dt class="ro">skinid</dt>\r
- <dd>削除されたスキンID</dd>\r
- </dl></td> \r
- </tr> \r
- <tr>\r
- <td>PreDeletePlugin</td>\r
- <td>(v2.0) プラグインがデータベースから削除される直前</td>\r
- <td><dl>\r
- <dt class="ro">plugid</dt>\r
- <dd>削除されるプラグインID</dd>\r
- </dl></td> \r
- </tr>\r
- <tr>\r
- <td>PostDeletePlugin</td>\r
- <td>(v2.0) プラグインがデータベースから削除された直後</td>\r
- <td><dl>\r
- <dt class="ro">plugid</dt>\r
- <dd>削除されたプラグインID</dd>\r
- </dl></td> \r
- </tr> \r
- <tr>\r
- <td>PreDeleteBan</td>\r
- <td>(v2.0) 禁止IPがデータベースから削除される直前</td>\r
- <td><dl>\r
- <dt class="ro">blogid</dt>\r
- <dd>禁止IPが削除されるblogのID</dd>\r
- <dt class="ro">iprange</dt>\r
- <dd>禁止されたIPレンジ</dd> \r
- </dl></td> \r
- </tr>\r
- <tr>\r
- <td>PostDeleteBan</td>\r
- <td>(v2.0) 禁止IPがデータベースから削除された直後</td>\r
- <td><dl>\r
- <dt class="ro">blogid</dt>\r
- <dd>禁止IPが削除されたblogのID</dd>\r
- <dt class="ro">iprange</dt>\r
- <dd>禁止されたIPレンジ</dd> \r
- </dl></td> \r
- </tr> \r
- <tr>\r
- <td>PreAddCategory</td>\r
- <td>(v2.0) 新しいカテゴリーがデータベースに生成される直前</td>\r
- <td><dl>\r
- <dt class="ref obj">blog</dt>\r
- <dd><code>BLOG</code> オブジェクトの参照</dd>\r
- <dt class="ref">name</dt>\r
- <dd>新しいカテゴリー名</dd> \r
- <dt class="ref">description</dt>\r
- <dd>新しいカテゴリーの説明</dd>\r
- </dl></td> \r
- </tr>\r
- <tr>\r
- <td>PostAddCategory</td>\r
- <td>(v2.0) 新しいカテゴリーがデータベースに生成された直後</td>\r
- <td><dl>\r
- <dt class="ref obj">blog</dt>\r
- <dd><code>BLOG</code> オブジェクトへの参照</dd>\r
- <dt class="ro">name</dt>\r
- <dd>新しいカテゴリー名</dd> \r
- <dt class="ro">description</dt>\r
- <dd>新しいカテゴリーの説明</dd>\r
- <dt class="ro">catid</dt>\r
- <dd>新しいカテゴリー ID</dd> \r
- </dl></td> \r
- </tr>\r
- <tr>\r
- <td>PreAddBlog</td>\r
- <td>(v2.0) 新しいblogが生成される直前</td>\r
- <td><dl>\r
- <dt class="ref">name</dt>\r
- <dd>新しい blog名</dd>\r
- <dt class="ref">shortname</dt>\r
- <dd>新しい blogの短縮名</dd>\r
- <dt class="ref">timeoffset</dt>\r
- <dd>新しい blogのタイムオフセット</dd>\r
- <dt class="ref">description</dt>\r
- <dd>新しい blogの説明</dd>\r
- <dt class="ref">defaultskin</dt>\r
- <dd>新しいblogのデフォルトスキンのID</dd>\r
- </dl></td> \r
- </tr>\r
- <tr>\r
- <td>PostAddBlog</td>\r
- <td>(v2.0) 新しいblogが生成された直後</td>\r
- <td><dl>\r
- <dt class="ref obj">blog</dt>\r
- <dd>新しい<code>BLOG</code> オブジェクト</dd>\r
- </dl></td> \r
- </tr>\r
- <tr>\r
- <td>PreAddPlugin</td>\r
- <td>(v2.0) プラグインが追加される直前</td>\r
- <td><dl>\r
- <dt class="ref">file</dt>\r
- <dd>新しいプラグインのファイル名</dd>\r
- </dl></td> \r
- </tr>\r
- <tr>\r
- <td>PostAddPlugin</td>\r
- <td>(v2.0) プラグインが追加された直後</td>\r
- <td><dl>\r
- <dt class="ref obj">plugin</dt>\r
- <dd>新しく追加されたプラグインのオブジェクト</dd>\r
- </dl></td> \r
- </tr>\r
- <tr>\r
- <td>PreAddTeamMember</td>\r
- <td>(v2.0) メンバーがblogチームに追加される直前</td>\r
- <td><dl>\r
- <dt class="ref obj">blog</dt>\r
- <dd><code>BLOG</code> オブジェクト</dd>\r
- <dt class="ref obj">member</dt>\r
- <dd><code>MEMBER</code> オブジェクト</dd>\r
- <dt class="ref">admin</dt>\r
- <dd>新しく追加されたメンバーが管理権限を持っているかどうかを示すブール値</dd>\r
- </dl></td> \r
- </tr>\r
- <tr>\r
- <td>PostAddTeamMember</td>\r
- <td>(v2.0) メンバーがblogチームに追加された直後</td>\r
- <td><dl>\r
- <dt class="ref obj">blog</dt>\r
- <dd><code>BLOG</code> オブジェクト</dd>\r
- <dt class="ref obj">member</dt>\r
- <dd><code>MEMBER</code> オブジェクト</dd>\r
- <dt class="ro">admin</dt>\r
- <dd>新しく追加されたメンバーが管理権限を持っているかどうかを示すブール値</dd>\r
- </dl></td> \r
- </tr>\r
- <tr>\r
- <td>PreAddTemplate</td>\r
- <td>(v2.0) 新しいテンプレートが生成される直前（注：テンプレートが複製されたときも呼ばれる）</td>\r
- <td><dl>\r
- <dt class="ref">name</dt>\r
- <dd>新しいテンプレート名</dd>\r
- <dt class="ref">description</dt>\r
- <dd>新しいテンプレートの説明</dd>\r
- </dl></td> \r
- </tr>\r
- <tr>\r
- <td>PostAddTemplate</td>\r
- <td>(v2.0) 新しいテンプレートが生成された直後</td>\r
- <td><dl>\r
- <dt class="ro">name</dt>\r
- <dd>新しいテンプレート名</dd>\r
- <dt class="ro">description</dt>\r
- <dd>新しいテンプレートの説明</dd>\r
- <dt class="ro">templateid</dt>\r
- <dd>新しいテンプレートID</dd>\r
- </dl></td> \r
- </tr> \r
- <tr>\r
- <td>PreAddSkin</td>\r
- <td>(v2.0) 新しいスキンが生成される直前（注：スキンが複製されたときも呼ばれる）</td>\r
- <td><dl>\r
- <dt class="ref">name</dt>\r
- <dd>新しいスキン名</dd>\r
- <dt class="ref">description</dt>\r
- <dd>新しいスキン名の説明</dd>\r
- <dt class="ref">type</dt>\r
- <dd>スキンのコンテントタイプ</dd>\r
- <dt class="ref">includeMode</dt>\r
- <dd>新しいスキンのインクルードモード</dd>\r
- <dt class="ref">includePrefix</dt>\r
- <dd>新しいスキンのインクルードプレフィックス</dd>\r
- </dl></td> \r
- </tr>\r
- <tr>\r
- <td>PostAddSkin</td>\r
- <td>(v2.0) 新しいスキンが生成された直後</td>\r
- <td><dl>\r
- <dt class="ro">name</dt>\r
- <dd>新しいスキン名</dd>\r
- <dt class="ro">description</dt>\r
- <dd>新しいスキンの説明</dd>\r
- <dt class="ro">type</dt>\r
- <dd>スキンのコンテントタイプ</dd>\r
- <dt class="ro">includeMode</dt>\r
- <dd>新しいスキンのインクルードモード</dd>\r
- <dt class="ro">includePrefix</dt>\r
- <dd>新しいスキンのインクルードプレフィックス</dd>\r
- <dt class="ro">skinid</dt>\r
- <dd>新しいスキンID</dd>\r
- </dl></td> \r
- </tr> \r
- <tr>\r
- <td>PreAddBan</td>\r
- <td>(v2.0) 新しい禁止IPが追加される直前</td>\r
- <td><dl>\r
- <dt class="ref">blogid</dt>\r
- <dd>blogID</dd>\r
- <dt class="ref">iprange</dt>\r
- <dd>禁止されたIPレンジ</dd>\r
- <dt class="ref">reason</dt>\r
- <dd>禁止された理由を記述したテキストメッセージ</dd>\r
- </dl></td> \r
- </tr>\r
- <tr>\r
- <td>PostAddBan</td>\r
- <td>(v2.0) 新しい禁止IPが追加された直後</td>\r
- <td><dl>\r
- <dt class="ro">blogid</dt>\r
- <dd>blogID</dd>\r
- <dt class="ro">iprange</dt>\r
- <dd>禁止されたIPレンジ</dd>\r
- <dt class="ro">reason</dt>\r
- <dd>禁止された理由を記述したテキストメッセージ</dd>\r
- </dl></td> \r
- </tr> \r
-\r
- <tr>\r
- <td>PreMoveItem</td>\r
- <td>(v2.0) アイテムが他のblog/カテゴリーに移される直前</td>\r
- <td><dl>\r
- <dt class="ref">itemid</dt>\r
- <dd>アイテムID</dd>\r
- <dt class="ref">destblogid</dt>\r
- <dd>移動先のblogID</dd>\r
- <dt class="ref">destcatid</dt>\r
- <dd>移動先のカテゴリーID</dd> \r
- </dl></td> \r
- </tr>\r
- <tr>\r
- <td>PostMoveItem</td>\r
- <td>(v2.0) アイテムが他のblog/カテゴリーに移された直後</td>\r
- <td><dl>\r
- <dt class="ro">itemid</dt>\r
- <dd>アイテムID</dd>\r
- <dt class="ro">destblogid</dt>\r
- <dd>新しいblogID</dd>\r
- <dt class="ro">destcatid</dt>\r
- <dd>新しいカテゴリーID</dd> \r
- </dl></td> \r
- </tr>\r
- <tr>\r
- <td>PreMoveCategory</td>\r
- <td>(v2.0) カテゴリーが他のblogに移される直前</td>\r
- <td><dl>\r
- <dt class="ref">catid</dt>\r
- <dd>カテゴリーID</dd>\r
- <dt class="ref obj">sourceblog</dt>\r
- <dd>移動元の<code>BLOG</code> オブジェクト</dd>\r
- <dt class="ref obj">destblog</dt>\r
- <dd>移動先の<code>BLOG</code> オブジェクト</dd> \r
- </dl></td> \r
- </tr>\r
- <tr>\r
- <td>PostMoveCategory</td>\r
- <td>(v2.0) カテゴリーが他のblogに移された直後</td>\r
- <td><dl>\r
- <dt class="ro">catid</dt>\r
- <dd>カテゴリーID</dd>\r
- <dt class="ref obj">sourceblog</dt>\r
- <dd>移動元の<code>BLOG</code> オブジェクト</dd>\r
- <dt class="ref obj">destblog</dt>\r
- <dd>移動先の<code>BLOG</code> オブジェクト</dd> \r
- </dl></td> \r
- </tr> \r
- <tr>\r
- <td>MemberSettingsFormExtras</td>\r
- <td>(v2.0) メンバー設定ページにフォームを追加可能<br /><br /> \r
- あまり多くのデータを追加しないこと。また以下のように<strong>正しいXHTML</strong>を生成してください。\r
- <pre class="example"><code><h4>プラグイン名</h4>\r
-<form method="post" action="..."><p>\r
-追加フォームの内容</p></form></code></pre>\r
-このようにして、正しい構造を保ちつつ複数のプラグインがオプションを保持できます。またフィールド名の重複を避けるためにプレフィックスを用いてください（例 <code>plug_tb_url</code>）。</td>\r
- <td><dl>\r
- <dt class="ref obj">member</dt>\r
- <dd><code>MEMBER</code> オブジェクトへの参照</dd>\r
- </dl></td> \r
- </tr>\r
- <tr>\r
- <td>GeneralSettingsFormExtras</td>\r
- <td>(v2.0) 一般設定ページにフォームを追加可能<br />\r
- <br />\r
-あまり多くのデータを追加しないこと。また以下のように<strong>正しいXHTML</strong>を生成してください。\r
-<pre class="example"><code><h4>プラグイン名</h4>\r
-<form method="post" action="..."><p>\r
-追加フォームの内容</p></form></code></pre>\r
-このようにして、正しい構造を保ちつつ複数のプラグインがオプションを保持できます。またフィールド名の重複を避けるためにプレフィックスを用いてください（例 <code>plug_tb_url</code>）。</td>\r
- <td>なし</td> \r
- </tr>\r
- <tr>\r
- <td>AdminPrePageHead</td>\r
- <td>(v2.5) 管理画面で、ページヘッドを出力する直前。このイベントはヘッド領域にスクリプトやCSSを追加するのに用いられます。</td>\r
- <td><dl>\r
- <dt class="ref">extrahead</dt>\r
- <dd>HTMLページのヘッド領域に埋め込まれる追加情報。ここに追加したいものを入れてください。</dd>\r
- <dt class="ro">action</dt>\r
- <dd>現在実行されているアクション、またはページタイプ</dd>\r
- </dl></td>\r
- </tr>\r
- <tr>\r
- <td>AdminPrePageFoot</td>\r
- <td>(v2.5) 管理画面で、ページフッターを出力する直前。</td>\r
- <td><dl>\r
- <dt class="ro">action</dt>\r
- <dd></dd>\r
- </dl>\r
- 現在実行されているアクション、またはページタイプ</td>\r
- </tr>\r
- <tr>\r
- <td>PreSendContentType</td>\r
- <td>(v2.5) HTTPヘッダーにコンテントタイプがセットされる直前</td>\r
- <td><dl>\r
- <dt class="ref">contentType</dt>\r
- <dd>コンテントタイプ（<code>application/xhtml+xml</code>など）</dd>\r
- <dt class="ref">charset</dt>\r
- <dd>キャラクターセット</dd>\r
- <dt class="ro">pageType</dt>\r
- <dd>表示するページの種類を示す文字列：<code>skin</code> (スキンタイプ), <code>media</code> (メディアライブラリ), <code>admin-<em>action</em></code> (管理エリア), <code>bookmarklet-<em>action</em></code> (ブックマークレット)</dd>\r
- </dl></td>\r
- </tr>\r
- <tr>\r
- <td>QuickMenu</td>\r
- <td>(v2.5) 管理エリアのクイックメニューの一番下。そこへのプラグイン登録に利用されます。登録するにはoptionsに連想配列を入れます。実装例が<a href="#admin">プラグイン管理エリアを作る</a>のセクションにあります。</td>\r
- <td><dl>\r
- <dt class="ref">options</dt>\r
- <dd>配列</dd>\r
- </dl></td>\r
- </tr>\r
- <tr>\r
- <td>BookmarkletExtraHead</td>\r
- <td>(v2.5) ブックマークレット\r
- XHTMLコードのヘッド領域内。</td>\r
- <td><dl>\r
- <dt class="ref">extrahead</dt>\r
- <dd>XHTMLコードのヘッド領域に埋め込まれる追加情報。ここに追加したいものを入れてください。</dd>\r
- </dl></td>\r
- </tr>\r
- <tr>\r
- <td>FormExtra</td>\r
- <td>(v3.2) このイベントは、プラグインがコメント、メンバー間メール、認証フォームのいずれかのフォーム内に追加フィールドを挿入するときに使います。フォーム処理の際に発生する <code>ValidateForm</code> イベントに対応します。</td>\r
- <td><dl>\r
- <dt class="ro">type</dt>\r
- <dd>イベントを発生させるフォームタイプ\r
- <ul>\r
- <li><code>activation</code></li>\r
- <li><code>additemform</code> （注：これは管理画面のアイテム追加フォームではない）</li>\r
- <li><code>commentform-loggedin</code></li>\r
- <li><code>commentform-notloggedin</code></li>\r
- <li><code>membermailform-loggedin</code></li>\r
- <li><code>membermailform-notloggedin</code></li>\r
- </ul>\r
- </dd>\r
- <dt class="ro obj">member</dt>\r
- <dd><code>type</code> が <code>activation</code>のとき、このフィールドは認証メンバーの詳細情報を含みます</dd>\r
- </dl></td>\r
- </tr>\r
- <tr>\r
- <td>ValidateForm</td>\r
- <td>(v3.2) コメント、メンバー間メール、アカウント認証のいずれかが処理されるときに呼ばれます。プラグインはこれで各データの評価を実行でき、もし不具合があれば処理を中断できます。<code>FormExtra</code> と共に使うとフォームにフィールドを追加できます。</td>\r
- <td><dl>\r
- <dt class="ro">type</dt>\r
- <dd>処理されるフォームタイプ\r
- <ul>\r
- <li><code>membermail</code></li>\r
- <li><code>comment</code></li>\r
- <li><code>activation</code></li>\r
- </ul>\r
- </dd>\r
- <dt class="ref">error</dt>\r
- <dd>フォーム処理をストップするときに、<code>error</code> フィールドに空でないエラーメッセージを記入します。このエラーメッセージはユーザー側に表示されます。</dd>\r
- <dt class="ref">comment</dt>\r
- <dd>コメントフォームのとき、コメントデータに関する連想配列を含みます。</dd>\r
- <dt class="ro obj">member</dt>\r
- <dd>認証フォームのとき、認証中のメンバー情報を含みます。</dd>\r
- </dl></td>\r
- </tr>\r
-<!--\r
- <tr>\r
- <td></td>\r
- <td></td>\r
- <td><dl>\r
- <dt></dt>\r
- <dd></dd>\r
- </dl></td>\r
- </tr>\r
- <tr>\r
- <td></td>\r
- <td></td>\r
- <td><dl>\r
- <dt></dt>\r
- <dd></dd>\r
- </dl></td>\r
- </tr>\r
- <tr>\r
- <td></td>\r
- <td></td>\r
- <td><dl>\r
- <dt></dt>\r
- <dd></dd>\r
- </dl></td>\r
- </tr>\r
- <tr>\r
- <td></td>\r
- <td></td>\r
- <td><dl>\r
- <dt></dt>\r
- <dd></dd>\r
- </dl></td>\r
- </tr>\r
- <tr>\r
- <td></td>\r
- <td></td>\r
- <td><dl>\r
- <dt></dt>\r
- <dd></dd>\r
- </dl></td>\r
- </tr>\r
- <tr>\r
- <td></td>\r
- <td></td>\r
- <td><dl>\r
- <dt></dt>\r
- <dd></dd>\r
- </dl></td>\r
- </tr>\r
- <tr>\r
- <td></td>\r
- <td></td>\r
- <td><dl>\r
- <dt></dt>\r
- <dd></dd>\r
- </dl></td>\r
- </tr>\r
- <tr>\r
- <td></td>\r
- <td></td>\r
- <td><dl>\r
- <dt></dt>\r
- <dd></dd>\r
- </dl></td>\r
- </tr> -->\r
-</table>\r
-\r
-\r
-\r
-<h1>オプションを保存する<a name="options" href="#top" class="toplink"><img src="../icon-up.gif" width="15" height="15" alt="back to top" /></a></h1>\r
-\r
-<p>プラグインに簡単にオプションを登録・取得できるように一連のメソッドが用意されています。これらのオプションは直接Nucleusの管理エリアで編集でき、プラグイン自身の管理エリアを用意する必要もなく、PHPファイルそのものの中にオプションの値を書き込まずにすみます。</p>\r
-\r
-<p>オプションは異なったコンテクストで利用可能です。</p>\r
-\r
-<ol>\r
- <li><strong>グローバルオプション</strong>：管理エリアのプラグインセクションで編集可能</li>\r
- <li><strong>blogオプション</strong>：blog設定ページで編集可能</li>\r
- <li><strong>カテゴリーオプション</strong>：blog設定ページ（のカテゴリー編集ページ）で編集可能</li> \r
- <li><strong>メンバーオプション</strong>：メンバー編集ページで編集可能</li>\r
- <li><strong>アイテムオプション</strong>：アイテムの追加、およびアイテムの編集ページで編集可能</li>\r
-</ol>\r
-\r
-<h2>オプションの種類</h2>\r
-\r
-<p>オプションにはいくつかのタイプが提供されています。</p>\r
-\r
-<dl>\r
- <dt>text</dt>\r
- <dd>シンプルなテキスト</dd>\r
- <dt>yesno</dt>\r
- <dd>'yes'か'no'どちらか（編集画面ではラジオボタンとして表示されます）</dd>\r
- <dt>password</dt>\r
- <dd>テキストフィールド (編集画面では伏字で表示されます)</dd>\r
- <dt>textarea (v2.2)</dt>\r
- <dd>複数行のテキストフィールド</dd>\r
- <dt>select (v2.2)</dt>\r
- <dd>ドロップダウンメニュー。次のような形式の追加情報が必要です： Option 1|value1|Option 2|value2|Option 3|value3 </dd>\r
-</dl>\r
-\r
-<h2>オプション・メタ</h2>\r
-\r
-<p>Nucleus v3.2よりオプション・メタデータを用いて、オプションタイプを正しい値を受け取れるように制限できるようになりました。このメタデータは <code>$typeExtras</code>フィールドにセミコロン区切りのリストで保存されます。注：selectオプションでは、selectリストは<code>$typeExtras</code>のなかで一番最初でなければいけません。</p>\r
-\r
-<table><tr>\r
- <th>キー</th>\r
- <th>説明</th>\r
-</tr><tr>\r
- <td><code>datatype</code></td>\r
- <td>Nucleus本体に、どのデータ型を使いたいかという追加情報を与えます。現在は '<code>numerical</code>' のみ利用できます。 '<code>numerical</code>' を指定することでNucleusは数値情報のみを受け付けます（クライアントサイド・サーバサイド両方でチェック） （'<code>select</code>' と '<code>text</code>'のオプションタイプで利用できます）</td>\r
-</tr><tr>\r
- <td><code>access</code></td>\r
- <td>'<code>readonly</code>'にセットすることで、オプションを編集不可能にします（'<code>text</code>' と '<code>textarea</code>'のオプションタイプで利用できます）<br />\r
- '<code>hidden</code>'を使うと、利用者側にそのオプションの存在を完全に隠蔽します（'<code>text</code>'のオプションタイプで利用できます）</td>\r
-</tr></table>\r
-\r
-<p>設定例</p>\r
-<pre class="example"><code>// 数値のみを受け付けるテキストオプションを作成\r
-$this->createBlogOption('FooBar', 'foobar', 'text', '0', 'datatype=numerical');\r
-// 数値のみを受け付けるセレクトオプションを作成\r
-$this->createItemOption('FooBar', 'foobar', 'select', '0', '0|0|1|1|2|2;datatype=numerical');\r
-// 編集不可能なテキストエリアオプションを作成\r
-$this->createOption('FooBar', 'foobar', 'textarea', 'This textarea is readonly', 'access=readonly');\r
-</code></pre>\r
-\r
-<h2>制限</h2>\r
-\r
-<ol>\r
- <li>オプション名は最大20文字です。</li>\r
- <li>オプションの説明文は最大255文字です。</li>\r
- <li>オプションの値は制限ありません（v2.2より前のバージョンでは128文字の制限がありました）</li>\r
- <li>'=', '|', ';' のキャラクターはセレクトオプション用のセレクトリストやオプション・メタデータ中で使用することはできません。</li>\r
-</ol>\r
-\r
-<h2>メソッド</h2>\r
-\r
-<h3>createOption($name, $desc, $type, $defValue = '', $typeExtras = '')</h3>\r
-\r
-<p><strong>グローバル</strong>なコンテクストで新しいオプションを生成します。</p>\r
-\r
-<table><tr>\r
- <th>パラメータ</th>\r
- <th>値</th>\r
-</tr><tr>\r
- <td>$name</td>\r
- <td>オプション名</td>\r
-</tr><tr>\r
- <td>$desc</td>\r
- <td>オプション編集画面で表示される説明文</td>\r
-</tr><tr>\r
- <td>$type</td>\r
- <td>オプションタイプ（前出）</td>\r
-</tr><tr>\r
- <td>$defValue</td>\r
- <td>初期値</td>\r
-</tr><tr>\r
- <td>$typeExtras</td>\r
- <td>オプションタイプの追加情報（前出）</td>\r
-</tr></table>\r
-\r
-<h3>[v2.2] createBlogOption($name, $desc, $type, $defValue = '', $typeExtras = '')</h3>\r
-\r
-<p><strong>blog</strong>のコンテクストで新しいオプションを生成します（<code>createOption</code>を参照）。</p>\r
-\r
-<h3>[v2.2] createCategoryOption($name, $desc, $type, $defValue = '', $typeExtras = '')</h3>\r
-\r
-<p><strong>カテゴリー</strong>のコンテクストで新しいオプションを生成します（<code>createOption</code>を参照）。</p>\r
-\r
-<h3>[v2.2] createMemberOption($name, $desc, $type, $defValue = '', $typeExtras = '')</h3>\r
-\r
-<p><strong>メンバー</strong>のコンテクストで新しいオプションを生成します（<code>createOption</code>を参照）。</p>\r
-\r
-<h3>[v3.2] createItemOption($name, $desc, $type, $defValue = '', $typeExtras = '')</h3>\r
-\r
-<p><strong>アイテム</strong>のコンテクストで新しいオプションを生成します（<code>createOption</code>を参照）。</p>\r
-\r
-<h3>setOption($name, $value)</h3>\r
-\r
-<p>すでにデータベースに存在するオプションの値を変更します。</p>\r
-\r
-<table><tr>\r
- <th>パラメータ</th>\r
- <th>値</th>\r
-</tr><tr> \r
- <td>$name</td>\r
- <td>オプション名</td>\r
-</tr><tr>\r
- <td>$value</td>\r
- <td>新しい値</td>\r
-</tr></table>\r
-\r
-<h3>[v2.2] setBlogOption($blogid, $name, $value)</h3>\r
-\r
-<p>blogオプションの値を変更します。<code>blogid</code>属性はどのblogでそのオプションが有効かを示します（その他のオプション：<code>setOption</code>を参照）。</p>\r
-\r
-<h3>[v2.2] setCategoryOption($catid, $name, $value)</h3>\r
-\r
-<p>カテゴリーオプションの値を変更します。<code>catid</code>属性はどのカテゴリーでそのオプションが有効かを示します（その他のオプション：<code>setOption</code>を参照）。</p>\r
-\r
-<h3>[v2.2] setMemberOption($memberid, $name, $value)</h3>\r
-\r
-<p>メンバーオプションの値を変更します。<code>memberid</code>属性はどのメンバーでそのオプションが有効かを示します（その他のオプション：<code>setOption</code>を参照）。</p>\r
-\r
-<h3>[v3.2] setItemOption($itemid, $name, $value)</h3>\r
-\r
-<p>アイテムオプションの値を変更します。<code>itemid</code>属性はどのアイテムでそのオプションが有効かを示します（その他のオプション：<code>setOption</code>を参照）。</p>\r
-\r
-<h3>getOption($name)</h3>\r
-\r
-<p>データベース内のオプションの値を返します。</p>\r
-\r
-<table><tr>\r
- <th>パラメータ</th>\r
- <th>値</th>\r
-</tr><tr> \r
- <td>$name</td>\r
- <td>オプション名</td>\r
-</tr></table>\r
-\r
-<h3>[v2.2] getBlogOption($blogid, $name)</h3>\r
-\r
-<p>blogオプションの値を返します。<code>blogid</code>属性は値がリスエストされたblogを示します（その他のオプション：<code>getOption</code>を参照）。</p>\r
-\r
-<h3>[v2.2] getCategoryOption($catid, $name)</h3>\r
-\r
-<p>カテゴリーオプションの値を返します。<code>catid</code>属性は値がリスエストされたカテゴリーを示します（その他のオプション：<code>getOption</code>を参照）。<br />\r
-</p>\r
-\r
-<h3>[v2.2] getMemberOption($memberid, $name)</h3>\r
-\r
-<p>メンバーオプションの値を返します。<code>memberid</code>属性は値がリスエストされたメンバーを示します（その他のオプション：<code>getOption</code>を参照）。</p>\r
-\r
-<h3>[v3.2] getItemOption($itemid, $name)</h3>\r
-\r
-<p>アイテムオプションの値を返します。<code>itemid</code>属性は値がリスエストされたアイテムを示します（その他のオプション：<code>getOption</code>を参照）。</p>\r
-\r
-<h3>deleteOption($name)</h3>\r
-\r
-<p>データベースからオプションを削除します。</p>\r
-\r
-<table><tr>\r
- <th>パラメータ</th>\r
- <th>値</th>\r
-</tr><tr> \r
- <td>$name</td>\r
- <td>オプション名</td>\r
-</tr></table>\r
-\r
-<h3>[v2.2] deleteBlogOption($name)</h3>\r
-\r
-<p>blogオプションを削除します（<code>deleteOption</code>を参照）。</p>\r
-\r
-<h3>[v2.2] deleteCategoryOption($name)</h3>\r
-\r
-<p>カテゴリーオプションを削除します（<code>deleteOption</code>を参照）。</p>\r
-\r
-<h3>[v2.2] deleteMemberOption($name)</h3>\r
-\r
-<p>メンバーオプションを削除します（<code>deleteOption</code>を参照）。</p>\r
-\r
-<h3>[v3.2] deleteItemOption($name)</h3>\r
-\r
-<p>アイテムオプションを削除します（<code>deleteOption</code>を参照）。</p>\r
-\r
-<h3>[v2.2] getAllBlogOptions($name)</h3>\r
-\r
-<p>与えられたblogオプションの全ての値を返します。結果は存在するblogidごとの連想配列です。</p>\r
-\r
-<h3>[v2.2] getAllCategoryOptions($name)</h3>\r
-\r
-<p>与えられたカテゴリーオプションの全ての値を返します。結果は存在するcatidごとの連想配列です。</p>\r
-\r
-<h3>[v2.2] getAllMemberOptions($name)</h3>\r
-\r
-<p>与えられたメンバーオプションの全ての値を返します。結果は存在するmemberidごとの連想配列です。</p>\r
-\r
-<h3>[v3.2] getAllItemOptions($name)</h3>\r
-\r
-<p>与えられたアイテムオプションの全ての値を返します。結果は存在するitemidごとの連想配列です。</p>\r
-\r
-<h3>[v3.2] getBlogOptionTop($name, $amount = 10, $sort = 'desc')</h3>\r
-\r
-<p>与えられたオプションの最初の値を返します。結果は配列で、各要素がそれぞれのblogid ('id') の値 ('value') を持つ配列になっています。</p>\r
-\r
-<table><tr>\r
- <th>パラメータ</th>\r
- <th>値</th>\r
-</tr><tr>\r
- <td>$name</td>\r
- <td>オプション名</td>\r
-</tr><tr>\r
- <td>$amount</td>\r
- <td>必要なオプション数</td>\r
-</tr><tr>\r
- <td>$sort</td>\r
- <td>昇順 ('asc') か降順 ('desc') で並べ替え</td>\r
-</tr></table>\r
-\r
-<h3>[v3.2] getMemberOptionTop($name, $amount = 10, $sort = 'desc')</h3>\r
-\r
-<p>与えられたオプションの最初の値を返します。結果は配列で、各要素がそれぞれのメンバーID ('id') の値 ('value') を持つ配列になっています（パラメータは<code>getBlogOptionTop</code>を参照）。</p>\r
-\r
-<h3>[v3.2] getCategoryOptionTop($name, $amount = 10, $sort = 'desc')</h3>\r
-\r
-<p>与えられたオプションの最初の値を返します。結果は配列で、各要素がそれぞれのカテゴリーID ('id') の値 ('value') を持つ配列になっています（パラメータは<code>getBlogOptionTop</code>を参照）。</p>\r
-\r
-\r
-<h3>[v3.2] getItemOptionTop($name, $amount = 10, $sort = 'desc')</h3>\r
-\r
-<p>与えられたオプションの最初の値を返します。結果は配列で、各要素がそれぞれのアイテムID ('id') の値 ('value') を持つ配列になっています（パラメータは<code>getBlogOptionTop</code>を参照）。</p>\r
-\r
-\r
-<div class="note">\r
-<b>注：</b> プラグインクラス内のコンストラクタから、これらのファンクションを呼ぶことはできません。プラグインがロードされた後にこれらを実行したいときは、かわりに<code>init()</code>メソッド内に置きます。</div>\r
-\r
-<h1>データベース・テーブル<a name="tables" href="#top" class="toplink"><img src="../icon-up.gif" width="15" height="15" alt="back to top" /></a></h1>\r
-\r
-<h2>Nucleusテーブルへのアクセス</h2>\r
-\r
-<p>v2.0まで、Nucleusテーブルへのアクセスは単に<code>nucleus_</code>と名づけられたテーブルに対してSQL命令を実行するだけのものでした。Nucleusのバージョン2.2以降はカスタム・テーブル名を利用できるようになったため、プラグイン開発に若干注意する必要があります。</p>\r
-\r
-<ol>\r
- <li><code>nucleus_item</code> などの固定されたテーブル名の代わりに、テーブル名のプレフィックスを生成するために <code>sql_table('item') </code>というグローバルファンクションを利用します。</li>\r
- <li><code>supportsFeature('SqlTablePrefix')</code> が呼ばれたときにプラグインが1（真）を返すようにします。これがないと、カスタムプレフィックスがセットされている場合でバージョンが2.0より大きいNucleusではプラグインをロードできません（用心のため）。</li>\r
-</ol>\r
-\r
-<p class="note">v2.0までのNucleusではグローバルファンクション <code>sql_table</code> は利用できないことに注意してください。もしこのメソッドを用いつつ、プラグインをv2.0以下のNucleusで動作させたい場合は、以下のコードをプラグインクラスの前に追加してください。</p>\r
-\r
-<pre class="example"><code><?\r
-\r
-// プラグインがNucleusバージョン2.0以下と互換性を持つために必要\r
-if (!function_exists('sql_table'))\r
-{\r
- function sql_table($name) {\r
- return 'nucleus_' . $name;\r
- }\r
-}\r
-\r
-class NP_HelloWorld extends NucleusPlugin {\r
-...\r
-}\r
-\r
-?></code></pre>\r
-\r
-<h2>独自テーブル</h2>\r
-\r
-<p>もしプラグイン独自のテーブルが必要なら、<code>install</code>メソッドの中で独自テーブルを生成し、<code>unInstall</code>メソッドの中でそれを削除するようにします。</p>\r
-\r
-<p>いくつかの注意点</p>\r
-<ul>\r
- <li><code>nucleus_plug_<em>plugname</em></code> のように、他のプラグインと競合しないテーブル名を考えてください。カスタムプレフィックスに対応するため、テーブル名を\r
- <code>sql_table('plug_plugname')</code> で生成してください。\r
- </li>\r
- <li>自分自身でデータベース接続をする必要はありません。PHPコマンド <code>mysql_query()</code> を使ってSQL命令を実行できます。</li>\r
- <li>自分でデータベース接続をする場合、後でNucleusデータベースへの接続を復元するようにしてください。自前処理の後で <code>sql_connect()</code> を呼ぶことで可能です。頻繁な再接続を避けるために、コンストラクタでそれを行うのも良いです。<code>$this- >db</code>のリンクIDを保持でき、各クエリにそれを渡すことができます。</li>\r
- <li>バックアップ機能を使う時は、独自テーブルもバックアップに含めるよう、<code>getTableList()</code> を再定義してください。</li>\r
-</ul>\r
-\r
-<h1>プラグイン管理エリア<a name="admin" href="#top" class="toplink"><img src="../icon-up.gif" width="15" height="15" alt="back to top" /></a></h1>\r
-\r
-<p>Ver2.5から、Nucleusの管理エリアに統合されたプラグイン管理エリアを作成できます。これらのページは従来のプラグイン管理ページや左側のクイックメニューからアクセスできます。</p>\r
-\r
-<h2>基本</h2>\r
-\r
-<p>管理エリアを提供するには、次のステップが必要です。</p>\r
-\r
-<ol>\r
- <li>プラグインディレクトリに<strong>プラグイン名</strong>のサブディレクトリを作ります。たとえばプラグイン名が<code>NP_PluginName</code>なら、'pluginname'です。ディレクトリ名はすべて小文字で！</li>\r
- <li>\r
- そのディレクトリで、次のような<strong>index.php</strong>を用意します。\r
- <pre><code><?php\r
-\r
- // if your 'plugin' directory is not in the default location,\r
- // edit this variable to point to your site directory\r
- // (where config.php is)\r
- $strRel = '../../../';\r
-\r
- include($strRel . 'config.php');\r
- if (!$member->isLoggedIn())\r
- doError('You\'re not logged in.');\r
-\r
- include($DIR_LIBS . 'PLUGINADMIN.php');\r
-\r
- // create the admin area page\r
- $oPluginAdmin = new PluginAdmin('<strong>PluginName</strong>');\r
- $oPluginAdmin->start();\r
-\r
- echo '<h2>プラグイン名</h2>';\r
-\r
- echo '<p><strong>ページ内容</strong><p>';\r
-\r
- $oPluginAdmin->end();\r
-\r
-?></code></pre>\r
- </li>\r
- <li>\r
- プラグイン側に次のコードを挿入し、クイックメニューイベントに登録します。\r
- <pre><code>function event_QuickMenu(&$data) {\r
- array_push(\r
- $data['options'],\r
- array(\r
- 'title' => '<strong>プラグイン名</strong>',\r
- 'url' => $this->getAdminURL(),\r
- 'tooltip' => '<strong>ツールチップテキスト</strong>'\r
- )\r
- );\r
- }</code></pre>\r
- </li>\r
- <li>\r
- プラグイン側に次の関数を記述します。\r
- <pre><code>function hasAdminArea()\r
-{\r
- return 1;\r
-}</code></pre>\r
- </li>\r
-</ol>\r
-\r
-<h2>考慮すること</h2>\r
-\r
-<ul>\r
- <li>登録できるからといって安易にクイックメニューへ登録しないこと。クイックメニューにプラグインが100個並んだりしたらかなりウンザリするでしょう。ですので、クイックメニューに登録する場合でも、クイックメニュー登録を有効・無効化するプラグインオプションを（グローバルまたはメンバーオプションで）用意することを考えてください。</li>\r
- <li><code>プラグインディレクトリが nucleus/plugins/ ではない場合は、index.php内の $strRel</code> 変数は手動で書き換える必要があります。</li>\r
- <li>管理エリアのアウトプットが<strong>正しいXHTML</strong>になっているか確認してください。正しくないと、MozillaなどのGeckoベースのブラウザでページ表示が崩れます。</li>\r
-</ul>\r
-\r
-<h2>PluginAdmin クラス</h2>\r
-\r
-<p><code>PluginAdmin</code> クラスは助けになります。これを一度生成すれば、<code>$oPluginAdmin->plugin</code> でプラグインのインスタンスにアクセスできます。</p>\r
-\r
-<h1>プラグイン用ヘルプページ <a name="help" href="#top" class="toplink"><img src="../icon-up.gif" width="15" height="15" alt="back to top" /></a></h1>\r
-\r
-<p>Nucleus v3.2から、プラグインの機能の概要、利用できるスキン・テンプレート変数、さらに詳細な情報のありかなどを示すヘルプページを提供可能になりました。</p>\r
-\r
-<p>ヘルプページは管理画面のプラグイン一覧からアクセス可能になります。</p>\r
-\r
-<h2>基本</h2>\r
-<p>ヘルプページを提供するために、次のステップが必要です。</p>\r
-<ol>\r
-<li>プラグインディレクトリに、プラグイン名をつけたサブディレクトリを作成します。ディレクトリ名は小文字であることに注意します。<a href="#admin">管理エリア</a>を作るときと同様です。</li>\r
-<li>そのディレクトリの中に help.html を作り、プラグインについての文章を記述します。次の雛型からはじめると良いでしょう。\r
-<pre><code><h3>プラグインの概要</h3>\r
-\r
-<p>このプラグインはヘルプページがいかに機能するかを示すためだけのものです</p>\r
-\r
-<h3>インストール</h3>\r
-\r
-<p>これを読めてるならインストールは正しく出来てます :-)</p>\r
-\r
-<h3>スキン変数</h3>\r
-\r
-<p>このプラグインはただのテストケースなのでスキン・テンプレート変数はありませんが、書くとすれば。\r
-\r
-<ul><li><b><%HelpPageTestCase1%></b>: なにかをする</li>\r
-<li><b><%HelpPageTestCase1(foobar)%></b>: 別のなにかをする</li></ul></p>\r
-\r
-<h3>サポートとバグ報告</h3>\r
-\r
-<p>さらなるサポートやバグ報告のために、次のフォーラムのスレッドを利用してください。\r
-<a href="http://forum.nucleuscms.org/viewtopic.php?t=<トピックID>">\r
-http://forum.nucleuscms.org/viewtopic.php?t=<トピックID></a></p>\r
-\r
-<h3>バージョン履歴</h3>\r
-\r
-<ul><li>Version 0.1: 最初のテストケースバージョン</li>\r
-<li>Version 0.0: その前のバージョン ;-)</li></ul></code></pre>\r
-</li>\r
-<li>supportsFeature('HelpPage') で0より大きい数字を返すように設定します。\r
-<pre><code>function supportsFeature($what) {\r
- switch($what) {\r
- case 'HelpPage':\r
- return 1;\r
- default:\r
- return 0;\r
- }\r
- }</code></pre>\r
-</li>\r
-</ol>\r
-\r
-<h1>プラグイン依存チェック <a name="dependency" href="#top" class="toplink"><img src="../icon-up.gif" width="15" height="15" alt="back to top" /></a></h1>\r
-\r
-<p>v3.2から、他のプラグインとの依存関係を宣言する新しいプラグインインターフェイスが追加されました。他のプラグインの機能を必要とするプラグインに利用できます。特に依存関係が成立しなくて正しく機能しない状態を検知するときに便利です。</p>\r
-\r
-<h2>この機能を利用するプラグインの書き方</h2>\r
-\r
-<p>現実世界での例からはじめましょう。</p>\r
-\r
-<p>NP_PageLinkList は NP_BlogWithOffset の機能を利用するため、利用者には NP_BlogWithOffset のインストール後に NP_PageLinkList をインストールさせたいとします。NucleusはこのAPIによって、インストール前に依存関係を検知させる方法をプラグインに提供します。</p>\r
-\r
-<p>このケースでは、NP_PageLinkList 側に NP_BlogWithOffset が必要だということを認識させるコードを埋め込みます。プラグインがインストールされる際に、Nucleusコアは <code>getPluginDep()</code> というファンクションを呼び出します。このファンクションは必要なプラグインのリストを返し、コアはインストール済みのプラグインをチェックして、もし依存関係に欠如があればインストールを拒否します。</p>\r
-\r
-<p>必要なことは NP_PageLinkList にこのファンクションを追加する、ただそれだけです。</p>\r
-\r
-<pre><code>function getPluginDep() {\r
- return array('NP_BlogWithOffset');\r
-}</code></pre>\r
-\r
-<p>このプラグイン依存チェックは、他のプラグインが依存しているプラグインがアンインストールされることも防ぎます。</p>\r
-\r
-</body>\r
-</html>\r
+++ /dev/null
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">\r
-<html xml:lang="en" xmlns="http://www.w3.org/1999/xhtml">\r
-<head>\r
- <!-- $Id: sqltables.html,v 1.4 2005-03-19 07:28:32 kimitake Exp $ -->\r
- <title>Nucleus - SQL Table Structure</title>\r
- <link rel="stylesheet" type="text/css" href="styles/manual.css" />\r
- <style type="text/css">\r
- /* auto increment table columns*/\r
- .autoinc {\r
- }\r
-\r
- /* primary-keys */\r
- .primary {\r
- text-decoration: underline;\r
- font-weight: bold;\r
- }\r
-\r
- /* NOT NULL */\r
- .notnull {\r
- }\r
-\r
- /* unique key */\r
- .unique {\r
- }\r
-\r
- /* foreign keys */\r
- .foreign {\r
- font-style: italic;\r
- }\r
-\r
- /* auto increment table columns*/\r
- .autoinc {\r
- }\r
-\r
- /* fulltext index */\r
- .fulltext {\r
- }\r
-\r
- /* columns/tables to remove in later versions */\r
- .toremove {\r
- color: red;\r
- }\r
-\r
-\r
-\r
-\r
- </style>\r
-</head>\r
-<body>\r
-\r
-<a name="top" id="top"></a>\r
-\r
-<div class="heading">\r
-SQL Table Reference\r
-<i>March 5, 2005</i>\r
-</div>\r
-\r
-<h1>Introduction</h1>\r
-\r
-<p>\r
-<a href="index.html">Back to the developer docs index</a>\r
-</p>\r
-\r
-<p>\r
-This document contains information on the fields inside the Nucleus database tables.\r
-</p>\r
-\r
-<p class="note">The structure as presented here is for <strong>Nucleus v3.2</strong>.</p>\r
-\r
-<h1><a name="toc" id="toc"></a>Table Of Contents</h1>\r
-\r
-<ul>\r
- <li><a href="#legend">Color codes in this document</a></li>\r
- <li>\r
-\r
- Blogs\r
-\r
- <ul>\r
- <li><a href="#nucleus_blog">nucleus_blog</a></li>\r
- <li><a href="#nucleus_category">nucleus_category</a></li>\r
- <li><a href="#nucleus_item">nucleus_item</a></li>\r
- <li><a href="#nucleus_comment">nucleus_comment</a></li>\r
- <li><a href="#nucleus_member">nucleus_member</a></li>\r
- <li><a href="#nucleus_team">nucleus_team</a></li>\r
- </ul>\r
- </li>\r
- <li>\r
- Plugins\r
- <ul>\r
- <li><a href="#nucleus_plugin">nucleus_plugin</a></li>\r
- <li><a href="#nucleus_plugin_event">nucleus_plugin_event</a></li>\r
- <li><a href="#nucleus_plugin_option">nucleus_plugin_option</a></li>\r
- <li><a href="#nucleus_plugin_option_desc">nucleus_plugin_option_desc</a></li>\r
- </ul>\r
- </li>\r
- <li>\r
- Skins and templates\r
- <ul>\r
- <li><a href="#nucleus_skin">nucleus_skin</a></li>\r
- <li><a href="#nucleus_skin_desc">nucleus_skin_desc</a></li>\r
- <li><a href="#nucleus_template">nucleus_template</a></li>\r
- <li><a href="#nucleus_template_desc">nucleus_template_desc</a></li>\r
- </ul>\r
- </li>\r
- <li>\r
- Administration\r
- <ul>\r
- <li><a href="#nucleus_actionlog">nucleus_actionlog</a></li>\r
- <li>\r
- <a href="#nucleus_config">nucleus_config</a>\r
- <ul>\r
- <li><a href="#nucleus_config_options">Available Options</a></li>\r
- </ul>\r
- </li>\r
- <li><a href="#nucleus_tickets">nucleus_tickets</a></li>\r
- <li><a href="#nucleus_activation">nucleus_activation</a></li>\r
- </ul>\r
- </li>\r
- <li>\r
- Extras\r
- <ul>\r
- <li><a href="#nucleus_karma">nucleus_karma</a></li>\r
- <li><a href="#nucleus_ban">nucleus_ban</a></li>\r
- </ul>\r
- </li>\r
-\r
-\r
-</ul>\r
-\r
-<a id="legend" name="legend"></a>\r
-<h1>Color codes<a href="#top" class="toplink"><img src="../icon-up.gif" width="15" height="15" alt="back to top" /></a></h1>\r
-\r
-<p>This document uses some visual styles to indicate the type of columns. An overview is listed below:</p>\r
-\r
-<table><tr>\r
- <td class="primary">primary</td>\r
- <td>Primary keys</td>\r
-</tr><tr>\r
- <td class="foreign">foreign</td>\r
- <td>Foreign keys (click to go to the references value in other columns). Please note that MySQL does not enforce foreign key restrictions.</td>\r
-</tr><tr>\r
- <td class="toremove">toremove</td>\r
- <td>Tables/columns that will probably be removed in upcoming Nucleus version, in favor of plugins that provide the same functionality.</td>\r
-</tr><tr>\r
- <td class="fulltext">fulltext</td>\r
- <td>There is a fulltext index on the column (used for searches).</td>\r
-</tr></table>\r
-\r
-\r
-<a id="nucleus_blog" name="nucleus_blog"></a>\r
-<h1>Table nucleus_blog<a href="#top" class="toplink"><img src="../icon-up.gif" width="15" height="15" alt="back to top" /></a></h1>\r
-\r
-<table><tr>\r
- <th>Column Name</th>\r
- <th>Type</th>\r
- <th>Default</th>\r
- <th>Description</th>\r
-\r
-</tr><tr>\r
- <td class="notnull autoinc primary">bnumber</td>\r
- <td>int(11)</td>\r
- <td></td>\r
- <td>Blog ID</td>\r
-\r
-</tr><tr>\r
- <td class="notnull">bname</td>\r
- <td>varchar(60)</td>\r
- <td>''</td>\r
- <td>Blog Name</td>\r
-\r
-</tr><tr>\r
- <td class="notnull unique">bshortname</td>\r
- <td>varchar(15)</td>\r
- <td>''</td>\r
- <td>Short Blog Name (as used in skinvars <code><%blog%></code> etc.)</td>\r
-\r
-</tr><tr>\r
- <td>bdesc</td>\r
- <td>varchar(200)</td>\r
- <td>NULL</td>\r
- <td>Blog Description</td>\r
-\r
-</tr><tr>\r
- <td class="notnull">bcomments</td>\r
- <td>tinyint(2)</td>\r
- <td>'1'</td>\r
- <td>Enable comments (1=true, 0=false)</td>\r
-\r
-</tr><tr>\r
- <td class="notnull">bmaxcomments</td>\r
- <td>int(11)</td>\r
- <td>'0'</td>\r
- <td>Maximum amount of comments to show on <code>index</code> skintypes (inline comments). The default value (0) means that there is no limit. If you don't use inline comments, you shouldn't edit this.</td>\r
-\r
-</tr><tr>\r
- <td class="notnull">btimeoffset</td>\r
- <td>decimal(3,1)</td>\r
- <td>'0.0'</td>\r
- <td>Time offset to use. The items will be stored in the database using the correct time (server time+offset).</td>\r
-\r
-</tr><tr>\r
- <td class="toremove">bnotify</td>\r
- <td>varchar(60)</td>\r
- <td>NULL</td>\r
- <td>Notify e-mail address. On certain events (see <code>bnotifytype</code> for the exact definition of these events), a notification e-mail is sent out to this e-mail address.</td>\r
-\r
-</tr><tr>\r
- <td>burl</td>\r
- <td>varchar(100)</td>\r
- <td>NULL</td>\r
- <td>Blog URL</td>\r
-\r
-</tr><tr>\r
- <td class="toremove">bupdate</td>\r
- <td>varchar(60)</td>\r
- <td>NULL</td>\r
- <td>Update file that needs to be altered each time a new item is posted to the weblog. Its an absolute path of a file on the server.</td>\r
-\r
-</tr><tr>\r
- <td class="notnull foreign"><a href="#nucleus_skin_desc">bdefskin</a></td>\r
- <td>int(11)</td>\r
- <td>'1'</td>\r
- <td>Default skin to use when displaying this weblog</td>\r
-\r
-</tr><tr>\r
- <td class="notnull">bpublic</td>\r
- <td>tinyint(2)</td>\r
- <td>'1'</td>\r
- <td>Allow comments by non-registered members? (1=true/0=false)</td>\r
-\r
-</tr><tr>\r
- <td class="notnull toremove">bsendping</td>\r
- <td>tinyint(2)</td>\r
- <td>'0'</td>\r
- <td>Send a ping to weblogs.com on update? (1=true/0=false)</td>\r
-\r
-</tr><tr>\r
- <td class="notnull toremove">bconvertbreaks</td>\r
- <td>tinyint(2)</td>\r
- <td>'1'</td>\r
- <td>Convert line breaks to <code><br /></code>? (1=true/0=false)</td>\r
-\r
-</tr><tr>\r
- <td class="foreign"><a href="#nucleus_category">bdefcat</a></td>\r
- <td>int(11)</td>\r
- <td>NULL</td>\r
- <td>Default category. This category will be selected by default when no other category is selected.</td>\r
-\r
-</tr><tr>\r
- <td class="notnull">bnotifytype</td>\r
- <td>int(11)</td>\r
- <td>'15'</td>\r
- <td>\r
- Which events to send notification e-mails on (see <code>bnotify</code> for the specification of the e-mail address). It's a combination of three values (multiply the values to get the notify type):\r
- <ul>\r
- <li>3: New comment</li>\r
- <li>5: New karma vote</li>\r
- <li>7: New item</li>\r
- </ul>\r
- Default = New comments & New karma votes (3*5=15)\r
- </td>\r
-\r
-</tr><tr>\r
- <td class="notnull">ballowpast</td>\r
- <td>tinyint(2)</td>\r
- <td>'0'</td>\r
- <td>Allow backdating of items and editing the timestamp of an item (1=true/0=false)</td>\r
-\r
-</tr><tr>\r
- <td class="notnull">bincludesearch</td>\r
- <td>tinyint(2)</td>\r
- <td>'0'</td>\r
- <td>Always include in search queries, even if the query is on another blog (1=true/0=false)</td>\r
-</tr></table>\r
-\r
-\r
-<a id="nucleus_category" name="nucleus_category"></a>\r
-<h1>Table nucleus_category<a href="#top" class="toplink"><img src="../icon-up.gif" width="15" height="15" alt="back to top" /></a></h1>\r
-\r
-<table><tr>\r
- <th>Column Name</th>\r
- <th>Type</th>\r
- <th>Default</th>\r
- <th>Description</th>\r
-</tr><tr>\r
- <td class="notnull autoinc primary">catid</td>\r
- <td>int(11)</td>\r
- <td></td>\r
- <td>Category ID</td>\r
-\r
-</tr><tr>\r
- <td class="notnull foreign"><a href="#nucleus_blog">cblog</a></td>\r
- <td>int(11)</td>\r
- <td>'0'</td>\r
- <td>Blog to which the category belongs</td>\r
-\r
-</tr><tr>\r
- <td>cname</td>\r
- <td>varchar(40)</td>\r
- <td>NULL</td>\r
- <td>Category Name</td>\r
-\r
-</tr><tr>\r
- <td>cdesc</td>\r
- <td>varchar(200)</td>\r
- <td>NULL</td>\r
- <td>Category Description</td>\r
-</tr></table>\r
-\r
-\r
-<a id="nucleus_item" name="nucleus_item"></a>\r
-<h1>Table nucleus_item<a href="#top" class="toplink"><img src="../icon-up.gif" width="15" height="15" alt="back to top" /></a></h1>\r
-\r
-<table><tr>\r
- <th>Column Name</th>\r
- <th>Type</th>\r
- <th>Default</th>\r
- <th>Description</th>\r
-</tr><tr>\r
- <td class="notnull autoinc primary">inumber</td>\r
- <td>int(11)</td>\r
- <td></td>\r
- <td>Item ID</td>\r
-\r
-</tr><tr>\r
- <td class="fulltext">ititle</td>\r
- <td>varchar(160)</td>\r
- <td>NULL</td>\r
- <td>Title</td>\r
-\r
-</tr><tr>\r
- <td class="notnull fulltext">ibody</td>\r
- <td>text</td>\r
- <td></td>\r
- <td>Body text</td>\r
-\r
-</tr><tr>\r
- <td class="fulltext">imore</td>\r
- <td>text</td>\r
- <td></td>\r
- <td>Extended text</td>\r
-\r
-</tr><tr>\r
- <td class="notnull foreign"><a href="#nucleus_blog">iblog</a></td>\r
- <td>int(11)</td>\r
- <td>'0'</td>\r
- <td>Blog to which the item belongs to</td>\r
-\r
-</tr><tr>\r
- <td class="notnull foreign"><a href="#nucleus_member">iauthor</a></td>\r
- <td>int(11)</td>\r
- <td>'0'</td>\r
- <td>Member that is the author of the item</td>\r
-\r
-</tr><tr>\r
- <td class="notnull">itime</td>\r
- <td>datetime</td>\r
- <td>'0000-00-00 00:00:00'</td>\r
- <td>Item time (this is the corrected time, with offset already applies)</td>\r
-\r
-</tr><tr>\r
- <td class="notnull">iclosed</td>\r
- <td>tinyint(2)</td>\r
- <td>'0'</td>\r
- <td>Is item closed? (1=true/0=false). When an item is closed, it's no longer possible to add new comments or cast 'karma votes'</td>\r
-\r
-</tr><tr>\r
- <td class="notnull">idraft</td>\r
- <td>tinyint(2)</td>\r
- <td>'0'</td>\r
- <td>Is the item a draft version? Draft versions only show up in the admin area.</td>\r
-\r
-</tr><tr>\r
- <td class="notnull toremove">ikarmapos</td>\r
- <td>int(11)</td>\r
- <td>'0'</td>\r
- <td>Total amount of positive karma votes casted</td>\r
-\r
-</tr><tr>\r
- <td class="notnull toremove">ikarmaneg</td>\r
- <td>int(11)</td>\r
- <td>'0'</td>\r
- <td>Total amount of negative karma votes casted</td>\r
-\r
-</tr><tr>\r
- <td class="foreign"><a href="#nucleus_category">icat</a></td>\r
- <td>int(11)</td>\r
- <td>NULL</td>\r
- <td>Category to which the item belongs</td>\r
-\r
-</tr></table>\r
-\r
-\r
-<a id="nucleus_comment" name="nucleus_comment"></a>\r
-<h1>Table nucleus_comment<a href="#top" class="toplink"><img src="../icon-up.gif" width="15" height="15" alt="back to top" /></a></h1>\r
-\r
-<table><tr>\r
- <th>Column Name</th>\r
- <th>Type</th>\r
- <th>Default</th>\r
- <th>Description</th>\r
-</tr><tr>\r
- <td class="notnull autoinc primary">cnumber</td>\r
- <td>int(11)</td>\r
- <td></td>\r
- <td>Comment ID</td>\r
-\r
-</tr><tr>\r
- <td class="notnull fulltext">cbody</td>\r
- <td>text</td>\r
- <td></td>\r
- <td>Comment text</td>\r
-\r
-</tr><tr>\r
- <td>cuser</td>\r
- <td>varchar(40)</td>\r
- <td>NULL</td>\r
- <td>Anonymous user name (only used when comment was placed by a non-member. For members, see <code>cmember</code>)</td>\r
-\r
-</tr><tr>\r
- <td>cmail</td>\r
- <td>varchar(100)</td>\r
- <td>NULL</td>\r
- <td>E-mail address or URL (only used when comment was placed by a non-member. For members, see <code>cmember</code>)</td>\r
-\r
-</tr><tr>\r
- <td class="foreign"><a href="#nucleus_member">cmember</a></td>\r
- <td>int(11)</td>\r
- <td>NULL</td>\r
- <td>ID of site member that placed the commend (0 for comments by non-members)</td>\r
-\r
-</tr><tr>\r
- <td class="notnull foreign"><a href="#nucleus_item">citem</a></td>\r
- <td>int(11)</td>\r
- <td>'0'</td>\r
- <td>Item ID to which the comment is attached</td>\r
-\r
-</tr><tr>\r
- <td class="notnull">ctime</td>\r
- <td>datetime</td>\r
- <td>'0000-00-00 00:00:00'</td>\r
- <td>Time of comment</td>\r
-\r
-</tr><tr>\r
- <td>chost</td>\r
- <td>varchar(60)</td>\r
- <td>NULL</td>\r
- <td>Hostname from where the comment was placed</td>\r
-\r
-</tr><tr>\r
- <td class="notnull">cip</td>\r
- <td>varchar(15)</td>\r
- <td>''</td>\r
- <td>IP address from where the comment was placed</td>\r
-\r
-</tr><tr>\r
- <td class="notnull foreign"><a href="#nucleus_blog">cblog</a></td>\r
- <td>int(11)</td>\r
- <td>'0'</td>\r
- <td>Blog to which the comment belongs (this is redundant information)</td>\r
-\r
-</tr></table>\r
-\r
-\r
-\r
-<a id="nucleus_member" name="nucleus_member"></a>\r
-<h1>Table nucleus_member<a href="#top" class="toplink"><img src="../icon-up.gif" width="15" height="15" alt="back to top" /></a></h1>\r
-\r
-<table><tr>\r
- <th>Column Name</th>\r
- <th>Type</th>\r
- <th>Default</th>\r
- <th>Description</th>\r
-</tr><tr>\r
- <td class="notnull autoinc primary">mnumber</td>\r
- <td>int(11)</td>\r
- <td></td>\r
- <td>Member ID</td>\r
-\r
-</tr><tr>\r
- <td class="notnull unique">mname</td>\r
- <td>varchar(16)</td>\r
- <td>''</td>\r
- <td>Display name (the one used to login)</td>\r
-\r
-</tr><tr>\r
- <td>mrealname</td>\r
- <td>varchar(60)</td>\r
- <td>NULL</td>\r
- <td>Full name</td>\r
-\r
-</tr><tr>\r
- <td class="notnull">mpassword</td>\r
- <td>varchar(40)</td>\r
- <td>''</td>\r
- <td>password (<a href="http://www.php.net/md5" title="Info about the PHP md5() function">md5</a> hash)</td>\r
-\r
-</tr><tr>\r
- <td>memail</td>\r
- <td>varchar(60)</td>\r
- <td>NULL</td>\r
- <td>E-mail address. This should always be a valid address.</td>\r
-\r
-</tr><tr>\r
- <td>murl</td>\r
- <td>varchar(100)</td>\r
- <td>NULL</td>\r
- <td>URL of members site</td>\r
-\r
-</tr><tr>\r
- <td>mnotes</td>\r
- <td>varchar(100)</td>\r
- <td>NULL</td>\r
- <td>Extra notes (members can fill these out themselves)</td>\r
-\r
-</tr><tr>\r
- <td class="notnull">madmin</td>\r
- <td>tinyint(2)</td>\r
- <td>'0'</td>\r
- <td>Is super-admin? (1=true/0=false; super-admins have all rights; there must be at least one super-admin in the system)</td>\r
-\r
-</tr><tr>\r
- <td class="notnull">mcanlogin</td>\r
- <td>tinyint(2)</td>\r
- <td>'1'</td>\r
- <td>Can logon to admin area? (1=true/0=false)</td>\r
-\r
-</tr><tr>\r
- <td>mcookiekey</td>\r
- <td>varchar(40)</td>\r
- <td>NULL</td>\r
- <td>A copy of the key that is stored in the users cookie. This key is used to log on. When a member logs on, a random cookiekey is generated. One copy goes into the database, another one goes into a cookie on the users computer. (together with the username).</td>\r
-\r
-</tr><tr>\r
- <td class="notnull">deflang</td>\r
- <td>varchar(20)</td>\r
- <td>''</td>\r
- <td>Language file to use for this member. When empty, uses the default site language.</td>\r
-</tr></table>\r
-\r
-\r
-\r
-\r
-<a id="nucleus_team" name="nucleus_team"></a>\r
-<h1>Table nucleus_team<a href="#top" class="toplink"><img src="../icon-up.gif" width="15" height="15" alt="back to top" /></a></h1>\r
-\r
-<p>For each team member of a blog, there is a row in this table.</p>\r
-\r
-<table><tr>\r
- <th>Column Name</th>\r
- <th>Type</th>\r
- <th>Default</th>\r
- <th>Description</th>\r
-</tr><tr>\r
- <td class="notnull primary foreign"><a href="#nucleus_member">tmember</a></td>\r
- <td>int(11)</td>\r
- <td>'0'</td>\r
- <td>Member ID</td>\r
-\r
-</tr><tr>\r
- <td class="notnull primary foreign"><a href="#nucleus_blog">tblog</a></td>\r
- <td>int(11)</td>\r
- <td>'0'</td>\r
- <td>Blog of which member is on team</td>\r
-\r
-</tr><tr>\r
- <td class="notnull">tadmin</td>\r
- <td>tinyint(2)</td>\r
- <td>'0'</td>\r
- <td>Is blog admin? (0=false/1=true; each blog must have at least one admin)</td>\r
-</tr></table>\r
-\r
-\r
-<a id="nucleus_plugin" name="nucleus_plugin"></a>\r
-<h1>Table nucleus_plugin<a href="#top" class="toplink"><img src="../icon-up.gif" width="15" height="15" alt="back to top" /></a></h1>\r
-\r
-<table><tr>\r
- <th>Column Name</th>\r
- <th>Type</th>\r
- <th>Default</th>\r
- <th>Description</th>\r
-</tr><tr>\r
- <td class="notnull autoinc primary">pid</td>\r
- <td>int(11)</td>\r
- <td></td>\r
- <td>Plugin ID</td>\r
-\r
-</tr><tr>\r
- <td class="notnull">pfile</td>\r
- <td>varchar(40)</td>\r
- <td>''</td>\r
- <td>Filename (e.g. <code>NP_CommentControl</code>) of plugin. This must be a file in the plugins directory (.php extension).</td>\r
-\r
-</tr><tr>\r
- <td class="notnull">porder</td>\r
- <td>int(11)</td>\r
- <td>'0'</td>\r
- <td>Order in which the plugins are called, and in which they are displayed on the plugins page. A lower order number places the plugin earlier in the list.</td>\r
-</tr></table>\r
-\r
-<a id="nucleus_plugin_event" name="nucleus_plugin_event"></a>\r
-<h1>Table nucleus_plugin_event<a href="#top" class="toplink"><img src="../icon-up.gif" width="15" height="15" alt="back to top" /></a></h1>\r
-\r
-<p>A cache that remembers which plugins are registered to which events. Thsi information is stored to avoid having to load all plugins on each requests just to find out which events they want to have. <a href="plugins.html#events">More info on plugins events</a></p>\r
-\r
-<table><tr>\r
- <th>Column Name</th>\r
- <th>Type</th>\r
- <th>Default</th>\r
- <th>Description</th>\r
-</tr><tr>\r
- <td class="notnull foreign"><a href="#nucleus_plugin">pid</a></td>\r
- <td>int(11)</td>\r
- <td>'0'</td>\r
- <td>Plugin ID</td>\r
-\r
-</tr><tr>\r
- <td>event</td>\r
- <td>varchar(40)</td>\r
- <td>NULL</td>\r
- <td>Name of event</td>\r
-</tr></table>\r
-\r
-<a id="nucleus_plugin_option" name="nucleus_plugin_option"></a>\r
-<h1>Table nucleus_plugin_option<a href="#top" class="toplink"><img src="../icon-up.gif" width="15" height="15" alt="back to top" /></a></h1>\r
-\r
-<p>Values for the plugin options. See the <a href="#nucleus_plugin_option_desc">nucleus_plugin_option_desc</a> table for the definition of the options itself.</p>\r
-\r
-<table><tr>\r
- <th>Column Name</th>\r
- <th>Type</th>\r
- <th>Default</th>\r
- <th>Description</th>\r
-\r
-</tr><tr>\r
- <td class="notnull autoinc primary foreign"><a href="#nucleus_plugin_option_desc">oid</a></td>\r
- <td>int(11)</td>\r
- <td></td>\r
- <td>Identification of the option (See the <a href="#nucleus_plugin_option_desc">nucleus_plugin_option_desc</a> table)</td>\r
-\r
-</tr><tr>\r
- <td class="notnull">ovalue</td>\r
- <td>TEXT</td>\r
- <td>''</td>\r
- <td>Value of the option</td>\r
-\r
-</tr><tr>\r
- <td class="notnull primary">ocontextid</td>\r
- <td>int(11)</td>\r
- <td>'0'</td>\r
- <td>\r
- Semantics depend on the option context type,\r
- <ul>\r
- <li>global context: not used</li>\r
- <li>blog context: <a href="#nucleus_blog">blog id</a></li>\r
- <li>category context: <a href="#nucleus_category">category id</a></li>\r
- <li>member context: <a href="#nucleus_member">member id</a></li>\r
- </ul>\r
- </td>\r
-</tr></table>\r
-\r
-\r
-<a id="nucleus_plugin_option_desc" name="nucleus_plugin_option_desc"></a>\r
-<h1>Table nucleus_plugin_option_desc<a href="#top" class="toplink"><img src="../icon-up.gif" width="15" height="15" alt="back to top" /></a></h1>\r
-\r
-<p>For each option created by a plugin, a row is present in this table.</p>\r
-\r
-<table><tr>\r
- <th>Column Name</th>\r
- <th>Type</th>\r
- <th>Default</th>\r
- <th>Description</th>\r
-</tr><tr>\r
- <td class="notnull autoinc unique">oid</td>\r
- <td>int(11)</td>\r
- <td></td>\r
- <td>Option ID. Used from <a href="#nucleus_plugin_option">nucleus_plugin_option</a></td>\r
-\r
-</tr><tr>\r
- <td class="notnull primary foreign"><a href="#nucleus_plugin">opid</a></td>\r
- <td>int(11)</td>\r
- <td>'0'</td>\r
- <td>Plugin to which the option belongs</td>\r
-\r
-</tr><tr>\r
- <td class="notnull primary">oname</td>\r
- <td>varchar(20)</td>\r
- <td>''</td>\r
- <td>Name of the option</td>\r
-\r
-</tr><tr>\r
- <td class="notnull primary">ocontext</td>\r
- <td>varchar(20)</td>\r
- <td>''</td>\r
- <td>Context of the option (<code>global</code>, <code>blog</code>, <code>category</code>, <code>member</code>)</td>\r
-\r
-</tr><tr>\r
- <td>odesc</td>\r
- <td>varchar(255)</td>\r
- <td>NULL</td>\r
- <td>Option description</td>\r
-\r
-</tr><tr>\r
- <td>otype</td>\r
- <td>varchar(20)</td>\r
- <td>NULL</td>\r
- <td>option type. <a href="plugins.html#options" title="Nucleus Plugin API - Option types">See plugin documentation</a>.</td>\r
-\r
-</tr><tr>\r
- <td>odef</td>\r
- <td>text</td>\r
- <td></td>\r
- <td>Default value for options</td>\r
-\r
-</tr><tr>\r
- <td>oextra</td>\r
- <td>text</td>\r
- <td></td>\r
- <td>Extra data needed for some option types (e.g. <code>select</code> option type)</td>\r
-</tr></table>\r
-\r
-<a id="nucleus_skin" name="nucleus_skin"></a>\r
-<h1>Table nucleus_skin<a href="#top" class="toplink"><img src="../icon-up.gif" width="15" height="15" alt="back to top" /></a></h1>\r
-\r
-<table><tr>\r
- <th>Column Name</th>\r
- <th>Type</th>\r
- <th>Default</th>\r
- <th>Description</th>\r
-</tr><tr>\r
- <td class="notnull primary foreign"><a href="#nucleus_skin_desc">sdesc</a></td>\r
- <td>int(11)</td>\r
- <td>'0'</td>\r
- <td>Reference to the skin description</td>\r
-\r
-</tr><tr>\r
- <td class="notnull primary">stype</td>\r
- <td>varchar(20)</td>\r
- <td>''</td>\r
- <td>\r
- Skinpart type\r
- <ul>\r
- <li><code>index</code></li>\r
- <li><code>item</code></li>\r
- <li><code>archive</code></li>\r
- <li><code>archivelist</code></li>\r
- <li><code>search</code></li>\r
- <li><code>error</code></li>\r
- <li><code>member</code></li>\r
- <li><code>imagepopup</code></li>\r
- </ul>\r
- </td>\r
-\r
-</tr><tr>\r
- <td class="notnull">scontent</td>\r
- <td>text</td>\r
- <td></td>\r
- <td>Contents of the skinpart</td>\r
-</tr></table>\r
-\r
-<a id="nucleus_skin_desc" name="nucleus_skin_desc"></a>\r
-<h1>Table nucleus_skin_desc<a href="#top" class="toplink"><img src="../icon-up.gif" width="15" height="15" alt="back to top" /></a></h1>\r
-\r
-<table><tr>\r
- <th>Column Name</th>\r
- <th>Type</th>\r
- <th>Default</th>\r
- <th>Description</th>\r
-</tr><tr>\r
- <td class="notnull autoinc primary">sdnumber</td>\r
- <td>int(11)</td>\r
- <td></td>\r
- <td>Skin ID</td>\r
-\r
-</tr><tr>\r
- <td class="notnull unique">sdname</td>\r
- <td>varchar(20)</td>\r
- <td>''</td>\r
- <td>Name of skin</td>\r
-\r
-</tr><tr>\r
- <td>sddesc</td>\r
- <td>varchar(200)</td>\r
- <td>NULL</td>\r
- <td>Skin description</td>\r
-\r
-</tr><tr>\r
- <td class="notnull">sdtype</td>\r
- <td>varchar(40)</td>\r
- <td>'text/html'</td>\r
- <td>mimetype of skin</td>\r
-\r
-</tr><tr>\r
- <td class="notnull">sdincmode</td>\r
- <td>varchar(10)</td>\r
- <td>'normal'</td>\r
- <td>\r
- Include mode\r
- <ul>\r
- <li><code>normal</code></li>\r
- <li><code>skindir</code></li>\r
- </ul>\r
- </td>\r
-\r
-</tr><tr>\r
- <td class="notnull">sdincpref</td>\r
- <td>varchar(50)</td>\r
- <td>''</td>\r
- <td>Prefix to use when including files</td>\r
-</tr></table>\r
-\r
-<a id="nucleus_template" name="nucleus_template"></a>\r
-<h1>Table nucleus_template<a href="#top" class="toplink"><img src="../icon-up.gif" width="15" height="15" alt="back to top" /></a></h1>\r
-\r
-<table><tr>\r
- <th>Column Name</th>\r
- <th>Type</th>\r
- <th>Default</th>\r
- <th>Description</th>\r
-</tr><tr>\r
- <td class="notnull primary foreign"><a href="#nucleus_template_desc">tdesc</a></td>\r
- <td>int(11)</td>\r
- <td>'0'</td>\r
- <td>Reference to template description info</td>\r
-\r
-</tr><tr>\r
- <td class="notnull primary">tpartname</td>\r
- <td>varchar(20)</td>\r
- <td>''</td>\r
- <td>\r
- Name of template part\r
- <ul>\r
- <li>ARCHIVELIST_FOOTER</li>\r
- <li>ARCHIVELIST_HEADER</li>\r
- <li>ARCHIVELIST_LISTITEM</li>\r
- <li>CATLIST_FOOTER</li>\r
- <li>CATLIST_HEADER</li>\r
- <li>CATLIST_LISTITEM</li>\r
- <li>COMMENTS_BODY</li>\r
- <li>COMMENTS_MANY</li>\r
- <li>COMMENTS_NONE</li>\r
- <li>COMMENTS_ONE</li>\r
- <li>COMMENTS_TOOMUCH</li>\r
- <li>DATE_HEADER</li>\r
- <li>EDITLINK</li>\r
- <li>FORMAT_DATE</li>\r
- <li>FORMAT_TIME</li>\r
- <li>IMAGE_CODE</li>\r
- <li>ITEM</li>\r
- <li>LOCALE</li>\r
- <li>MEDIA_CODE</li>\r
- <li>MORELINK</li>\r
- <li>POPUP_CODE</li>\r
- <li>SEARCH_HIGHLIGHT</li>\r
- <li>SEARCH_NOTHINGFOUND</li>\r
- </ul>\r
- </td>\r
-\r
-</tr><tr>\r
- <td class="notnull">tcontent</td>\r
- <td>text</td>\r
- <td></td>\r
- <td>Contents of templatepart</td>\r
-</tr></table>\r
-\r
-\r
-<a id="nucleus_template_desc" name="nucleus_template_desc"></a>\r
-<h1>Table nucleus_template_desc<a href="#top" class="toplink"><img src="../icon-up.gif" width="15" height="15" alt="back to top" /></a></h1>\r
-\r
-<table><tr>\r
- <th>Column Name</th>\r
- <th>Type</th>\r
- <th>Default</th>\r
- <th>Description</th>\r
-</tr><tr>\r
- <td class="notnull autoinc primary unique">tdnumber</td>\r
- <td>int(11)</td>\r
- <td></td>\r
- <td>Template ID</td>\r
-\r
-</tr><tr>\r
- <td class="notnull unique">tdname</td>\r
- <td>varchar(20)</td>\r
- <td>''</td>\r
- <td>Name of template</td>\r
-\r
-</tr><tr>\r
- <td>tddesc</td>\r
- <td>varchar(200)</td>\r
- <td>NULL</td>\r
- <td>Template description</td>\r
-</tr></table>\r
-\r
-<a id="nucleus_actionlog" name="nucleus_actionlog"></a>\r
-<h1>Table nucleus_actionlog<a href="#top" class="toplink"><img src="../icon-up.gif" width="15" height="15" alt="back to top" /></a></h1>\r
-\r
-<p>[[general purpose description]]</p>\r
-\r
-<table><tr>\r
- <th>Column Name</th>\r
- <th>Type</th>\r
- <th></th>\r
- <th>Description</th>\r
-</tr><tr>\r
- <td class="notnull">timestamp</td>\r
- <td>datetime</td>\r
- <td>'0000-00-00 00:00:00'</td>\r
- <td>Time of action</td>\r
-\r
-</tr><tr>\r
- <td class="notnull">message</td>\r
- <td>varchar(255)</td>\r
- <td>''</td>\r
- <td>Action message</td>\r
-</tr></table>\r
-\r
-\r
-\r
-<a id="nucleus_config" name="nucleus_config"></a>\r
-<h1>Table nucleus_config<a href="#top" class="toplink"><img src="../icon-up.gif" width="15" height="15" alt="back to top" /></a></h1>\r
-\r
-<p>Nucleus stores some global options in the <code>nucleus_config</code> table. They can be accessed at any time using <code>$CONF['OptionName']</code> (the values are read on each request and stored in a global array named <code>$CONF</code>)</p>\r
-\r
-<table><tr>\r
- <th>Column Name</th>\r
- <th>Type</th>\r
- <th>Default</th>\r
- <th>Description</th>\r
-</tr><tr>\r
- <td class="notnull primary">name</td>\r
- <td>varchar(20)</td>\r
- <td>''</td>\r
- <td>Option name</td>\r
-\r
-</tr><tr>\r
- <td>value</td>\r
- <td>varchar(128)</td>\r
- <td>NULL</td>\r
- <td>Option value</td>\r
-</tr></table>\r
-\r
-<a name="nucleus_config_options" id="nucleus_config_options"></a>\r
-<h2>Available Options</h2>\r
-\r
-<p>An overview of available options is given below:</p>\r
-\r
-<p>Options for yes/no options are represented using 1/0 (1=yes/true, 0=no/false)</p>\r
-\r
-<table><tr>\r
- <th>Name</th>\r
- <th>Default Value</th>\r
- <th>Description</th>\r
-</tr><tr>\r
- <td class="foreign"><a href="#nucleus_blog">DefaultBlog</a></td>\r
- <td>1</td>\r
- <td>Default weblog. This is the blog that will be used when no other blog has been specified in the request.</td>\r
-</tr><tr>\r
- <td>AdminEmail</td>\r
- <td></td>\r
- <td>E-mail address of site administrator</td>\r
-</tr><tr>\r
- <td>IndexURL</td>\r
- <td></td>\r
- <td>URL of website. Should end with a slash.</td>\r
-</tr><tr>\r
- <td>Language</td>\r
- <td>english</td>\r
- <td>Language file to use by default. A file <strong>languagename.php</strong> must exist in the languages directory.</td>\r
-</tr><tr>\r
- <td>SessionCookie</td>\r
- <td>0</td>\r
- <td>Use session cookie instead of cookies with a lifetime of one month?</td>\r
-</tr><tr>\r
- <td>AllowMemberCreate</td>\r
- <td>0</td>\r
- <td>Allow visitors to create their own account?</td>\r
-</tr><tr>\r
- <td>AllowMemberMail</td>\r
- <td>1</td>\r
- <td>Allow members to send messages to each other through the member mail forms (e-mail addresses remain hidden)</td>\r
-</tr><tr>\r
- <td>SiteName</td>\r
- <td></td>\r
- <td>Name of the website</td>\r
-</tr><tr>\r
- <td>AdminURL</td>\r
- <td></td>\r
- <td>URL of admin area. Should end with a slash.</td>\r
-</tr><tr>\r
- <td>NewMemberCanLogon</td>\r
- <td>1</td>\r
- <td>Can newly registered members login right away? If not, the administrator will have to change their 'can login' option first</td>\r
-</tr><tr>\r
- <td class="toremove">DisableSite</td>\r
- <td>0</td>\r
- <td>Is the website disabled? If so, only the administrator can access it. All other visitors are redirected to <code>DisableSiteURL</code>.</td>\r
-</tr><tr>\r
- <td class="toremove">DisableSiteURL</td>\r
- <td></td>\r
- <td>An URL to redirect to when the site is disabled.</td>\r
-</tr><tr>\r
- <td class="toremove">LastVisit</td>\r
- <td>0</td>\r
- <td>Save 'Last Visit' cookies</td>\r
-</tr><tr>\r
- <td>MediaURL</td>\r
- <td></td>\r
- <td>URL of media folder. Should end with a slash.</td>\r
-</tr><tr>\r
- <td>AllowedTypes</td>\r
- <td>jpg, jpeg, gif, mpg, mpeg, avi, mov, mp3, swf, png</td>\r
- <td>Filetypes that can be uploaded</td>\r
-</tr><tr>\r
- <td>AllowLoginEdit</td>\r
- <td>0</td>\r
- <td>Allow members to edit their login name and password?</td>\r
-</tr><tr>\r
- <td>AllowUpload</td>\r
- <td>1</td>\r
- <td>Allow file uploads?</td>\r
-</tr><tr>\r
- <td class="toremove">DisableJsTools</td>\r
- <td>2</td>\r
- <td>\r
- Style of the javascript toolbar:\r
- <ul>\r
- <li>0: full featured (IE)</li>\r
- <li>1: toolbar disabled</li>\r
- <li>2: simpler (Gecko)</li>\r
- </ul>\r
- </td>\r
-</tr><tr>\r
- <td>CookiePath</td>\r
- <td>/</td>\r
- <td>Path to set cookie on</td>\r
-</tr><tr>\r
- <td>CookiePrefix</td>\r
- <td></td>\r
- <td>String to prefix cookie names with. This is useful when multiple Nucleus installs are on the same domain, as it prevents login sessions to interfere with each other.</td>\r
-</tr><tr>\r
- <td>CookieDomain</td>\r
- <td></td>\r
- <td>Domain to set cookie on</td>\r
-</tr><tr>\r
- <td>CookieSecure</td>\r
- <td>0</td>\r
- <td>Secure cookie (https)</td>\r
-</tr><tr>\r
- <td>MediaPrefix</td>\r
- <td>1</td>\r
- <td>If true, the uploaded files get the current date in their filename.</td>\r
-</tr><tr>\r
- <td>MaxUploadSize</td>\r
- <td>1048576</td>\r
- <td>Max. size of uploaded files (in bytes)</td>\r
-</tr><tr>\r
- <td>NonmemberMail</td>\r
- <td>0</td>\r
- <td>Allow non-members to send e-mail messages to site members?</td>\r
-</tr><tr>\r
- <td>PluginURL</td>\r
- <td></td>\r
- <td>URL of plugin folder. Should end with a slash.</td>\r
-</tr><tr>\r
- <td>ProtectMemNames</td>\r
- <td>1</td>\r
- <td>When this option is enabled, non-logged in members cannot add comments using the same name as registered members. The reason to do this would be to avoid guest impersonating members.</td>\r
-</tr><tr>\r
- <td class="foreign"><a href="#nucleus_skin_desc">BaseSkin</a></td>\r
- <td>1</td>\r
- <td>The option tells Nucleus which skin to fall back to when no such decision can be automatically made. This happens when skin parts are empty, when no blog or skin is implicitly/explicitly selected.</td>\r
-</tr><tr>\r
- <td>SkinsURL</td>\r
- <td></td>\r
- <td>URL of skins folder. Should end with a slash.</td>\r
-</tr><tr>\r
- <td>ActionURL</td>\r
- <td></td>\r
- <td>URL of <code>action.php</code> script.</td>\r
-</tr><tr>\r
- <td>URLMode</td>\r
- <td>normal</td>\r
- <td>either <code>normal</code> or <code>pathinfo</code></td>\r
-</tr><tr>\r
- <td>DatabaseVersion</td>\r
- <td>250</td>\r
- <td>Last Nucleus version for which the database structure has been updated (introduced in Nucleus v2.5)</td>\r
-</tr></table\r
-\r
-<a id="nucleus_tickets" name="nucleus_tickets"></a>\r
-<h1>Table nucleus_tickets<a href="#top" class="toplink"><img src="../icon-up.gif" width="15" height="15" alt="back to top" /></a></h1>\r
-\r
-<p>Nucleus uses the <code>nucleus_tickets</code> to prevent against certain security issues. In particular: each action on the admin area that affects the settings or database contents, requires a ticket. These tickets are generated when requesting an admin area page and passed along with the form. Tickets are destroyed one hour after their creation.</p>\r
-\r
-<table><tr>\r
- <th>Column Name</th>\r
- <th>Type</th>\r
- <th>Default</th>\r
- <th>Description</th>\r
-</tr><tr>\r
- <td class="notnull primary">ticket</td>\r
- <td>varchar(40)</td>\r
- <td></td>\r
- <td>Unique ticket, valid for one particular member. A typical ticket looks like this: <code>65303a785423b4d53c7b3e6579766f26</code></td>\r
-</tr><tr>\r
- <td class="notnull foreign primary"><a href="#nucleus_member">member</a></td>\r
- <td>int(11)</td>\r
- <td></td>\r
- <td>Member for which this ticket is valid.</td>\r
-</tr><tr>\r
- <td class="notnull">ctime</td>\r
- <td>datetime</td>\r
- <td></td>\r
- <td>Time of ticket creation. A ticket is valid no longer than one hour.</td>\r
-</tr></table>\r
-\r
-\r
-<a id="nucleus_activation" name="nucleus_activation"></a>\r
-<h1>Table nucleus_activation<a href="#top" class="toplink"><img src="../icon-up.gif" width="15" height="15" alt="back to top" /></a></h1>\r
-\r
-<p>When a new member registers, Nucleus doesn't allow that member to log in before his account is activated. This activation is done by sending out an activation link to the members email address. The <code>nucleus_activation</code> table keeps track of the activations that are in progress.</p>\r
-\r
-<table><tr>\r
- <th>Column Name</th>\r
- <th>Type</th>\r
- <th>Default</th>\r
- <th>Description</th>\r
-</tr><tr>\r
- <td class="notnull primary">vkey</td>\r
- <td>varchar(40)</td>\r
- <td></td>\r
- <td>Activation key. This key needs to be passed to the member activation code. A typical key looks like this: <code>41cf637d4fbeeff954b4ca70b8bde9dd</code></td>\r
-</tr><tr>\r
- <td class="notnull foreign"><a href="#nucleus_member">vmember</a></td>\r
- <td>int(11)</td>\r
- <td></td>\r
- <td>Member which needs to be activated.</td>\r
-</tr><tr>\r
- <td class="notnull">vtime</td>\r
- <td>datetime</td>\r
- <td></td>\r
- <td>Time at which activation key was generated. Each activation key is valid no longer than 2 days.</td>\r
-</tr><tr>\r
- <td class="notnull">vtype</td>\r
- <td>varchar(15)</td>\r
- <td></td>\r
- <td>Type of activation.\r
- <ul>\r
- <li><code>forgot</code>: member forgot his password.</li>\r
- <li><code>register</code>: new member registration.</li>\r
- <li><code>addresschange</code>: member changed his e-mail address.</li>\r
- </ul>\r
- </td>\r
-</tr><tr>\r
- <td class="notnull">vextra</td>\r
- <td>varchar(128)</td>\r
- <td></td>\r
- <td>Extra information. For an <code>addresschange</code> type of activation, this contains <code>oldemailaddress/x</code> with x either 0 or 1 and refering to the previous value of the <code>mcanlogin</code> field in the <a href="#nucleus_member">member</a> table. (untill fully re-activated, a user cannot login)</td>\r
-</tr></table>\r
-\r
-\r
-<a id="nucleus_karma" name="nucleus_karma"></a>\r
-<h1>Table nucleus_karma<a href="#top" class="toplink"><img src="../icon-up.gif" width="15" height="15" alt="back to top" /></a></h1>\r
-\r
-<p class="toremove">This table will most likely be removed in future Nucleus version, in favor of plugins with the same functionality.</p>\r
-\r
-<p>This table keeps track of IP addresses that have already voted for an item. This way, each IP address can cast only one vote.</p>\r
-\r
-<table><tr>\r
- <th>Column Name</th>\r
- <th>Type</th>\r
- <th>Default</th>\r
- <th>Description</th>\r
-</tr><tr>\r
- <td class="notnull foreign"><a href="#nucleus_item">itemid</a></td>\r
- <td>int(11)</td>\r
- <td>'0'</td>\r
- <td>Item ID</td>\r
-\r
-</tr><tr>\r
- <td class="notnull">ip</td>\r
- <td>char(15)</td>\r
- <td>''</td>\r
- <td>IP address of voter</td>\r
-</tr></table>\r
-\r
-<a id="nucleus_ban" name="nucleus_ban"></a>\r
-<h1>Table nucleus_ban<a href="#top" class="toplink"><img src="../icon-up.gif" width="15" height="15" alt="back to top" /></a></h1>\r
-\r
-<p class="toremove">This table will most likely be removed in future Nucleus version, in favor of plugins with the same functionality.</p>\r
-\r
-<p>IP bans. These people cannot comment or cast karma votes.</p>\r
-\r
-<table><tr>\r
- <th>Column Name</th>\r
- <th>Type</th>\r
- <th>Default</th>\r
- <th>Description</th>\r
-</tr><tr>\r
- <td class="notnull">iprange</td>\r
- <td>varchar(15)</td>\r
- <td>''</td>\r
- <td>IP 'range'. This can either be a full IP address or part of an IP address (starting from the left) to ban ranges</td>\r
-\r
-</tr><tr>\r
- <td class="notnull">reason</td>\r
- <td>varchar(255)</td>\r
- <td>''</td>\r
- <td>A message with the reason why someone was banned. This message will be shown when they try to add a comment/cast a vote.</td>\r
-</tr><tr>\r
- <td class="notnull foreign"><a href="#nucleus_blog">blogid</a></td>\r
- <td>int(11)</td>\r
- <td>'0'</td>\r
- <td>Blog for which the ban is active</td>\r
-</tr></table>\r
-\r
-\r
-</body>\r
-</html>
\ No newline at end of file
+++ /dev/null
-body {\r
- background-color: #fff;\r
- color: #000;\r
- font-family: verdana, arial;\r
- font-size: small;\r
-}\r
-\r
-@media screen {\r
- body {\r
- margin-left: 10%;\r
- margin-right: 10%;\r
- }\r
-}\r
-\r
-@media print {\r
- pre, .note, td, th {\r
- border: 1px dashed gray;\r
- }\r
-}\r
-\r
-img {\r
- border: none;\r
-}\r
-\r
-a:link, a:visited {\r
- color: #1D3565; \r
- font-weight: bold;\r
- text-decoration: none;\r
-}\r
-a: hover {\r
- text-decoration: underline;\r
-}\r
-\r
-.heading {\r
- text-align: center;\r
- font-size: xx-large;\r
- font-weight: bold;\r
- color: gray; \r
-}\r
-\r
-.heading i {\r
- position: absolute;\r
- top: 5px;\r
- right: 5px;\r
- font-size: small;\r
- font-style: normal;\r
- font-weight: normal;\r
-}\r
-\r
-p:first-letter {\r
- font-size: large;\r
-}\r
-\r
-p {\r
- text-indent: 20px;\r
-}\r
-\r
-h1 {\r
- border-bottom: 1px dotted gray;\r
- font-size: x-large;\r
- color: #596d9d;\r
-}\r
-\r
-h2 {\r
- color: gray;\r
- font-size: large;\r
- margin-left: 20px;\r
- text-indent: 10px;\r
- border-bottom: 1px solid #ddd;\r
-}\r
-\r
-pre, .note, .faq .answer {\r
- background-color: #ddd;\r
- padding: 10px;\r
- font-size: small;\r
-}\r
-\r
-.screenshot {\r
- text-align: center;\r
- background-color: #ddd;\r
- padding: 10px;\r
-}\r
-\r
-.faq .question {\r
- font-weight: bold;\r
- margin-bottom: 0px;\r
-}\r
-\r
-.faq .answer {\r
-\r
-}\r
-\r
-.faq {\r
- margin-bottom: 20px;\r
-}\r
-\r
-table {\r
- border: none;\r
-}\r
-\r
-th {\r
- background-color: linen;\r
- font-size: medium;\r
-}\r
-\r
-th, td {\r
- padding: 5px;\r
-}\r
-\r
-td {\r
- background-color: #dddddd;\r
- font-size: small;\r
- vertical-align: top;\r
- text-align: left;\r
-}\r
-\r
-input, select, option, textarea {\r
- background-color: transparent;\r
-}\r
-\r
-.deprecated {\r
- border: 3px solid red;\r
- padding: 5px;\r
- font-size: medium;\r
-}\r
-\r
-tt, code, samp {\r
- font-size: small;\r
-}\r
-\r
-.warning {\r
- color: red;\r
-}\r
-.ok {\r
- color: green;\r
-}\r
-\r
-acronym, abbr {\r
- border-bottom: 1px dotted gray;\r
- cursor: help;\r
-}\r
+++ /dev/null
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">\r
-<html xmlns="http://www.w3.org/1999/xhtml">\r
-<head>\r
- <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />\r
- <title>Nucleus - XML-RPC インターフェイス</title>\r
- <link rel="stylesheet" type="text/css" href="styles/manual.css" />\r
-</head>\r
-<body>\r
-\r
-<div class="heading">\r
-XML-RPC インターフェイス\r
-</div>\r
-\r
-<h1>はじめに</h1>\r
-\r
-<p>\r
-<a href="index.html">開発者マニュアルに戻る</a>\r
-</p>\r
-\r
-<p>\r
-このドキュメントはNucleusが提供するXML-RPCインターフェイスと、生成される<a href="#errorcodes">エラーメッセージ</a>についての解説です。この仕様は将来変更される可能性があることに注意して下さい。\r
-</p>\r
-\r
-<div class="note">\r
-NucleusにおけるXML-RPCインターフェイスのURLは以下のようになります：\r
-<br />\r
-<b>http://www.yourserver.com/yourpath/nucleus/xmlrpc/server.php</b>\r
-\r
-</div>\r
-\r
-<a name="bloggerApi" id="bloggerApi"></a>\r
-<h1>Blogger API (XML-RPC)</h1>\r
-\r
-<p>\r
-Nucleusは<a href="http://www.blogger.com/developers/api/1_docs/">Blogger API</a>に対応しています。これはBloggerと通信するツールやサービスに対して、Nucleusとも通信できるようにするものです。Nucleusの仕様により、いくつかのパラメータに若干の違いがあります。これについては後述の説明を参照して下さい。呼び出しや応答のメソッドは、もちろん、Bloggerのものと同じ構造になっています。\r
-</p>\r
-\r
-<p>\r
-ここに挙げたリストは利用できるメソッドの一覧です。クリックするとさらに詳しい情報を得ることができます（それぞれのリンク先はBlogger APIの仕様書やその<a href="http://groups.yahoo.com/group/bloggerDev">メーリングリスト</a>です）。\r
-</p>\r
-\r
-<ul>\r
- <li><b><a href="http://www.blogger.com/developers/api/1_docs/xmlrpc_newPost.html">blogger.newPost</a></b></li>\r
- <li><b><a href="http://www.blogger.com/developers/api/1_docs/xmlrpc_editPost.html">blogger.editPost</a></b></li>\r
-\r
- <li><b><a href="http://groups.yahoo.com/group/bloggerDev/message/296">blogger.getPost</a></b></li>\r
- <li><b><a href="http://groups.yahoo.com/group/bloggerDev/message/147">blogger.deletePost</a></b></li>\r
- <li><b><a href="http://www.blogger.com/developers/api/1_docs/xmlrpc_getUsersBlogs.html">blogger.getUsersBlogs</a></b></li>\r
-\r
- <li><b><a href="http://groups.yahoo.com/group/bloggerDev/message/225">blogger.getRecentPosts</a></b></li>\r
- <li><b><a href="http://groups.yahoo.com/group/bloggerDev/message/315">blogger.getUserInfo</a></b></li>\r
- <li><b><a href="http://www.blogger.com/developers/api/1_docs/xmlrpc_getTemplate.html">blogger.getTemplate</a></b></li>\r
- <li><b><a href="http://www.blogger.com/developers/api/1_docs/xmlrpc_setTemplate.html">blogger.setTemplate</a></b></li>\r
-</ul>\r
-\r
-\r
-<p>\r
-Nucleusは内部的に異なる実装を用いているため、パラメータの扱いに若干の違いがあります。概説すると：\r
-\r
-</p>\r
-\r
-<ul>\r
- <li>Appkeyは無視されます。</li>\r
- <li>Nucleusの場合は本文のあとにタイトルとカテゴリが続きます。Bloggerでは 'コンテンツ' と呼ばれるは本文だけが存在します。これらの追加されたパーツを利用可能にするため、<tt><title></tt>や<tt><category></tt>をNucleusに送るコンテンツに含めることができます。これらのタグは getRecentPosts の呼び出しでのみ追加されます。</li>\r
- <li>Bloggerで 'templates' と呼ばれているものに相当するのが、Nucleusの 'スキン' です。ひとつのシステムに複数のスキンを設定でき、それぞれのスキンをblogごとに使い分けることができます。メソッド blogger.setTemplate と blogger.getTemplate は、Nucleusのblog設定で選択されているblogのデフォルトスキンに影響します。'main' と 'archiveIndex' の二種類のテンプレートは、Nucleusの 'メインの目次ページ' と '月別アーカイブ一覧ページ' に相当します。（<em>訳注： Blogger の仕様がわからないので、この項不確か</em>)</li>\r
-\r
- <li>項目 <tt>publish</tt> は、追加した項目がデフォルトでドラフトになるか公開になるかを決める箇所です。<tt>blogger.editPost</tt> を使う場合は、<tt>publish</tt> がドラフトと公開のどちらになっていても無視されます。</li>\r
- <li><tt>getUserInfo</tt> を呼び出した場合、返値のうち 'lastname' は空になり、'firstname' にフルネームが入ります。これはNucleusが姓と名を分けない仕様になっていることに由来します。</li>\r
-\r
- <li>メソッド <tt>getRecentPostst</tt> は <tt>authorName</tt> と <tt>title</tt> を追加パラメータとして返します。Bloggerもまたこれらの値を返します（この仕様は文書化されていないようですが）。</li>\r
-</ul>\r
-\r
-<a name="metaWeblogApi" id="metaWeblogApi"></a>\r
-<h1><a name="metaweblog"></a>metaWeblog API</h1>\r
-\r
-<p>\r
-Nucleus v1.1以降、<a href="http://www.xmlrpc.com/metaWeblogApi">metaWeblog API</a>もサポートされました。これはBlogger APIの拡張版です。 \r
-</p>\r
-\r
-<p>\r
-Nucleus v2.5では <code>newMediaObject</code> と <code>getRecentPosts</code> の二つのメソッドにも対応しました（これらは最初のmetaWeblog仕様には存在しませんでした）。\r
-</p>\r
-\r
-<p>\r
-利用可能なメソッド一覧は以下の通りです（<a href="http://www.xmlrpc.com/metaWeblogApi">specification</a>に詳しい情報があります）：\r
-</p>\r
-\r
-<ul>\r
- <li>metaWeblog.newPost</li>\r
- <li>metaWeblog.editPost</li> \r
- <li>metaWeblog.getPost</li> \r
- <li>metaWeblog.getCategories</li> \r
- <li>metaWeblog.newMediaObject (v2.5)</li>\r
- <li>metaWeblog.getRecentPosts (v2.5)</li> \r
-\r
-</ul>\r
-\r
-<a name="mtApi" id="mtApi"></a>\r
-<h1>Movable Type API</h1>\r
-\r
-<p>v2.5から、Nucleusは<a href="http://www.movabletype.org/docs/mtmanual_programmatic.html">Movable Type API</a>からのメソッドをサポートするようになりました。</p>\r
-\r
-<p>利用できるメソッドの一覧を以下に示します：</p>\r
-\r
-<ul>\r
- <li>mt.supportedMethods</li>\r
-\r
- <li>mt.supportedTextFilters</li>\r
- <li>mt.publishPost</li>\r
- <li>mt.getCategoryList</li>\r
- <li>mt.getPostCategories</li>\r
- <li>mt.setPostCategories</li>\r
- <li>mt.getRecentPostTitles</li>\r
-\r
- <li>mt.getTrackbackPings</li>\r
-</ul>\r
-\r
-<p>いくつかのノート：</p>\r
-\r
-<ul>\r
- <li>Nucleusはアイテムひとつにつき一つだけカテゴリを設定することができます。これは 'primary' 以外のカテゴリ設定項目はすべて無視されることを意味します。</li>\r
- <li>トラックバックはNucleusのコアではサポート対象外です（プラグインの導入によって利用することができるようになります）。このため、<code>mt.getTrackbackPings</code> のデフォルトの返値は空です。</li>\r
-\r
- <li>Nucleusはテキストフィルタを実装していません。このため、<code>mt.getSupportedTextFilters</code> は空の値を返します。</li>\r
-</ul>\r
-\r
-<h1><a name="errorcodes"></a>エラーコード</h1>\r
-\r
-<p>\r
-以下に示すのは、それぞれのメソッドから得られるエラーの種類です：\r
-</p>\r
-\r
-<table>\r
- <tr>\r
-\r
- <th>エラーコード</th>\r
- <th>エラーメッセージ</th>\r
- </tr>\r
- <tr>\r
- <td>801</td>\r
- <td>Login Error <br />\r
- ログインエラー（ユーザ名とパスワードの組み合わせが正しくないと推測されます）</td>\r
- </tr>\r
-\r
- <tr>\r
- <td>802</td>\r
- <td>No Such Blog<br />\r
- 指定されたBlogは存在しません</td>\r
- </tr>\r
- <tr>\r
- <td>803</td>\r
- <td>Not a Team Member<br />\r
- チームに登録されていません</td>\r
-\r
- </tr>\r
- <tr>\r
- <td>804</td>\r
- <td>Cannot add Empty Items<br />\r
- 空のアイテムは投稿できません</td>\r
- </tr>\r
- <tr>\r
- <td>805</td>\r
-\r
- <td>Amount parameter must be in range 1..20<br />\r
- パラメータの値は 1..20 の範囲でなければなりません（<i>getRecentItems</i></td>\r
- </tr>\r
- <tr>\r
- <td>806</td>\r
- <td>No Such Item<br />\r
- 指定されたアイテムは存在しません</td>\r
- </tr>\r
-\r
- <tr>\r
- <td>807</td>\r
- <td>Not Allowed to Alter Item<br />\r
- アイテム追加の権限がありません</td>\r
- </tr>\r
- <tr>\r
- <td>808</td>\r
- <td>Invalid media type<br />\r
- メディアタイプが不正です</td>\r
-\r
- </tr> \r
- <tr>\r
- <td>809</td>\r
- <td>File is too large<br />\r
- ファイルが大きすぎます（最大のアップロードファイルサイズ）</td>\r
- </tr> \r
- <tr>\r
- <td>810</td>\r
- <td>Other error on newMediaObject<br />\r
- newMediaObject で予期せぬエラーが発生しました（何が起きたのかもう少し情報が含まれるでしょう）</td>\r
-\r
- </tr>\r
- <tr>\r
- <td><i>その他のコード < 100</i></td>\r
- <td>Errors encountered by the Useful Inc. XML-RPC implementation<br />\r
- Usefil Inc. XML-RPC の実行でエラーが発生しました</td>\r
- </tr>\r
- <tr>\r
- <td><i>その他のコード > 100</i></td>\r
-\r
- <td>Errors encountered by the XML parser<br />\r
- XML パーサでエラーが発生しました</td>\r
- </tr>\r
-\r
-\r
-</table>\r
-\r
-</body>\r
-</html>\r
+++ /dev/null
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">\r
-<html xmlns="http://www.w3.org/1999/xhtml">\r
-<head>\r
- <!-- $Id: help.html,v 1.6 2005-03-19 07:28:32 kimitake Exp $ -->\r
-\r
- <title>Nucleus Admin Help</title>\r
- <style type="text/css">\r
- <!--\r
- body {\r
- font-family: verdana, arial;\r
- font-size: small;\r
- }\r
-\r
- h1 {\r
- font-size: large;\r
- border-bottom: 1px gray dashed;\r
- color: #596d9d;\r
- text-align: left;\r
- }\r
-\r
- h2 {\r
- font-size: medium;\r
- border: 1px solid #ddd;\r
- background-color: whitesmoke;\r
- text-align: left;\r
- }\r
-\r
- .page {\r
- height: 800px;\r
- text-align: justify;\r
- margin-bottom: 100px;\r
- }\r
-\r
- pre {\r
- background-color: #ddd;\r
- padding: 5px;\r
- font-size: small;\r
- }\r
-\r
- .example {\r
- background-color: #ddd;\r
- padding: 5px;\r
- }\r
-\r
- ul.templates {\r
- font-size: x-small;\r
- line-height: 1.1;\r
- list-style: none;\r
- text-indent: -20px;\r
- margin-left: 20px;\r
- }\r
-\r
- ul {\r
- text-align: left;\r
- }\r
-\r
- a:link, a:visited {\r
- color: #1D3565;\r
- font-weight: bold;\r
- text-decoration: underline;\r
- }\r
-\r
- a:hover {\r
- background-color: whitesmoke;\r
- }\r
-\r
- .deprecated {\r
- border: 3px solid red;\r
- padding: 5px;\r
- font-size: medium;\r
- }\r
-\r
- tt, code {\r
- font-size: small;\r
- }\r
-\r
- table {\r
- border: 1px solid #ccc;\r
- }\r
-\r
- th {\r
- background-color: #eee;\r
- }\r
-\r
- td {\r
- vertical-align: top;\r
- }\r
-\r
- .note {\r
- background-color: #eee;\r
- padding: 5px;\r
- }\r
- -->\r
- </style>\r
-</head>\r
-<body>\r
-\r
-<div class="page">\r
-<h1>Nucleus Popup Help</h1>\r
-<p>Please hold on while the page is being downloaded (about 100KB).</p>\r
-</div>\r
-\r
-\r
-<div class="page">\r
-<a name="future"></a>\r
-<a name="allowpastposting"></a>\r
-<h1>Add Later/Earlier</h1>\r
-<h2>Add Later</h2>\r
-<p>The 'Add Later' option on add-item forms allows you to mark an item to become visible only at the exact time you've specified. Before that time has come, the item will not be viewable anywhere in the public part of your site.</p>\r
-<p>This date <strong>must</strong> be in the future, unless the 'Allow posting to the past' option is enabled for the blog to which you want to add the item.</p>\r
-<h2>Allow posting to the past</h2>\r
-<p>When enabled, you'll be allowed to specify the date on which an item should be added, and to edit the timestamp of already existing items.</p>\r
-</div>\r
-\r
-<div class="page"><a name="changedate"></a>\r
-<h1>Change post date/time</h1>\r
-<p>\r
-The 'Update Timestamp' option allows you to change the posting date and/or time of an item. If you changed the content of an item, this is a way bring the story back to the top of your front page.</p>\r
-<p>But, the unique id connected to the item will not change, so your visitors can still find out that the item was originally posted later than items with a lower id.</p>\r
-</div>\r
-\r
-\r
-<div class="page"><a name="draft"></a>\r
-<h1>Drafts</h1>\r
-<p>\r
-Draft items are not yet viewable in the public blog. They might come in handy when you are working on a story, and something comes in between. Your draft items will be listed on the main page, so you can continue your work when you have the time to do so.</p>\r
-<p>When editing drafts, choose the '<strong>Add now</strong>' radiobutton and hit the 'Edit item' button to make them visible.\r
-</p>\r
-</div>\r
-\r
-<div class="page"><a name="extended"></a>\r
-<h1>Extended part</h1>\r
-<p>\r
-Items have an optional extended part that you can use for continued stories. e.g. when a story is too long to put on the main page of your blog, you can write an introduction in the body part and the rest in the extended part. When viewing your main blog page, you will then see 'read more' links (as defined by the templates).\r
-</p>\r
-<p>\r
-If you want to write an introduction only for <em>some</em> of your items, you could use the <a href="#templatevar-smartbody">smartbody</a> template variable to make a selection out of the body text and the extended text.\r
-</p>\r
-</div>\r
-\r
-<div class="page"><a name="shortblogname"></a>\r
-<h1>Short Blog Name</h1>\r
-<p>\r
-The short blog name is used mainly in the admin area to indicate which items are associated with which blog.\r
-</p>\r
-<p>\r
-It can also be used in alternative index files, to make a second weblog available:\r
-</p>\r
-<pre>\r
-<?\r
- include('./config.php');\r
- selectBlog('myshortblogname');\r
- selector();\r
-?>\r
-</pre>\r
-</div>\r
-\r
-<div class="page"><a name="blogdefaultskin"></a>\r
-<h1>Default Skin</h1>\r
-<p>\r
-The default skin selected in the blog settings is the skin that should be used when the blog is displayed, and there is no other skin selected (through arguments in the URL)\r
-</p>\r
-</div>\r
-\r
-\r
-<div class="page"><a name="blognotify"></a>\r
-<h1>Notify Address</h1>\r
-<p>\r
-This option contains one or multiple e-mail addresses to which notification e-mails should be sent when new comments are added. Leave empty if you don't want notification. The given e-mail addresses must, of course, be valid.\r
-</p>\r
-<p>\r
-If you're using multiple addresses, you should use a semicolon (<strong>;</strong>) as a separator.\r
-</p>\r
-<div class="note">\r
-<b>Note:</b> As the maximum length of the settings fields is 128 characters, there's only a limited amount of e-mail addresses you can list.\r
-</div>\r
-<div class="note">\r
-<b>Note:</b> When you set up your own e-mail address as notification address, you won't get notified of the items/comments that you wrote yourself. Assuming that you know what you wrote, that shouldn't be a problem.\r
-</div>\r
-</div>\r
-\r
-<div class="page"><a name="blogmaxcomments"></a>\r
-<h1>Max Amount of Comments</h1>\r
-<p>\r
-This is the maximum number of comments that will be shown on the <em>main page</em>. <strong>This is NOT a restriction on the total number of comments that can be made</strong>. On the detail pages, all comments will be shown, even if there are more than the maximum amount chosen.\r
-</p>\r
-<p class="note"><strong>Note:</strong>\r
-Inside templates, this variable can be overridden by an optional parameter of the <a href="#templatevar-comments">comments</a> templatevar.\r
-</p>\r
-</div>\r
-\r
-<div class="page"><a name="blogtimeoffset"></a>\r
-<h1>Time Offset</h1>\r
-<p>\r
-If the time on your server is not equal to the time where you live, you might want to add an offset to the server time in order to get the correct time. Use negative values to subtract (negation sign). The current server time is listed as a reference.\r
-</p>\r
-<h2>Example</h2>\r
-<p>If your local time is 20:35 and the server time is listed as 14:35, you'll need to set the time offset equal to 6 in order to get your blog time to 20:35\r
-</p>\r
-<p class="note"><strong>Note:</strong> Fractional offsets can be used as well, for people living in half time zones. e.g. an offset of <strong>1.5</strong> equals an offset of 1 hour and 30 minutes.</p>\r
-</div>\r
-\r
-<div class="page"><a name="blogupdatefile"></a>\r
-<h1>Update File</h1>\r
-<p>\r
-Nucleus can edit a file for you whenever a new item is added to the blog. The contents of that file will be a timestamp of the last change. The use of such a file could be useful for services which check a file on your server once in a while to see if there were updates, and generate 'updated weblogs' from that. Pointing them to your main blog could cause false update warnings to be sent out when visitors add comments or when you change something to the skins or templates.\r
-</p>\r
-<p>\r
-When you don't need an update file, just leave the field empty.\r
-</p>\r
-<p>\r
-Please note that the location of the update file is relative to the admin-area, so you might want to use an absolute path (something like <tt>/path/to/your/website/update.txt</tt>). Also make sure the update file already exists and is writable (<a href="tips.html#filepermissions" onclick="window.open(this.href);return false;" class="out" title="quick guide on changing file permissions">chmod it to 666</a> if you want to be sure).\r
-</p>\r
-</div>\r
-\r
-<div class="page"><a name="teamadmin"></a>\r
-<h1>Blog Admin</h1>\r
-<p>\r
-Blog administrators have the following extra rights:\r
-</p>\r
-\r
-<ul>\r
- <li>They can manage the team</li>\r
- <li>They can edit blog settings</li>\r
- <li>They can edit/delete all items by all authors (from the blog of which they are admin)</li>\r
- <li>They can delete the blog</li>\r
-</ul>\r
-\r
-<p>\r
-A blog can have multiple admins, but there must be at least one admin at all times.\r
-</p>\r
-</div>\r
-\r
-\r
-<div class="page"><a name="superadmin"></a>\r
-<h1>Administrator Privileges</h1>\r
-\r
-<p>\r
-A so called <em>super-admin</em> has <strong>full access</strong> to all functions and all weblogs, even if she is not on the blog team.\r
-</p>\r
-\r
-<p>\r
-On top of that: a super-admin has the right to create new weblogs, to change general settings, to change templates, to change skins and to manage the members (creation/ manipulation/ deletion of members).\r
-</p>\r
-\r
-<p>\r
-Usually, there will be only one super-admin, the site administrator.\r
-</p>\r
-\r
-</div>\r
-\r
-<div class="page"><a name="canlogin"></a>\r
-<h1>Can Login?</h1>\r
-<p>\r
-As a <a href="#superadmin" title="Administrator Privileges">superadmin</a>, you can disallow individual members to login to the admin area.\r
-</p>\r
-</div>\r
-\r
-<div class="page"><a name="defaultblog"></a>\r
-<h1>Default Blog</h1>\r
-<p>\r
-This is the blog that will be used when no other blog has been specified in the request.\r
-</p>\r
-</div>\r
-\r
-<div class="page"><a name="baseskin"></a>\r
-<h1>Base Skin</h1>\r
-\r
-<p>The option tells Nucleus which skin to fall back to when no such decision can be automatically made. This happens when skin parts are empty, when no blog or skin is implicitly/explicitly selected.</p>\r
-<p>Most users don't need to worry about this setting.</p>\r
-</div>\r
-\r
-<div class="page"><a name="cookies"></a>\r
-<h1>Cookies</h1>\r
-\r
-<h2>Cookie Lifetime</h2>\r
-<p>\r
-When a member logs in, a cookie is stored in his browser, so she doesn't need to log in again when she comes back the next day. The lifetime of this cookie decided when it will become invalid:</p>\r
-<ul>\r
- <li><strong>Session cookies</strong> get deleted when you exit the browser</li>\r
- <li>Cookies with a lifetime of <strong>one month</strong> will stay on the computer until you don't use/visit the site for a month. Using this option, you'll never have to login again (unless you've logged out yourself, or logged in from another computer)</li>\r
-</ul>\r
-\r
-<h2>Cookie Path & Cookie Domain</h2>\r
-<p>\r
-These settings are advanced settings. Normally, you shouldn't change them at all. In that case, cookie path is a simple slash ('/') and cookie domain is empty.\r
-</p>\r
-\r
-<h2>Secure Cookies</h2>\r
-<p>\r
-Normally, this should be set to 'no'. You should only set it to 'yes' when you have a HTTPS url and want cookies only to be sent over such a https connection.\r
-</p>\r
-\r
-<h2>'Last Visit' Cookie</h2>\r
-<p>\r
-You can setup Nucleus to store a cookie in which the time of the visitors last visit is stored. This can be used to put indications next to <a href="#templatenew">new items</a>\r
-</p>\r
-\r
-</div>\r
-\r
-\r
-<div class="page"><a name="language"></a>\r
-<h1>Language</h1>\r
-<p>\r
-You can choose a language to be used when nucleus creates content for you. The content generated by Nucleus includes the admin-area, the error messages, forms in skins, ...\r
-</p>\r
-\r
-<p>\r
-There are two places where a language can be chosen: the global site settings include a language option.\r
-Next to that, logged in members can override this setting if they want to.\r
-</p>\r
-\r
-<p>\r
-When both of these settings are invalid, 'english' is used as the default language.\r
-</p>\r
-\r
-<p class="note"><strong>Note:</strong> Extra language files can be downloaded from the <a href="http://www.nucleuscms.org/" onclick="window.open(this.href);return false;" class="out" title="Nucleus CMS Website">Nucleus Website</a>. (opens a new window)</p>\r
-\r
-</div>\r
-\r
-<div class="page"><a name="allowaccountcreation"></a>\r
-<h1>Account Creation</h1>\r
-<p>\r
-You can either allow or disallow your visitors to create their own 'member' account. They won't be allowed to add items to a blog (unless the admin adds them to a team), but they can login to the administration area and change their settings, and even delete or modify the comments they made.\r
-</p>\r
-</div>\r
-\r
-<div class="page"><a name="allownewmemberlogin"></a>\r
-<h1>New Member: can login ?</h1>\r
-<p>\r
-When you allow <a href="#allowaccountcreation">creation of member accounts</a> by your visitors, this setting defines whether or not accounts created in that way will have the ability to <a href="#canlogin">login to the administration area</a>.\r
-</p>\r
-</div>\r
-\r
-\r
-<div class="page"><a name="messageservice"></a>\r
-<h1>Message Service</h1>\r
-\r
-<p>\r
-For the privacy of your members, you can hide all e-mail addresses and allow members to send an e-mail message to each other through the script. The message that will be sent out will however contain the e-mail addresses of both users, so they can then do continued communication through regular e-mail. This service can be disabled.\r
-</p>\r
-\r
-<h2>Non-members</h2>\r
-<p>\r
-By default, non members cannot use the message service (because there's no way to check the validity of the e-mail address they enter). You can relax this restriction by allowing non-members to use the message service too. When submitting a message, they will be asked to enter their e-mail address, which will show up in the <tt>From:</tt> headers of the e-mail you receive.\r
-</p>\r
-\r
-</div>\r
-\r
-<div class="page"><a name="disablesite"></a>\r
-<h1>Disable Site</h1>\r
-<p>\r
-It's possible to disable your entire Nucleus site. You might want to do this when you are doing some configuration, or when something went horribly wrong :-)\r
-</p>\r
-<p>\r
-The URL that needs to be configured is an URL to which the visitor will be redirected.\r
-</p>\r
-<p>\r
-Exceptions: the <strong>admin-area</strong> is still available, and <strong><a href="#superadmin">super-admins</a></strong> can still see the entire site. (don't forget to re-enable your site afterwards ;-))\r
-</p>\r
-</div>\r
-\r
-\r
-<div class="page"><a name="urlmode"></a>\r
-<h1>URL Mode</h1>\r
-<p>Using this option, you can switch between URL styles:</p>\r
-<ul>\r
- <li><strong>Normal</strong>: URLs looking like <code>http://host/index.php?itemid=1234</code></li>\r
- <li><strong>Fancy</strong>: URLs looking like <code>http://host/item/1234</code></li>\r
-</ul>\r
-<p class="note"><strong>Note:</strong> In order to get the 'Fancy URL' mode working, some extra actions are required. They're described in the <a href="tips.html" class="out" onclick="window.open(this.href);return false;">Tips & Suggestions</a> (opens in new window)</p>\r
-\r
-</div>\r
-\r
-<div class="page"><a name="templateitems"></a>\r
-<h1>Templates: Items</h1>\r
-<p>\r
-When items are shown, the following setup is repeated for each item:\r
-</p>\r
-\r
-<pre>\r
-item header\r
-item body\r
-item footer\r
-</pre>\r
-\r
-<p>These three blocks all refer to a template-part, which define what the result looks like.</p>\r
-\r
-<h2>Variables</h2>\r
-\r
-<p>Within these template, a series of so called <a href="#templatevars-overview" title="Find out which variables are available">template variables can be used</a> to insert item data.</p>\r
-\r
-<h2>Example</h2>\r
-<p><a href="#templateitemsexample">An example</a></p>\r
-\r
-</div>\r
-\r
-<div class="page"><a name="templateitemsexample"></a>\r
-<h1>Templates: Items</h1>\r
-<p>\r
-An example for the <b>item body</b> template:\r
-</p>\r
-\r
-<pre><h1><%title%></h1>\r
-\r
-<p><%body%></p>\r
-\r
-<div class="metadata">\r
- <a href="<%itemlink%>">link</a> -\r
- <%date%> <%time%> -\r
- <a href="<%authorlink%>"><%author%></a> -\r
- <%comments%>\r
-</div></pre>\r
-\r
-<p>The result would become something like this:</p>\r
-\r
-<div class="example">\r
-<h4 style="margin: 2px;">This is an item</h4>\r
-<p style="margin: 2px; padding: 0px;">This is the text for the item</p>\r
-<div style="font-style: italic; margin: 2px;">\r
- <a href="#templateitemsexample">link</a> -\r
- August 8th 2002 18:51 -\r
- <a href="#templateitemsexample">karma</a> -\r
- <a href="#templateitemsexample">no comments</a>\r
-</div>\r
-</div>\r
-\r
-</div>\r
-\r
-\r
-<div class="page"><a name="templatecomments"></a>\r
-<h1>Templates: comments</h1>\r
-\r
-<p>There are three possible structures for a comments block.</p>\r
-\r
-<ol>\r
- <li>\r
- When comments are displayed (like on detail pages, or on the main page when there are less than the maximum allowed amount of comments)\r
-<pre>comments header\r
- comments body (repeated)\r
-comments footer</pre>\r
- </li>\r
- <li>\r
- When there are no comments at all\r
-<pre>\r
-no comments\r
-</pre>\r
- </li>\r
- <li>\r
- When there are comments, but there are more than the maximum allowed number. (only applies when not on a detailed item page)\r
-<pre>\r
-too much comments\r
-</pre>\r
- </li>\r
-</ol>\r
-\r
-<p>Inside these template-parts, some <a href="#templatevars-comments" title="Overview of comments-related template variables">comments-related variables</a> are available</p>\r
-\r
-</div>\r
-\r
-<div class="page">\r
-<a name="templatecommentheaders"></a>\r
-<a name="templatecommentfooters"></a>\r
-<h1>Templates: Comment headers/footers</h1>\r
-\r
-<h2>Description</h2>\r
-\r
-<p>While the comments-body is repeated for each comment, the header and footer are only displayed once. A typicall structure would look like this:</p>\r
-<pre>comments header\r
- comments body 1\r
- comments body 2\r
- comments body 3\r
-comments footer</pre>\r
-<p>In these template-parts, <a href="#templatevars-comments" title="Overview of comments-related template variables">comments-related templatevars</a> are available</p>\r
-\r
-<h2>Examples</h2>\r
-\r
-<p>Header:</p>\r
-<pre><ul></pre>\r
-<p>Body:</p>\r
-<pre><li><%user%>: <%body%></li></pre>\r
-<p>Footer</p>\r
-<pre></ul></pre>\r
-<p>Result</p>\r
-\r
-<ul class="example">\r
- <li>karma: nice!</li>\r
- <li>xiffy: yes indeed!</li>\r
-</ul>\r
-\r
-</div>\r
-\r
-<div class="page"><a name="templatemorelink"></a>\r
-<h1>Templates: Link to extended entry</h1>\r
-<p>\r
-This is the template that will be used to format the <a href="#templatevar-morelink">morelink templatevar</a> that is available in the item templates. <a href="#templatevars-overview">Available variables</a> are the same as in the item templates.\r
-</p>\r
-<p>\r
-When there's no extended part of the item, the <code><%morelink%></code> templatevar will have no effect.\r
-</p>\r
-\r
-<h2>Example</h2>\r
-<pre><code><a href="<%itemlink%>">[Read More!]</a></code></pre>\r
-\r
-</div>\r
-\r
-<div class="page"><a name="templatearchivelists"></a>\r
-\r
-<h1>Templates: Archive Lists</h1>\r
-\r
-<p>The archive lists are formatted as listed below:</p>\r
-\r
-<pre>archivelist header\r
- archivelist listitem (repeated for each archive)\r
-archivelist footer</pre>\r
-\r
-<p>\r
-Available variables: (in the header and footer, only <tt>blogid</tt> is allowed)\r
-</p>\r
-\r
-<table><tr>\r
- <th>Name</th>\r
- <th>Description</th>\r
-</tr><tr>\r
- <td>blogid</td>\r
- <td>ID of the weblog</td>\r
-</tr><tr>\r
- <td>archivelink</td>\r
- <td>link to the archive, which you can embed in a <code><a href=".."></code> tag.</td>\r
-</tr><tr>\r
- <td>month</td>\r
- <td>Number of the month (2 digits: 01-12)</td>\r
-</tr><tr>\r
- <td>year</td>\r
- <td>Year (4 digits)</td>\r
-</tr><tr>\r
- <td>day</td>\r
- <td>Day of month (2 digits; only when in day mode)</td>\r
-</tr></table>\r
-\r
-<p>A more flexible way to add the date of the archive to the listitem, is to use <a href="#strftime">strftime</a> variables. If you find this too complicated, use the following:</p>\r
-\r
-<pre><code><a href="<%archivelink%>">%B, %Y</a><br /></code></pre>\r
-\r
-\r
-<p>To change the language to your local settings, change the <a href="#templatelocale">locale</a>.</p>\r
-\r
-</div>\r
-\r
-\r
-\r
-\r
-<div class="page"><a name="templatecategorylists"></a>\r
-<h1>Templates: Category Lists</h1>\r
-\r
-<p>The category lists are formatted as listed below:</p>\r
-\r
-<pre>categorylist header\r
- categorylist listitem (repeated)\r
-categorylist footer</pre>\r
-\r
-<p>Available variables: (in the header and footer, only <tt>blogid</tt>, <tt>blogurl</tt> and <tt>self</tt> are allowed)</p>\r
-\r
-<table><tr>\r
- <th>Name</th>\r
- <th>Description</th>\r
-</tr><tr>\r
- <td>blogid</td>\r
- <td>ID of the weblog</td>\r
-</tr><tr>\r
- <td>blogurl</td>\r
- <td>URL of the blog (as defined in blogsettings)</td>\r
-</tr><tr>\r
- <td>self</td>\r
- <td>Current page, without parameters (e.g. <tt>index.php</tt>)</td>\r
-</tr><tr>\r
- <td>catlink</td>\r
- <td>a link to the most recent items for a category, which you can embed in a <a href=".."> tag.</td>\r
-</tr><tr>\r
- <td>catid</td>\r
- <td>Category ID</td>\r
-</tr><tr>\r
- <td>catname</td>\r
- <td>Category name</td>\r
-</tr><tr>\r
- <td>catdesc</td>\r
- <td>Category description</td>\r
-</tr></table>\r
-\r
-<p><a href="#categorylistexample">View an example</a></p>\r
-\r
-</div>\r
-\r
-<div class="page"><a name="categorylistexample"></a>\r
-<h1>Templates: Category Lists Example</h1>\r
-<p>\r
-<a href="#templatecategorylists">(go back)</a>\r
-</p>\r
-\r
-<h2>Header</h2>\r
-<pre><code><ul>\r
- <li><a href="<blogurl%>">All</a></li></code></pre>\r
-\r
-<h2>List Item</h2>\r
-<pre><code><li><a href="<%catlink%>"><%catname%></a></li></code></pre>\r
-\r
-<h2>Footer</h2>\r
-<pre><code></ul></code></pre>\r
-\r
-<h2>Results in:</h2>\r
-\r
-<ul class="example">\r
- <li><a href="#categorylistexample">All</a></li>\r
- <li><a href="#categorylistexample">myCategory</a></li>\r
- <li><a href="#categorylistexample">yourCategory</a></li>\r
-</ul>\r
-\r
-</div>\r
-\r
-\r
-\r
-\r
-\r
-\r
-\r
-<div class="page"><a name="templatelocale"></a>\r
-<h1>Templates: Locale</h1>\r
-<p>\r
-This is actually not a template-part, it's a setting. Setting it allows the date and time preferences when to be localized. Names of months and days will be in the desired language, etc.\r
-</p>\r
-\r
-<p>\r
-The possible values depend according to which machine Nucleus is running on. Some possible values are\r
-</p>\r
-\r
-<ul>\r
- <li><strong>en</strong>: English</li>\r
- <li><strong>dutch</strong>: Dutch</li>\r
- <li>...</li>\r
-</ul>\r
-\r
-<p>\r
-More info in the <a href="http://www.opengroup.org/onlinepubs/7908799/xsh/strftime.html" onclick="window.open(this.href);return false;" class="out" title="Open Group specification">Open Group Specification</a> for strftime. (opens a new window)\r
-</p>\r
-\r
-<p>\r
-The locale is used for the <a href="#templatedatetime">date and time format</a>, for the <a href="#templatedateheads">dateheaders</a>, and for the <a href="#templatearchivelists">archivelist items</a>\r
-</p>\r
-\r
-</div>\r
-\r
-<div class="page"><a name="templatedatetime"></a>\r
-<h1>Templates: Date and Time formats</h1>\r
-<p>\r
-These are used to format dates and times into the <code><%date%></code> and <code><%time%></code> vars (see <a href="#templatevars-overview">template vars</a>). The formatting is done according to the <a href="#templatelocale">locale</a>\r
-</p>\r
-\r
-<p>\r
-<a href="#strftime">More info on the available vars</a>. If want to get started quickly, use "%x" to format the date and "%X" to format the time.\r
-</p>\r
-\r
-</div>\r
-\r
-<div class="page"><a name="templatedateheads"></a>\r
-<h1>Template: Date headers/footers</h1>\r
-\r
-<p>\r
-The date header and date footer can contain date and time vars. <a href="#strftime">More info on the available vars</a>. If you want to get started quickly, use "%x" to format the date. The language which is used to format the date, is determined by the <a href="#templatelocale">locale-setting</a> in the template.</p>\r
-\r
-<p>\r
-In the date header, the template variable <%%daylink%%> is allowed to insert a link to the archive for that day. <strong>Note the double '%'! It's necessary to avoid %d to be expanded as the current day of the month.</strong> Also, if you just want to add a '%' character somewhere, you should also put it twice ('%%') or it will be gone on your website.\r
-</p>\r
-\r
-<p>\r
-Sample for date header:\r
-</p>\r
-\r
-<pre>\r
-<div class="day">\r
-<h1>%d %B</h1>\r
-</pre>\r
-\r
-<p>\r
-Sample for date footer:\r
-</p>\r
-\r
-<pre>\r
-</div>\r
-</pre>\r
-\r
-<p>And another example for the date head using daylink</p>\r
-\r
-<pre>\r
-<div class="day">\r
-<h1>%d %B</h1>\r
-<a href="<%%daylink%%>">(archive)</a>\r
-</pre>\r
-\r
-</div>\r
-\r
-<div class="page"><a name="templatehighlight"></a>\r
-<h1>Templates: Highlight</h1>\r
-<p>\r
-The highlighting is used when performing searches. This is actually used in a regular expression, so you might want to escape some characters by putting a backslash before them. The place where the highlighted word will come, is indicated by "\0".\r
-</p>\r
-\r
-<h2>Example</h2>\r
-\r
-<pre><code><span style='background-color:yellow'>\0</span></code></pre>\r
-\r
-</div>\r
-\r
-<div class="page"><a name="templatenothingfound"></a>\r
-<h1>Templates: nothing found</h1>\r
-\r
-<p>\r
-Shown when a search has been performed and no results were found.\r
-</p>\r
-\r
-<p>Available variables:</p>\r
-\r
-<table><tr>\r
- <th>Name</th>\r
- <th>Description</th>\r
-</tr><tr>\r
- <td>blogid</td>\r
- <td>ID of the weblog</td>\r
-</tr><tr>\r
- <td>query</td>\r
- <td>the query that was used in the search</td>\r
-</tr></table>\r
-\r
-<h2>Example</h2>\r
-\r
-<pre><code>No search results found for <b><%query%></b></code></pre>\r
-\r
-</div>\r
-\r
-<div class="page"><a name="templatecommentbody"></a>\r
-<h1>Templates: Comment body</h1>\r
-<p>\r
-This is the part of the template used to display a single comment. In this template-part, <a href="#templatevars-comments" title="Overview of comments-related template variables">comments-related templatevars</a> are available.</p>\r
-\r
-<h2>Example</h2>\r
-<pre><code><h2>Comment by <%userlink%>:</h2>\r
-\r
-<p><%body%></p>\r
-\r
-<div class="metadata">\r
- (from <%host%> on <%date%> at <%time%>)\r
-</div></code></pre>\r
-\r
-<p>Result:</p>\r
-\r
-<div class="example">\r
-<h4 style="margin: 2px;">Comment by <a href="#templatecommentbody">karma</a>:</h4>\r
-<p style="margin: 2px;">Nice!</p>\r
-<div style="margin:2px;font-size:smaller;">(from host.example.org on 2003-03-02 at 13:30)</div>\r
-</div>\r
-\r
-</div>\r
-\r
-<div class="page"><a name="templatepopups"></a>\r
-<h1>Templates: Media & Popups</h1>\r
-<p>\r
-These templates are used to format links to popup image windows and media objects (non-pictures). The available variables for each of the templates are described below\r
-</p>\r
-\r
-<h2>Popup Link Code</h2>\r
-\r
-<table><tr>\r
- <th>Name</th>\r
- <th>Description</th>\r
-</tr><tr>\r
- <td>popuplink</td>\r
- <td>an <a href... link ready to use</td>\r
-</tr><tr>\r
- <td>rawpopuplink</td>\r
- <td>only the url inside href="..."</td>\r
-</tr><tr>\r
- <td>popupcode</td>\r
- <td>javascript code to open window</td>\r
-</tr><tr>\r
- <td>text</td>\r
- <td>the alternate text (link text)</td>\r
-</tr><tr>\r
- <td>width</td>\r
- <td>image width</td>\r
-</tr><tr>\r
- <td>height</td>\r
- <td>image width</td>\r
-</tr><tr>\r
- <td>popuptext</td>\r
- <td>(=same as text)</td>\r
-</tr></table>\r
-\r
-\r
-<h2>Inline Image Code</h2>\r
-\r
-<table><tr>\r
- <th>Name</th>\r
- <th>Description</th>\r
-</tr><tr>\r
- <td>image</td>\r
- <td>an IMG-tag, ready to use</td>\r
-</tr><tr>\r
- <td>link</td>\r
- <td>direct link to the image (URL)</td>\r
-</tr><tr>\r
- <td>text</td>\r
- <td>the alternate text (link text)</td>\r
-</tr><tr>\r
- <td>width</td>\r
- <td>image width</td>\r
-</tr><tr>\r
- <td>height</td>\r
- <td>image width</td>\r
-</tr></table>\r
-\r
-<h2>Media Object Link Code</h2>\r
-\r
-<table><tr>\r
- <th>Name</th>\r
- <th>Description</th>\r
-</tr><tr>\r
- <td>media</td>\r
- <td>an A-tag, ready to use</td>\r
-</tr><tr>\r
- <td>link</td>\r
- <td>direct link to the file (URL)</td>\r
-</tr><tr>\r
- <td>text</td>\r
- <td>the alternate text (link text)</td>\r
-</tr></table>\r
-\r
-</div>\r
-\r
-<div class="page"><a name="templatememberextra"></a>\r
-<h1>Templates: Member Extra</h1>\r
-<p>\r
-This is a template you can use to add an extra indication that a comment-author is a member. It ends up in the <code><%authtext%></code> variable for use in the <a href="#templatecommentbody">comment body</a>\r
-</p>\r
-\r
-<p>Inside this template-part, some <a href="#templatevars-comments" title="Overview of comments-related template variables">comments-related variables</a> are available.</p>\r
-\r
-</div>\r
-\r
-<div class="page"><a name="templatecommentcontinued"></a>\r
-<h1>Templates: Comments Read More</h1>\r
-<p>\r
-This is the format of the link that will be added at the end of <code><%short%></code>, which is a variable for use in the <a href="#templatecommentbody">comment body</a>\r
-</p>\r
-\r
-<p>Inside this template-part, some <a href="#templatevars-comments" title="Overview of comments-related template variables">comments-related variables</a> are available (except for the <code><%short%></code> variable).</p>\r
-\r
-<p>Example:</p>\r
-\r
-<pre>\r
- <a href="<%itemlink%>">[more]</a>\r
-</pre>\r
-\r
-</div>\r
-\r
-<div class="page"><a name="templatecommentwords"></a>\r
-<h1>Templates: commentword</h1>\r
-<p>\r
-Most likely, you'll rather want to write "1 comment" than "1 comment(s)". The "One comment" and "Many comments" template parts can be used for this purpose. They will be used to fill the <code><%commentword%></code> variable that you can use elsewhere.\r
-</p>\r
-\r
-<p>\r
-If there is only 1 comment, <code><%commentword%></code> will be equal to the contents of the "one comment" part. If there are many comments (more than one), <code><%commentword%></code> will be equal to the contents of the "two (or more) comments" part.\r
-</p>\r
-\r
-<p>\r
-Typical values are "comment" and "comments". <strong>No special variables can be used here</strong>.\r
-</p>\r
-</div>\r
-\r
-\r
-\r
-<div class="page"><a name="templateeditlink"></a>\r
-<h1>Templates: Edit Link</h1>\r
-<p>\r
-This template defines how the <a href="#templatevar-edit">edit-templatevar</a> will be marked up. You can use any of the <a href="#templatevars-overview">template variables</a> here.\r
-</p>\r
-\r
-<h2>Example:</h2>\r
-\r
-<pre><code><a href="<%editlink%>"\r
- onclick="<%editpopupcode%>">edit</a></code></pre>\r
-\r
-</div>\r
-\r
-\r
-\r
-\r
-<div class="page"><a name="skinpartindex"></a>\r
-<h1>Skins: Main Index</h1>\r
-<p>\r
-This skinpart is used to show the most recent entries of your weblog. It's usually the home page of your site.\r
-</p>\r
-\r
-<p>\r
-Very basic buildup for a main index:\r
-</p>\r
-\r
-<pre>\r
-<html>\r
- <head>\r
- <title>My Weblog</title>\r
- </head>\r
- <body>\r
-\r
- <h1>My Weblog</h1>\r
- <%blog(mytemplate,20)%>\r
-\r
- </body>\r
-</html>\r
-</pre>\r
-\r
-<p>\r
- This will show the 20 most recent items of the default weblog (unless overridden), using the 'mytemplate' template.\r
-</p>\r
-</div>\r
-\r
-\r
-<div class="page"><a name="skinpartitem"></a>\r
-<h1>Skins: Detail Pages</h1>\r
-<p>\r
-These pages are used to show the full items, all comments that were made and a form to add comments.\r
-</p>\r
-\r
-<p>\r
-Very basic buildup for a detailed item page:\r
-</p>\r
-\r
-<pre>\r
-<html>\r
- <head>\r
- <title>My Weblog :: Item</title>\r
- </head>\r
- <body>\r
-\r
- <h1>Item</h1>\r
- <%item(detailed)%>\r
-\r
- <h1>Comments</h1>\r
- <%comments(detailed)%>\r
-\r
- <h1>Add Comment</h1>\r
- <%commentform%>\r
-\r
- </body>\r
-</html>\r
-</pre>\r
-\r
-<p>\r
- This will show the item and comments using the 'detailed' template, and add a standard commentform.\r
-</p>\r
-\r
-\r
-</div>\r
-\r
-<div class="page"><a name="skinpartarchivelist"></a>\r
-<h1>Skins: Archive List</h1>\r
-<p>\r
-An overview of all the months for which archives are available, and links to those archives\r
-</p>\r
-\r
-<p>\r
-Very basic buildup for an archive list:\r
-</p>\r
-\r
-<pre>\r
-<html>\r
- <head>\r
- <title>My Weblog :: Archives</title>\r
- </head>\r
- <body>\r
-\r
- <h1>Archives</h1>\r
- <%archivelist(default)%>\r
-\r
- </body>\r
-</html>\r
-</pre>\r
-\r
-<p>\r
- This will show the list of all available archive files, using the 'default' template\r
-</p>\r
-\r
-</div>\r
-\r
-<div class="page"><a name="skinpartarchive"></a>\r
-<h1>Skins: Archive</h1>\r
-<p>\r
-An archive for one month. Behaves like a main index, but shows all the items from a certain month.\r
-</p>\r
-\r
-<p>\r
-Very basic buildup for an archive page:\r
-</p>\r
-\r
-<pre>\r
-<html>\r
- <head>\r
- <title>My Weblog :: Archive</title>\r
- </head>\r
- <body>\r
-\r
- <h1>Archive</h1>\r
- <%archive(default)%>\r
-\r
- </body>\r
-</html>\r
-</pre>\r
-\r
-<p>\r
- This will show the requested archive using the 'default' template\r
-</p>\r
-\r
-\r
-</div>\r
-\r
-\r
-<div class="page"><a name="skinpartsearch"></a>\r
-<h1>Skins: Search</h1>\r
-<p>\r
-Used to show search results.\r
-</p>\r
-\r
-<p>\r
-Very basic buildup for a searchresults page:\r
-</p>\r
-\r
-<pre>\r
-<html>\r
- <head>\r
- <title>My Weblog :: Search</title>\r
- </head>\r
- <body>\r
-\r
- <h1>Search</h1>\r
- <%searchform%>\r
-\r
- <h1>Searchresults</h1>\r
- <%searchresults(default)%>\r
-\r
- </body>\r
-</html>\r
-</pre>\r
-\r
-<p>\r
- This will show search results using the 'default' template.\r
-</p>\r
-\r
-</div>\r
-\r
-<div class="page"><a name="skinparterror"></a>\r
-<h1>Skins: Errors</h1>\r
-<p>\r
-Used when there is an error\r
-</p>\r
-\r
-<pre>\r
-<html>\r
- <head>\r
- <title>My Weblog :: Error</title>\r
- </head>\r
- <body>\r
-\r
- <h1>Error!</h1>\r
- <%errormessage%>\r
-\r
- <br /><br />\r
-\r
- <a href="javascript:history.back();">Back</a>\r
-\r
- </body>\r
-</html>\r
-</pre>\r
-\r
-<p>\r
- This will show the error message, plus a link to go back.\r
-</p>\r
-\r
-</div>\r
-\r
-<div class="page"><a name="skinpartmember"></a>\r
-<h1>Skins: Member</h1>\r
-<p>\r
-Used to show member details.\r
-</p>\r
-\r
-<p>\r
-Very basic buildup for a member-detail page:\r
-</p>\r
-\r
-<pre>\r
-<html>\r
- <head>\r
- <title>My Weblog :: Member details</title>\r
- </head>\r
- <body>\r
-\r
- <h1>Info about <%member(name)%></h1>\r
- Website:\r
- <a href="<%member(url)%>"><%member(url)%></a>\r
-\r
- <h1>Send Message</h1>\r
- <%membermailform%>\r
-\r
- </body>\r
-</html>\r
-</pre>\r
-\r
-<p>\r
- This will show the members name, website address and a mailform.\r
-</p>\r
-\r
-</div>\r
-\r
-\r
-<div class="page"><a name="skinpartimagepopup"></a>\r
-<h1>Skins: Image Popup</h1>\r
-<p>\r
-Used when a media file (image) needs to be shown in a popup window. This skin defines the layout that will be used in that case.\r
-</p>\r
-\r
-<p>\r
-Very basic buildup for an imagepopup page:\r
-</p>\r
-\r
-<pre>\r
-<html>\r
-<head>\r
- <title><%imagetext%></title>\r
- <style type="text/css">\r
- img { border: none; }\r
- </style>\r
-</head>\r
-<body>\r
- <a href="javascript:window.close();"><%image%></a>\r
-</body>\r
-</html>\r
-</pre>\r
-\r
-</div>\r
-\r
-\r
-\r
-\r
-\r
-<div class="page"><a name="shortnames"></a>\r
-<h1>Shortnames & Display Names</h1>\r
-<p>\r
-Weblogs, templates and skin should all have a short name next to the full name or description.\r
-</p>\r
-\r
-<p>\r
-A short name consists of <strong>only</strong> the characters a-z and 0-9, and <strong>cannot</strong> contain spaces\r
-</p>\r
-\r
-<p>\r
-Display names are used for members. They can contain a-z, A-Z, 0-9 and spaces, but the spaces cannot be placed at the beginning or end of the name.\r
-</p>\r
-</div>\r
-\r
-\r
-\r
-\r
-\r
-\r
-<div class="page"><a name="templatenew"></a>\r
-<h1>Template: 'New' indication</h1>\r
-<p>\r
-When the <a href="#cookies">'last visit' cookie</a> option is activated, the contents of the 'Indication of new item'-template is copied into the <%new%> variable for items that have been added since the last visit. The <code><%new%></code> variable can e.g. be used in the <a href="#templateitems">item body</a>-template.\r
-</p>\r
-\r
-<p>\r
-When the 'last visit' cookie is disabled, or the item is not 'new', this template part will not be used.\r
-</p>\r
-</div>\r
-\r
-\r
-<div class="page"><a name="strftime"></a>\r
-<h1>Time variables overview</h1>\r
-\r
-<p>The following conversion specifiers are recognized in the format string <small>(taken from the PHP documentation for the strftime function)</small>. More info in the <a href="http://www.opengroup.org/onlinepubs/7908799/xsh/strftime.html" onclick="window.open(this.href);return false;" class="out" title="Open Group specification">Open Group Specification</a></p>\r
-\r
-<ul>\r
- <li><strong>%a</strong> - abbreviated weekday name according to the current locale</li>\r
- <li><strong>%A</strong> - full weekday name according to the current locale</li>\r
- <li><strong>%b</strong> - abbreviated month name according to the current locale</li>\r
- <li><strong>%B</strong> - full month name according to the current locale</li>\r
- <li><strong>%c</strong> - preferred date and time representation for the current locale</li>\r
- <li><strong>%d</strong> - day of the month as a decimal number (range 00 to 31)</li>\r
- <li><strong>%H</strong> - hour as a decimal number using a 24-hour clock (range 00 to 23)</li>\r
- <li><strong>%I</strong> - hour as a decimal number using a 12-hour clock (range 01 to 12)</li>\r
- <li><strong>%j</strong> - day of the year as a decimal number (range 001 to 366)</li>\r
- <li><strong>%m</strong> - month as a decimal number (range 1 to 12)</li>\r
- <li><strong>%M</strong> - minute as a decimal number</li>\r
- <li><strong>%p</strong> - either `am' or `pm' according to the given time value, or the corresponding strings for the current locale</li>\r
- <li><strong>%S</strong> - second as a decimal number</li>\r
- <li><strong>%U</strong> - week number of the current year as a decimal number, starting with the first Sunday as the first day of the first week</li>\r
- <li><strong>%W</strong> - week number of the current year as a decimal number, starting with the first Monday as the first day of the first week</li>\r
- <li><strong>%w</strong> - day of the week as a decimal, Sunday being 0</li>\r
- <li><strong>%x</strong> - preferred date representation for the current locale without the time</li>\r
- <li><strong>%X</strong> - preferred time representation for the current locale without the date</li>\r
- <li><strong>%y</strong> - year as a decimal number without a century (range 00 to 99)</li>\r
- <li><strong>%Y</strong> - year as a decimal number including the century</li>\r
- <li><strong>%Z</strong> - time zone or name or abbreviation</li>\r
- <li><strong>%%</strong> - a literal `%' character</li>\r
-</ul>\r
-\r
-</div>\r
-\r
-<div class="page"><a name="pinguserland"></a>\r
-<h1>Ping Weblogs.com</h1>\r
-<p>\r
-When updating your weblog, you can choose to send an update notification (ping) to <a href="http://www.weblogs.com/" onclick="window.open(this.href);return false;" class="out">weblogs.com</a>. This website provides a list of recently updated weblogs to everyone who requests it. Lots of websites are using this data, so you might receive some extra hits when enabling the ping.\r
-</p>\r
-<p class="note"><strong>Note:</strong> For this feature to work correctly, you need to fill out both the weblog URL and the weblog name in the blogsettings.\r
-</p>\r
-\r
-</div>\r
-\r
-<div class="page"><a name="blogsearchable"></a>\r
-\r
-<h1>Always include in search</h1>\r
-\r
-<p>When the 'include in search' option is selected, the weblog will <strong>always</strong> be included in searches, even if the search is done on another weblog.</p>\r
-\r
-<p>As an example, suppose you have two blogs called 'lifelog' and 'linkdump', with the 'include in search' enabled for 'linkdump'. Now, a search query on 'lifelog' will also search through 'linkdump', while a search query on 'linkdump' will only search entries in 'linkdump'</p>\r
-\r
-\r
-</div>\r
-\r
-\r
-<div class="page"><a name="convertbreaks"></a>\r
-<h1>Convert Linebreaks</h1>\r
-<p>\r
-By default, Nucleus converts linebreaks in your items to <code><br /></code> tags, so a linebreak will also show up in your (X)HTML output\r
-</p>\r
-<p>\r
-Advanced users, or users striving for the semantic web (<tt>br</tt> tags don't add any information, they're just used for markup), might find this feature annoying, and turn this feature off.\r
-</p>\r
-</div>\r
-\r
-\r
-<div class="page"><a name="media"></a>\r
-<h1>Media</h1>\r
-<p>\r
-Nucleus allows you to upload media files (images, video, sound, ...) to your website\r
-</p>\r
-<p>\r
-Some settings are needed to do this:\r
-</p>\r
-<ul>\r
- <li><strong>Media dir</strong>: location on the server where the media files will be saved (local filesystem)</li>\r
- <li><strong>Media URL</strong>: location of the media files</li>\r
- <li><strong>Allow upload</strong>: It's possible to disable file upload</li>\r
- <li><strong>Allowed filetypes for upload</strong>: a bunch of extensions uploaded files can have (seperated by commas, case insensitive)</li>\r
- <li><strong>Max. upload file size</strong>: Puts a limit on the size of uploaded files</li>\r
- <li><strong>Prefix Media Files</strong>: When this option is turned on, uploaded file will be prefixed with the current date. Uploading a file named 'bunny.jpg' on April 8, 2003 will then result in a file named 20030408-bunny.jpg. The reason why you might want to do this, is when you're uploading tons of files, and don't want problems with duplicate names.</li>\r
-</ul>\r
-\r
-<p>\r
-Each member has his own private collection of media files. Next to that, subdirectories that are under the media dir are seen as global collections (shared between members).\r
-</p>\r
-\r
-<p>Uploading is only possible when a member is on the team of at least one of the blogs, to prevent abuse.</p>\r
-</div>\r
-\r
-\r
-<div class="page"><a name="protectmemnames"></a>\r
-<h1>Protect Member Names</h1>\r
-<p>When this option is enabled, non-logged in members cannot add comments using the same name as registered members. The reason to do this would be to avoid guest impersonating members.</p>\r
-</div>\r
-\r
-\r
-<div class="page"><a name="pluginurl"></a>\r
-<h1>Plugin URL</h1>\r
-<p>This setting is the base URL for plugin admin areas. Usually it will look like the following</p>\r
-<pre>http://hostname.com/nucleus/plugins/</pre>\r
-</div>\r
-\r
-<div class="page"><a name="skinsurl"></a>\r
-<h1>Skins URL</h1>\r
-<p>This setting is the base URL for the Nucleus skins directory. Usually it will look like the following</p>\r
-<pre>http://hostname.com/skins/</pre>\r
-</div>\r
-\r
-<div class="page"><a name="actionurl"></a>\r
-<h1>Action URL</h1>\r
-<p>This setting is the absolute URL of the <code>action.php</code> script that comes with Nucleus. Usually it will look like the following</p>\r
-<pre>http://hostname.com/actions.php</pre>\r
-</div>\r
-\r
-\r
-\r
-<div class="page"><a name="additem"></a>\r
-<h1>Adding items</h1>\r
-<p>When adding items to a weblog, there are four kinds of template variables that you can use in the body text, title or extended part:</p>\r
-<ul>\r
- <li><a href="#templatevar-popup"><%popup(...)%></a> to insert a popup image</li>\r
- <li><a href="#templatevar-popup"><%image(...)%></a> to insert an inline image</li>\r
- <li><a href="#templatevar-popup"><%media(...)%></a> to insert a media object</li>\r
-</ul>\r
-<p>Usually, these tags are inserted by the 'insert media' button in the JavaScript toolbar</p>\r
-\r
-\r
-</div>\r
-\r
-\r
-\r
-\r
-<div class="page">\r
-<a name="skinvar-referer"></a>\r
-<h1>Skinvar: referer</h1>\r
-<p>Inserts the refering URL (can be empty)</p>\r
-<h2>Arguments</h2>\r
-<p>None</p>\r
-<h2>Skintypes</h2>\r
-<p>all</p>\r
-<h2>Examples</h2>\r
-<pre>\r
-<a href="<%referer%>">back</a>\r
-</pre>\r
-</div>\r
-\r
-\r
-<div class="page">\r
-<a name="skinvar-itemid"></a>\r
-<h1>Skinvar: itemid</h1>\r
-<p>Inserts the ID of the currently selected item</p>\r
-<h2>Arguments</h2>\r
-<p>None</p>\r
-<h2>Skintypes</h2>\r
-<p>item</p>\r
-<h2>Examples</h2>\r
-<pre>\r
-<%itemid%>\r
-</pre>\r
-</div>\r
-\r
-\r
-<div class="page">\r
-<a name="skinvar-itemlink"></a>\r
-\r
-<h1>Skinvar: itemlink</h1>\r
-\r
-<p>Adds a permanent link for the item.</p>\r
-\r
-<h2>Arguments</h2>\r
-\r
-<p>\r
- Optional\r
- <ul>\r
- <li><strong><em>linktext</em></strong>: when present, a full <code><a href...</code> tag will be outputted, rather than a raw link</li>\r
- </ul>\r
-</p>\r
-<h2>Skintypes</h2>\r
-\r
-<p>item</p>\r
-\r
-<h2>Examples</h2>\r
-\r
-<pre>\r
-<%itemlink%>\r
-</pre>\r
-</div>\r
-\r
-<div class="page">\r
-<a name="skinvar-itemtitle"></a>\r
-<h1>Skinvar: itemtitle</h1>\r
-<p>Inserts the title of the item, with HTML-stripped off and entities encoded</p>\r
-<h2>Arguments</h2>\r
-<p>None</p>\r
-<h2>Skintypes</h2>\r
-<p>item</p>\r
-<h2>Examples</h2>\r
-<pre>\r
-<%itemtitle%>\r
-</pre>\r
-</div>\r
-\r
-\r
-<div class="page">\r
-<a name="skinvar-archivedate"></a>\r
-<h1>Skinvar: archivedate</h1>\r
-<p>Inserts a formatted date for an archive date. Using no parameters, this will either insert '15 august 2002' or 'august 2002' if the archive is for august 2002</p>\r
-<h2>Arguments</h2>\r
-<ul>\r
- <li>Optional\r
- <table><tr>\r
- <th>Name</th>\r
- <th>Value</th>\r
- </tr><tr>\r
- <td>Locale</td>\r
- <td><a href="#templatelocale">Locale</a> in which the date must be formatted</td>\r
- </tr><tr>\r
- <td>Format</td>\r
- <td>Date format (<a href="#strftime">strftime variables</a>)</td>\r
- </tr></table>\r
- </li>\r
-</ul>\r
-<h2>Skintypes</h2>\r
-<p>archive</p>\r
-<h2>Examples</h2>\r
-<pre>\r
-Archive for <%archivedate%>\r
-Archive for <%archivedate(dutch)%>\r
-Archive for <%archivedate(en,%B %Y)%>\r
-</pre>\r
-</div>\r
-\r
-\r
-\r
-<div class="page">\r
-<a name="skinvar-blog"></a>\r
-<h1>Skinvar: blog</h1>\r
-\r
-<p>\r
-Inserts the most recently added items of the currently active blog (usually the default one) into the skin.\r
-</p>\r
-\r
-<h2>Arguments</h2>\r
-<p>\r
- Required:\r
- <ul>\r
- <li><strong>template</strong>: name of the template to use</li>\r
- </ul>\r
- Optional:\r
- <ul>\r
- <li><strong><em>amount</em></strong>: the amount of items to show (default = 10). Can also contain an offset telling Nucleus to start only from the given item. e.g. <code>10(5)</code> shows 10 items starting from item 5</li>\r
- <li><strong><em>category</em></strong>: name of the category to show</li>\r
- </ul>\r
-</p>\r
-\r
-<h2>Skintypes</h2>\r
-\r
-<p>\r
-index, item, archive, archivelist, search\r
-</p>\r
-\r
-<h2>Examples</h2>\r
-\r
-<pre>\r
-<%blog(default,15)%>\r
-<%blog(default,5(15))%>\r
-<%blog(mytemplate)%>\r
-<%blog(mytemplate,5,mycategory)%>\r
-</pre>\r
-\r
-</div>\r
-\r
-\r
-\r
-\r
-<div class="page">\r
-<a name="skinvar-otherblog"></a>\r
-<h1>Skinvar: otherblog</h1>\r
-\r
-<p>\r
-Inserts the most recently added items of a given blog into the skin.\r
-</p>\r
-\r
-<h2>Arguments</h2>\r
-<p>\r
- Required:\r
- <ul>\r
- <li><strong>blogname</strong>: name of the blog to show</li>\r
- <li><strong>template</strong>: name of the template to use</li>\r
- </ul>\r
- Optional:\r
- <ul>\r
- <li><strong><em>amount</em></strong>: the amount of items to show (default = 10). Can also contain an offset telling Nucleus to start only from the given item. e.g. <code>10(5)</code> shows 10 items starting from item 5</li>\r
- <li><strong><em>category</em></strong>: name of the category to show</li>\r
- </ul>\r
-</p>\r
-\r
-<h2>Skintypes</h2>\r
-\r
-<p>\r
-all\r
-</p>\r
-\r
-<h2>Examples</h2>\r
-\r
-<pre>\r
-<%otherblog(myblog,default,15)%>\r
-<%otherblog(yourblog,mytemplate)%>\r
-<%otherblog(yourblog,mytemplate,15,mycategory)%>\r
-<%otherblog(yourblog,mytemplate,5(15),mycategory)%>\r
-</pre>\r
-\r
-</div>\r
-\r
-\r
-\r
-\r
-\r
-\r
-\r
-\r
-\r
-<div class="page">\r
-<a name="skinvar-item"></a>\r
-<h1>Skinvar: item</h1>\r
-\r
-<p>\r
-Shows the currently selected item (without comments) using a given template\r
-</p>\r
-\r
-<h2>Arguments</h2>\r
-<ul>\r
- <li><strong>template</strong>: name of the template to use</li>\r
-</ul>\r
-\r
-<h2>Skintypes</h2>\r
-\r
-<p>\r
-item\r
-</p>\r
-\r
-<h2>Examples</h2>\r
-\r
-<pre>\r
-<%item(mytemplate)%>\r
-</pre>\r
-\r
-</div>\r
-\r
-\r
-\r
-\r
-\r
-\r
-\r
-\r
-\r
-<div class="page">\r
-<a name="skinvar-comments"></a>\r
-<h1>Skinvar: comments</h1>\r
-\r
-<p>\r
-Shows the comments for the currently selected item using a given template.\r
-</p>\r
-\r
-<h2>Arguments</h2>\r
-<ul>\r
- <li><strong>template</strong>: name of the template to use</li>\r
-</ul>\r
-\r
-<h2>Skintypes</h2>\r
-\r
-<p>\r
-item\r
-</p>\r
-\r
-<h2>Examples</h2>\r
-\r
-<pre>\r
-<%comments(mytemplate)%>\r
-</pre>\r
-\r
-</div>\r
-\r
-\r
-\r
-\r
-\r
-\r
-\r
-<div class="page">\r
-<a name="skinvar-archive"></a>\r
-<h1>Skinvar: archive</h1>\r
-\r
-<p>\r
-Shows the archive for the selected month and the selected blog (usually the default one), using a given template\r
-</p>\r
-\r
-<h2>Arguments</h2>\r
-<p>\r
- Required\r
- <ul>\r
- <li><strong>template</strong>: name of the template to use</li>\r
- </ul>\r
- Optional\r
- <ul>\r
- <li><strong><em>category</em></strong>: name of the category to show</li>\r
- </ul>\r
-</p>\r
-\r
-<h2>Skintypes</h2>\r
-\r
-<p>\r
-archive\r
-</p>\r
-\r
-<h2>Examples</h2>\r
-\r
-<pre>\r
-<%archive(mytemplate)%>\r
-<%archive(mytemplate,mycategory)%>\r
-</pre>\r
-\r
-</div>\r
-\r
-\r
-\r
-\r
-<div class="page">\r
-<a name="skinvar-otherarchive"></a>\r
-<h1>Skinvar: otherarchive</h1>\r
-\r
-<p>\r
-Shows the archive for the selected month, using the given blog and template\r
-</p>\r
-\r
-<h2>Arguments</h2>\r
-<p>\r
- Required\r
- <ul>\r
- <li><strong>blogname</strong>: name of the blog to use</li>\r
- <li><strong>template</strong>: name of the template to use</li>\r
- </ul>\r
- Optional\r
- <ul>\r
- <li><strong><em>category</em></strong>: name of the category to show</li>\r
- </ul>\r
-</p>\r
-\r
-<h2>Skintypes</h2>\r
-\r
-<p>\r
-archive\r
-</p>\r
-\r
-<h2>Examples</h2>\r
-\r
-<pre>\r
-<%otherarchive(myblog,mytemplate)%>\r
-<%otherarchive(myblog,mytemplate,mycategory)%>\r
-</pre>\r
-\r
-</div>\r
-\r
-\r
-\r
-\r
-\r
-\r
-\r
-<div class="page">\r
-<a name="skinvar-archivelist"></a>\r
-<h1>Skinvar: archivelist</h1>\r
-\r
-<p>\r
-Shows the list of available archives for the currently selected blog (usually the default one), using a given template\r
-</p>\r
-\r
-<h2>Arguments</h2>\r
-<p>\r
- Required\r
- <ul>\r
- <li><strong>template</strong>: name of the template to use</li>\r
- </ul>\r
- Optional\r
- <ul>\r
- <li><strong><em>category</em></strong>: name of the category to show</li>\r
- <li><strong><em>limit</em></strong>: limits the amount of links shown (e.g. if you only want to show links to the past 3 months)</li>\r
- </ul>\r
-</p>\r
-\r
-<h2>Skintypes</h2>\r
-\r
-<p>\r
-index, archive, archivelist, search, item\r
-</p>\r
-</div>\r
-\r
-<div class="page">\r
-<a name="skinvar-archivedaylist"></a>\r
-<h1>Skinvar: archivedaylist</h1>\r
-\r
-<p>\r
-The same as the <a href="#skinvar-archivelist">archivelist</a> skinvar, but shows an entry for each <em>day</em> instead of for each <em>month</em>\r
-</p>\r
-\r
-<h2>Arguments</h2>\r
-<p>\r
- Required\r
- <ul>\r
- <li><strong>template</strong>: name of the template to use</li>\r
- </ul>\r
- Optional\r
- <ul>\r
- <li><strong><em>category</em></strong> name of the category to show</li>\r
- <li><strong><em>limit</em></strong>: limits the amount of links shown (e.g. if you only want to show links to the past 3 months)</li>\r
- </ul>\r
-</p>\r
-\r
-<h2>Skintypes</h2>\r
-\r
-<p>\r
-index, archive, archivelist, search, item\r
-</p>\r
-\r
-\r
-<h2>Examples</h2>\r
-\r
-<pre>\r
-<%archivedaylist(mytemplate)%>\r
-<%archivedaylist(mytemplate,mycategory)%>\r
-</pre>\r
-\r
-</div>\r
-\r
-\r
-<div class="page">\r
-<a name="skinvar-otherarchivedaylist"></a>\r
-<h1>Skinvar: otherarchivedaylist</h1>\r
-\r
-<p>\r
-The same as the <a href="#skinvar-otherarchivelist">otherarchivelist</a> skinvar, but shows an entry for each <em>day</em> instead of for each <em>month</em>\r
-\r
-</p>\r
-\r
-<h2>Arguments</h2>\r
-<p>\r
- Required\r
- <ul>\r
- <li><strong>blogname</strong>: name of the blog</li>\r
- <li><strong>template</strong>: name of the template to use</li>\r
- </ul>\r
- Optional\r
- <ul>\r
- <li><strong><em>category</em></strong>: name of the category to show</li>\r
- </ul>\r
-</p>\r
-\r
-<h2>Skintypes</h2>\r
-\r
-<p>\r
-all\r
-</p>\r
-\r
-<h2>Examples</h2>\r
-\r
-<pre>\r
-<%otherarchivedaylist(yourblog,mytemplate)%>\r
-<%otherarchivedaylist(yourblog,mytemplate,mycategory)%>\r
-</pre>\r
-\r
-</div>\r
-\r
-\r
-\r
-<div class="page">\r
-<a name="skinvar-otherarchivelist"></a>\r
-<h1>Skinvar: otherarchivelist</h1>\r
-\r
-<p>\r
-Shows the list of available archives for a given blog, using a given template\r
-</p>\r
-\r
-<h2>Arguments</h2>\r
-<p>\r
- Required\r
- <ul>\r
- <li><strong>blogname</strong>: name of the blog</li>\r
- <li><strong>template</strong>: name of the template to use</li>\r
- </ul>\r
- Optional\r
- <ul>\r
- <li><strong><em>category</em></strong>: name of the category to show</li>\r
- </ul>\r
-</p>\r
-\r
-<h2>Skintypes</h2>\r
-\r
-<p>\r
-all\r
-</p>\r
-\r
-<h2>Examples</h2>\r
-\r
-<pre>\r
-<%otherarchivelist(yourblog,mytemplate)%>\r
-<%otherarchivelist(yourblog,mytemplate,mycategory)%>\r
-</pre>\r
-\r
-</div>\r
-\r
-\r
-\r
-<div class="page">\r
-<a name="skinvar-categorylist"></a>\r
-<h1>Skinvar: categorylist</h1>\r
-\r
-<p>\r
-Inserts a list of categories for a blog (defaults to the currently selected blog), using a given template\r
-</p>\r
-\r
-<h2>Arguments</h2>\r
-<p>\r
- Required\r
- <ul>\r
- <li><strong>template</strong>: name of the template to use</li>\r
- </ul>\r
- Optional\r
- <ul>\r
- <li><strong><em>blogname</em></strong>: short name of the blog to use</li>\r
- </ul>\r
-</p>\r
-\r
-<h2>Skintypes</h2>\r
-\r
-<p>\r
-index, archive, archivelist, search, item\r
-</p>\r
-\r
-<h2>Examples</h2>\r
-\r
-<pre>\r
-<%categorylist(mytemplate)%>\r
-<%categorylist(mytemplate,myweblog)%>\r
-</pre>\r
-\r
-</div>\r
-\r
-\r
-\r
-<div class="page">\r
-<a name="skinvar-category"></a>\r
-<h1>Skinvar: category</h1>\r
-\r
-<p>\r
-Inserts some information about the currently selected category. When no category is selected, does nothing.\r
-</p>\r
-\r
-<h2>Arguments</h2>\r
-<p>\r
- Optional\r
- <ul>\r
- <li><strong><em>type</em></strong>: What information to include. Can be <b>name</b> (default), <b>desc</b> or <b>id</b></li>\r
- </ul>\r
-</p>\r
-\r
-<h2>Skintypes</h2>\r
-\r
-<p>\r
-all\r
-</p>\r
-\r
-<h2>Examples</h2>\r
-\r
-<pre>\r
-<%category%>\r
-<%category(id)%>\r
-<%category(desc)%>\r
-<%category(name)%>\r
-</pre>\r
-\r
-</div>\r
-\r
-\r
-<div class="page">\r
-<a name="skinvar-ifcat"></a>\r
-<h1>Skinvar: ifcat</h1>\r
-\r
-<p class="deprecated">Deprecated as of Nucleus v2.0. Use <a href="#skinvar-if"><%if(category)%></a> instead.</p>\r
-\r
-<h2>Arguments</h2>\r
-<p>\r
- None\r
- <ul>\r
- <li><em>text</em>: Text to show</li>\r
- </ul>\r
-</p>\r
-\r
-<h2>Skintypes</h2>\r
-\r
-<p>\r
-all\r
-</p>\r
-\r
-<h2>Examples</h2>\r
-\r
-<pre>\r
-<%ifcat(Current Category: )%><%category%>\r
-</pre>\r
-\r
-</div>\r
-\r
-\r
-\r
-\r
-<div class="page">\r
-<a name="skinvar-searchresults"></a>\r
-<h1>Skinvar: searchresults</h1>\r
-\r
-<p>\r
-Shows the searchresult for the current query\r
-</p>\r
-\r
-<h2>Arguments</h2>\r
-<p>\r
- Required:\r
- <ul>\r
- <li><strong>template</strong>: name of the template to use</li>\r
- </ul>\r
- Optional:\r
- <ul>\r
- <li><strong><em>maxresults</em></strong>: maximum amount of results to show</li>\r
- </ul>\r
-</p>\r
-\r
-<h2>Skintypes</h2>\r
-\r
-<p>\r
-search\r
-</p>\r
-\r
-<h2>Examples</h2>\r
-\r
-<pre>\r
-<%searchresults(mytemplate)%>\r
-</pre>\r
-\r
-</div>\r
-\r
-\r
-\r
-\r
-<div class="page">\r
-<a name="skinvar-othersearchresults"></a>\r
-<h1>Skinvar: othersearchresults</h1>\r
-\r
-<p>\r
-Shows the searchresult in a give blog for the current query, using the given template\r
-</p>\r
-\r
-<h2>Arguments</h2>\r
-<p>\r
- Required:\r
- <ul>\r
- <li><strong>blogname</strong>: name of the blog to use</li>\r
- <li><strong>template</strong>: name of the template to use</li>\r
- </ul>\r
- Optional:\r
- <ul>\r
- <li><strong><em>maxresults</em></strong>: maximum amount of results to show</li>\r
- </ul>\r
-</p>\r
-\r
-<h2>Skintypes</h2>\r
-\r
-<p>\r
-search\r
-</p>\r
-\r
-<h2>Examples</h2>\r
-\r
-<pre>\r
-<%othersearchresults(myblog,mytemplate)%>\r
-</pre>\r
-\r
-</div>\r
-\r
-\r
-\r
-\r
-\r
-\r
-\r
-<div class="page">\r
-<a name="skinvar-query"></a>\r
-<h1>Skinvar: query</h1>\r
-\r
-<p>\r
-Inserts the current search query.\r
-</p>\r
-\r
-<h2>Arguments</h2>\r
-<p>\r
-None\r
-</p>\r
-\r
-<h2>Skintypes</h2>\r
-\r
-<p>\r
-search\r
-</p>\r
-\r
-<h2>Examples</h2>\r
-\r
-<pre>\r
-<%query%>\r
-</pre>\r
-\r
-</div>\r
-\r
-\r
-\r
-\r
-\r
-\r
-\r
-\r
-<div class="page">\r
-<a name="skinvar-version"></a>\r
-<h1>Skinvar: version</h1>\r
-\r
-<p>Inserts the current Nucleus version.</p>\r
-\r
-<h2>Arguments</h2>\r
-\r
-<p>\r
-None\r
-</p>\r
-\r
-<h2>Skintypes</h2>\r
-\r
-<p>\r
-all\r
-</p>\r
-\r
-<h2>Examples</h2>\r
-\r
-<pre>\r
-<%version%>\r
-</pre>\r
-\r
-</div>\r
-\r
-\r
-\r
-\r
-\r
-\r
-\r
-\r
-<div class="page">\r
-<a name="skinvar-previtem"></a>\r
-<h1>Skinvar: previtem</h1>\r
-\r
-<p>\r
-Inserts the ID of the previous item in the blog\r
-</p>\r
-\r
-<h2>Arguments</h2>\r
-<p>None</p>\r
-\r
-<h2>Skintypes</h2>\r
-\r
-<p>\r
-item\r
-</p>\r
-\r
-<h2>Examples</h2>\r
-\r
-<pre>\r
-<%previtem%>\r
-</pre>\r
-\r
-</div>\r
-\r
-\r
-\r
-\r
-\r
-\r
-<div class="page">\r
-<a name="skinvar-nextitem"></a>\r
-<h1>Skinvar: nextitem</h1>\r
-\r
-<p>\r
-Inserts the ID of the next item in the blog\r
-</p>\r
-\r
-<h2>Arguments</h2>\r
-<p>None</p>\r
-\r
-<h2>Skintypes</h2>\r
-\r
-<p>\r
-item\r
-</p>\r
-\r
-<h2>Examples</h2>\r
-\r
-<pre>\r
-<%nextitem%>\r
-</pre>\r
-\r
-</div>\r
-\r
-\r
-<div class="page">\r
-<a name="skinvar-nextitemtitle"></a>\r
-<h1>Skinvar: nextitemtitle</h1>\r
-\r
-<p>\r
-Inserts the title of the next item in the blog\r
-</p>\r
-\r
-<h2>Arguments</h2>\r
-<p>None</p>\r
-\r
-<h2>Skintypes</h2>\r
-\r
-<p>\r
-item\r
-</p>\r
-\r
-<h2>Examples</h2>\r
-\r
-<pre>\r
-<%nextitemtitle%>\r
-</pre>\r
-\r
-</div>\r
-\r
-\r
-<div class="page">\r
-<a name="skinvar-previtemtitle"></a>\r
-<h1>Skinvar: previtemtitle</h1>\r
-\r
-<p>\r
-Inserts the title of the previous item in the blog\r
-</p>\r
-\r
-<h2>Arguments</h2>\r
-<p>None</p>\r
-\r
-<h2>Skintypes</h2>\r
-\r
-<p>\r
-item\r
-</p>\r
-\r
-<h2>Examples</h2>\r
-\r
-<pre>\r
-<%previtemtitle%>\r
-</pre>\r
-\r
-</div>\r
-\r
-\r
-\r
-\r
-<div class="page">\r
-<a name="skinvar-prevarchive"></a>\r
-<h1>Skinvar: prevarchive</h1>\r
-\r
-<p>\r
-Inserts the <code>archive</code> attribute that corresponds to the archive of either 1 day or 1 month back. This value can be used inside URLs to select an archive.\r
-</p>\r
-\r
-<ul>\r
- <li>If the shown archive is for one specific day, the value has the form <code>YYYY-MM-DD</code></li>\r
- <li>If the shown archive is for a full month, the value has the form <code>YYYY-MM</code></li>\r
-</ul>\r
-\r
-<h2>Arguments</h2>\r
-<p>None</p>\r
-\r
-<h2>Skintypes</h2>\r
-\r
-<p>\r
-archive\r
-</p>\r
-\r
-<h2>Examples</h2>\r
-\r
-<pre><code><a href="index.php?archive=<%prevarchive%>>....</code></pre>\r
-\r
-</div>\r
-\r
-\r
-\r
-\r
-\r
-\r
-<div class="page">\r
-<a name="skinvar-nextarchive"></a>\r
-<h1>Skinvar: nextarchive</h1>\r
-\r
-<p>\r
-Inserts the <code>archive</code> attribute that corresponds to the archive of either 1 day or 1 month further in time. This value can be used inside URLs to select an archive.\r
-</p>\r
-\r
-<ul>\r
- <li>If the shown archive is for one specific day, the value has the form <code>YYYY-MM-DD</code></li>\r
- <li>If the shown archive is for a full month, the value has the form <code>YYYY-MM</code></li>\r
-</ul>\r
-\r
-<h2>Arguments</h2>\r
-<p>None</p>\r
-\r
-<h2>Skintypes</h2>\r
-\r
-<p>\r
-archive\r
-</p>\r
-\r
-<h2>Examples</h2>\r
-\r
-<pre><code><a href="index.php?archive=<%nextarchive%>>....</code></pre>\r
-\r
-</div>\r
-\r
-\r
-<div class="page">\r
-<a name="skinvar-archivetype"></a>\r
-<h1>Skinvar: archivetype</h1>\r
-\r
-<p>\r
-Either <tt>day</tt> or <tt>month</tt>, indicating which type of archive is currently being shown\r
-</p>\r
-\r
-<h2>Arguments</h2>\r
-<p>None</p>\r
-\r
-<h2>Skintypes</h2>\r
-\r
-<p>\r
-archive\r
-</p>\r
-\r
-</div>\r
-\r
-\r
-\r
-\r
-\r
-<div class="page">\r
-<a name="skinvar-todaylink"></a>\r
-<h1>Skinvar: todaylink</h1>\r
-\r
-<p>\r
-Inserts a link to the main page of the weblog. Takes into account the currently selected blog and category.\r
-</p>\r
-\r
-<h2>Arguments</h2>\r
-<p>\r
- Optional\r
- <ul>\r
- <li><strong><em>linktext</em></strong>: when present, a full <code><a href...</code> tag will be outputted, rather than a raw link</li>\r
- </ul>\r
-</p>\r
-\r
-\r
-<h2>Skintypes</h2>\r
-\r
-<p>\r
-all\r
-</p>\r
-\r
-<h2>Examples</h2>\r
-\r
-<pre>\r
-<%todaylink%>\r
-</pre>\r
-\r
-</div>\r
-\r
-\r
-\r
-\r
-\r
-\r
-\r
-<div class="page">\r
-<a name="skinvar-archivelink"></a>\r
-<h1>Skinvar: archivelink</h1>\r
-\r
-<p>\r
-Inserts a link to the archive for the currently selected blog and category (or the default blog when no blog selected)\r
-</p>\r
-\r
-<h2>Arguments</h2>\r
-\r
-<p>\r
- Optional\r
- <ul>\r
- <li><strong><em>linktext</em></strong>: when present, a full <code><a href...</code> tag will be outputted, rather than a raw link</li>\r
- </ul>\r
-</p>\r
-\r
-\r
-<h2>Skintypes</h2>\r
-\r
-<p>\r
-all\r
-</p>\r
-\r
-<h2>Examples</h2>\r
-\r
-<pre>\r
-<%archivelink%>\r
-</pre>\r
-\r
-</div>\r
-\r
-\r
-\r
-\r
-\r
-\r
-<div class="page">\r
-<a name="skinvar-nextlink"></a>\r
-<h1>Skinvar: nextlink</h1>\r
-\r
-<p>\r
-Inserts a link to the next item (on item pages) or to the next archive (on archive pages)\r
-</p>\r
-\r
-<h2>Arguments</h2>\r
-<p>\r
- Optional\r
- <ul>\r
- <li><strong><em>linktext</em></strong>: when present, a full <code><a href...</code> tag will be outputted, rather than a raw link</li>\r
- <li><strong><em>amount</em></strong>: for search and index skins: the amount of items to go forward/backward</li>\r
- </ul>\r
-</p>\r
-\r
-\r
-<h2>Skintypes</h2>\r
-\r
-<p>\r
-item, archive, search, index\r
-</p>\r
-\r
-<h2>Examples</h2>\r
-\r
-<pre>\r
-<%nextlink%>\r
-</pre>\r
-\r
-</div>\r
-\r
-\r
-\r
-\r
-\r
-\r
-\r
-\r
-<div class="page">\r
-<a name="skinvar-prevlink"></a>\r
-<h1>Skinvar: prevlink</h1>\r
-\r
-<p>\r
-Inserts a link to the previous item (on item pages) or to the previous archive (on archive pages). For search and index pages\r
-</p>\r
-\r
-<h2>Arguments</h2>\r
-<p>\r
- Optional\r
- <ul>\r
- <li><strong><em>linktext</em></strong>: when present, a full <code><a href...</code> tag will be outputted, rather than a raw link</li>\r
- <li><strong><em>amount</em></strong>: for search and index skins: the amount of items to go forward/backward</li>\r
- </ul>\r
-</p>\r
-\r
-<h2>Skintypes</h2>\r
-\r
-<p>\r
-item, archive, search, index\r
-</p>\r
-\r
-<h2>Examples</h2>\r
-\r
-<pre>\r
-<%prevlink%>\r
-</pre>\r
-\r
-</div>\r
-\r
-\r
-\r
-\r
-\r
-\r
-\r
-\r
-<div class="page">\r
-<a name="skinvar-errormessage"></a>\r
-<h1>Skinvar: errormessage</h1>\r
-\r
-<p>\r
-Inserts the message corresponding to the error that occurred\r
-</p>\r
-\r
-<h2>Arguments</h2>\r
-<p>None</p>\r
-\r
-<h2>Skintypes</h2>\r
-\r
-<p>\r
-error\r
-</p>\r
-\r
-<h2>Examples</h2>\r
-\r
-<pre>\r
-<%errormessage%>\r
-</pre>\r
-\r
-</div>\r
-\r
-\r
-\r
-\r
-\r
-\r
-\r
-\r
-<div class="page">\r
-<a name="skinvar-imagetext"></a>\r
-<h1>Skinvar: imagetext</h1>\r
-\r
-<p class="deprecated">This skinvar is deprecated since Nucleus v2.0. You should use <a href="#skinvar-image"><code><%image(caption)%></code></a> instead</p>\r
-\r
-<p>\r
-Inserts the caption text for a popup image\r
-</p>\r
-\r
-<h2>Arguments</h2>\r
-<p>None</p>\r
-\r
-<h2>Skintypes</h2>\r
-\r
-<p>\r
-imagepopup\r
-</p>\r
-\r
-<h2>Examples</h2>\r
-\r
-<pre>\r
-<%imagetext%>\r
-</pre>\r
-\r
-</div>\r
-\r
-\r
-\r
-<div class="page">\r
-<a name="skinvar-image"></a>\r
-<h1>Skinvar: image</h1>\r
-\r
-<p>\r
-Inserts the selected image (for popup images)\r
-</p>\r
-\r
-<h2>Arguments</h2>\r
-\r
-<p>Optional</p>\r
-<ul>\r
- <li>\r
- <em>type</em>\r
- <table><tr>\r
- <td><strong>imgtag</strong> (default)</td>\r
- <td>Full XHTML <code><img ... /></code> tag</td>\r
- </tr><tr>\r
- <td><strong>url</strong></td>\r
- <td>Image file URL</td>\r
- </tr><tr>\r
- <td><strong>width</strong></td>\r
- <td>image width</td>\r
- </tr><tr>\r
- <td><strong>height</strong></td>\r
- <td>image height</td>\r
- </tr><tr>\r
- <td><strong>caption</strong></td>\r
- <td>image caption (text to go with image)</td>\r
- </tr></table>\r
- </li>\r
-</ul>\r
-\r
-<h2>Skintypes</h2>\r
-\r
-<p>\r
-imagepopup\r
-</p>\r
-\r
-<h2>Examples</h2>\r
-\r
-<pre>\r
-<%image%>\r
-</pre>\r
-\r
-</div>\r
-\r
-\r
-<div class="page">\r
-<a name="skinvar-vars"></a>\r
-<h1>Skinvar: vars</h1>\r
-\r
-<p class="deprecated">This skinvar is deprecated since Nucleus v2.0. It's a small pain to insert this HTML yourself using the <a href="#skinvar-itemid">itemid skinvar</a></p>\r
-\r
-<p>\r
-Inserts a hidden form-input field with the itemid.\r
-</p>\r
-\r
-<code><input type="hidden" name="itemid" value="<strong>1234</strong>" /></code>\r
-\r
-<h2>Arguments</h2>\r
-<p>None</p>\r
-\r
-<h2>Skintypes</h2>\r
-\r
-<p>\r
-item\r
-</p>\r
-\r
-\r
-</div>\r
-\r
-\r
-\r
-\r
-\r
-\r
-<div class="page">\r
-<a name="skinvar-sitevar"></a>\r
-<h1>Skinvar: sitevar</h1>\r
-\r
-<p>\r
-Includes a site variable\r
-</p>\r
-\r
-<h2>Arguments</h2>\r
-<ul>\r
- <li><strong>type</strong>: name of the variable to show:\r
- <ul>\r
- <li><em>url</em>: URL of the site</li>\r
- <li><em>name</em>: Name of the site</li>\r
- <li><em>admin</em>: E-mail address of the administrator</li>\r
- </ul>\r
- </li>\r
-</ul>\r
-\r
-<h2>Skintypes</h2>\r
-\r
-<p>\r
-all\r
-</p>\r
-\r
-<h2>Examples</h2>\r
-\r
-<pre>\r
-<%sitevar(name)%>\r
-<%sitevar(url)%>\r
-<a href="mailto:<%sitevar(email)%>">Admin</a>\r
-</pre>\r
-\r
-</div>\r
-\r
-\r
-\r
-\r
-\r
-\r
-<div class="page">\r
-<a name="skinvar-blogsetting"></a>\r
-<h1>Skinvar: blogsetting</h1>\r
-\r
-<p>\r
-Inserts a setting specific to the currently selected blog (usually the default one)\r
-</p>\r
-\r
-<h2>Arguments</h2>\r
-<ul>\r
- <li><strong>type</strong>: which setting to add\r
- <ul>\r
- <li><em>id</em>: ID of the blog</li>\r
- <li><em>url</em>: URL of the blog</li>\r
- <li><em>name</em>: Name of the blog (long name)</li>\r
- <li><em>desc</em>: Description of the blog</li>\r
- <li><em>short</em>: Short name of the blog</li>\r
- </ul>\r
- </li>\r
-</ul>\r
-\r
-<h2>Skintypes</h2>\r
-\r
-<p>\r
-index, archive, archivelist, search, item, member\r
-</p>\r
-\r
-<h2>Examples</h2>\r
-\r
-<pre>\r
-<%blogsetting(name)%>\r
-<%blogsetting(id)%>\r
-<%blogsetting(desc)%>\r
-<a href="<%blogsetting(url)%>">...</a>\r
-</pre>\r
-\r
-</div>\r
-\r
-\r
-\r
-\r
-\r
-\r
-<div class="page">\r
-<a name="skinvar-member"></a>\r
-<h1>Skinvar: member</h1>\r
-\r
-<p>\r
-Inserts some info about on the currently logged in member. On member detail pages, extra options are available to show the same information for the requested member.\r
-</p>\r
-\r
-<p>When the visitor is not logged in, the <em>your...</em> parameters will insert nothing</p>\r
-\r
-<h2>Arguments</h2>\r
-<ul>\r
- <li><strong>type</strong>: which information to show.\r
- <p>Information on the logged in member:</p>\r
- <ul>\r
- <li><em>yourname</em>: nickname of the member (the one used to login)</li>\r
- <li><em>yourrealname</em>: full name of the member</li>\r
- <li><em>yournotes</em>: extra information a member can set for him/herself</li>\r
- <li><em>yoururl</em>: URL of the members website</li>\r
- <li><em>youremail</em>: email address </li>\r
- <li><em>yourid</em>: ID</li>\r
- </ul>\r
- <p>Information on the requested member (only available on member detail pages):</p>\r
- <ul>\r
- <li><em>name</em>: nickname of the member (the one used to login)</li>\r
- <li><em>realname</em>: full name of the member</li>\r
- <li><em>notes</em>: extra information a member can set for him/herself</li>\r
- <li><em>url</em>: URL of the members website</li>\r
- <li><em>email</em>: email address of the member</li>\r
- <li><em>id</em>: ID</li>\r
- </ul>\r
- </li>\r
-</ul>\r
-\r
-<h2>Skintypes</h2>\r
-\r
-<p>\r
-all\r
-</p>\r
-\r
-<h2>Examples</h2>\r
-\r
-<pre><code>\r
-<%if(loggedin)%>\r
-you are <%member(yourrealname)%>\r
-<%endif%>\r
-</code></pre>\r
-\r
-</div>\r
-\r
-\r
-\r
-\r
-\r
-\r
-<div class="page">\r
-<a name="skinvar-preview"></a>\r
-<h1>Skinvar: preview</h1>\r
-\r
-<p>\r
-Inserts an item-preview into the page, using a given template (to be used in conjunction with <a href="#skinvar-additemform">additemform</a>)\r
-</p>\r
-\r
-<h2>Arguments</h2>\r
-<ul>\r
- <li><strong>template</strong>: name of the template to be used</li>\r
-</ul>\r
-\r
-<h2>Skintypes</h2>\r
-\r
-<p>\r
-index\r
-</p>\r
-\r
-<h2>Examples</h2>\r
-\r
-<pre>\r
-<%preview(mytemplate)%>\r
-</pre>\r
-\r
-</div>\r
-\r
-\r
-\r
-<div class="page">\r
-<a name="skinvar-adminurl"></a>\r
-<h1>Skinvar: adminurl</h1>\r
-\r
-<p>Inserts the full URL to the Admin Area</p>\r
-\r
-<h2>Arguments</h2>\r
-<p>None</p>\r
-\r
-<h2>Skintypes</h2>\r
-\r
-<p>\r
-all\r
-</p>\r
-\r
-<h2>Examples</h2>\r
-\r
-<pre>\r
-<a href="<%adminurl%>">Admin Area</a>\r
-</pre>\r
-\r
-</div>\r
-\r
-\r
-\r
-\r
-<div class="page">\r
-<a name="skinvar-additemform"></a>\r
-<h1>Skinvar: additemform</h1>\r
-\r
-<p>\r
-Shows an add-item form for the currently selected blog (usually the default one). Mostly used in conjunction with <a href="#skinvar-preview">preview</a>\r
-</p>\r
-\r
-<h2>Arguments</h2>\r
-<p>None</p>\r
-\r
-<h2>Skintypes</h2>\r
-\r
-<p>\r
-index\r
-</p>\r
-\r
-<h2>Examples</h2>\r
-\r
-<pre>\r
-<%additemform%>\r
-</pre>\r
-\r
-</div>\r
-\r
-\r
-\r
-\r
-\r
-\r
-<div class="page">\r
-<a name="skinvar-include"></a>\r
-<h1>Skin/Templatevar: include</h1>\r
-\r
-<p>\r
-Includes a textfile into the output. The contents of the file is not parsed in any way, so you cannot use skin/templatevars or use PHP code (see <a href="#skinvar-parsedinclude">parsedinclude</a> and <a href="#skinvar-phpinclude">phpinclude</a> if you want parsed includes)\r
-</p>\r
-\r
-<h2>Arguments</h2>\r
-<ul>\r
- <li><strong>filename</strong>: the name of the file to be included (either relative to the position of index.php, or absolute). Note that an URL can also be used here.</li>\r
-</ul>\r
-\r
-<h2>Notes</h2>\r
-<ul>\r
- <li>This tag is affected by the <a href="#parser-properties">parser settings <code>IncludeMode</code> and <code>IncludePrefix</code></a></li>\r
-</ul>\r
-\r
-<h2>Skintypes</h2>\r
-\r
-<p>\r
-all\r
-</p>\r
-\r
-<h2>Examples</h2>\r
-\r
-<pre>\r
-<%include(filename.txt)%>\r
-<%include(/home/user/myself/filename.txt)%>\r
-<%include(http://mydomain.com/filename.html)%>\r
-</pre>\r
-\r
-</div>\r
-\r
-\r
-\r
-\r
-\r
-\r
-\r
-<div class="page">\r
-<a name="skinvar-phpinclude"></a>\r
-<h1>Skin/Templatevar: phpinclude</h1>\r
-\r
-<p>\r
-Includes a php-file into the output. The contents of the file is parsed by the PHP parser, so be careful. Nucleus skin/templatevars are <b>not</b> parsed! (see <a href="#skinvar-parsedinclude">parsedinclude</a> and <a href="#skinvar-include">include</a> for other include options).\r
-</p>\r
-\r
-<h2>Arguments</h2>\r
-<ul>\r
- <li><strong>filename</strong>: the name of the file to be included (either relative to the position of index.php, or absolute)</li>\r
-</ul>\r
-\r
-<h2>Notes</h2>\r
-<ul>\r
- <li>This tag is affected by the <a href="#parser-properties">parser settings <code>IncludeMode</code> and <code>IncludePrefix</code></a></li>\r
- <li>Your file will be included using the standard php <code>include()</code> command. This command will be called from <em>inside</em> a class method, so <strong>you'll need to declare which global variables you want to access</strong> yourself. Most of the <a href="#skinvar-phpinclude-vars">standard variables</a> are automatically declared global by Nucleus itself.</li>\r
-</ul>\r
-\r
-<h2>Skintypes</h2>\r
-\r
-<p>\r
-all\r
-</p>\r
-\r
-<h2>Examples</h2>\r
-\r
-<pre><code><%phpinclude(filename.php)%>\r
-<%phpinclude(/home/user/myself/filename.php)%></code></pre>\r
-\r
-</div>\r
-\r
-\r
-\r
-<div class="page">\r
-<a name="skinvar-phpinclude-vars"></a>\r
-<h1>Skin/Templatevar: phpinclude : vars</h1>\r
-\r
-<p>\r
-The following global variables are accessible from within files included by the <a href="#skinvar-phpinclude">phpinclude</a> skin/templatevar:\r
-</p>\r
-\r
-<p>\r
-$GATEWAY_INTERFACE, $SERVER_NAME, $SERVER_SOFTWARE\r
-<br />$SERVER_PROTOCOL, $REQUEST_METHOD, $QUERY_STRING\r
-<br />$DOCUMENT_ROOT, $HTTP_ACCEPT, $HTTP_ACCEPT_CHARSET\r
-<br />$HTTP_ACCEPT_ENCODING, $HTTP_ACCEPT_LANGUAGE\r
-<br />$HTTP_CONNECTION, $HTTP_HOST, $HTTP_REFERER\r
-<br />$HTTP_USER_AGENT, $REMOTE_ADDR, $REMOTE_PORT\r
-<br />$SCRIPT_FILENAME, $SERVER_ADMIN, $SERVER_PORT\r
-<br />$SERVER_SIGNATURE, $PATH_TRANSLATED, $SCRIPT_NAME\r
-<br />$REQUEST_URI, $argv, $argc, $PHP_SELF\r
-<br />$HTTP_COOKIE_VARS, $HTTP_GET_VARS, $HTTP_POST_VARS\r
-<br />$HTTP_POST_FILES, $HTTP_ENV_VARS, $HTTP_SERVER_VARS\r
-<br />$HTTP_SESSION_VARS, $PATH_INFO, $HTTPS\r
-<br />$HTTP_RAW_POST_DATA, $HTTP_X_FORWARDED_FOR\r
-</p>\r
-\r
-<p>\r
-For others variables, you'll need to add '<tt>global $varname;</tt>' explicitly in your code\r
-</p>\r
-\r
-</div>\r
-\r
-\r
-\r
-<div class="page">\r
-<a name="skinvar-parsedinclude"></a>\r
-<h1>Skin/Templatevar: parsedinclude</h1>\r
-\r
-<p>\r
-Includes a file into the output. The contents of the file is parsed by the Nucleus skin/template parser, so you can use skin/templatevars. (see <a href="#skinvar-phpinclude">phpinclude</a> and <a href="#skinvar-include">include</a> for other include options)\r
-</p>\r
-\r
-<h2>Arguments</h2>\r
-<ul>\r
- <li><strong>filename</strong>: the name of the file to be included (either relative to the position of index.php, or absolute)</li>\r
-</ul>\r
-\r
-<h2>Notes</h2>\r
-<ul>\r
- <li>This tag is affected by the <a href="#parser-properties">parser settings <code>IncludeMode</code> and <code>IncludePrefix</code></a></li>\r
- <li>From inside the included file, you can call <code><%parsedinclude(filename)%></code> again. To avoid endless loops, the maximum depth level you can go is 3.</li>\r
-</ul>\r
-\r
-\r
-<h2>Skintypes</h2>\r
-\r
-<p>\r
-all\r
-</p>\r
-\r
-<h2>Examples</h2>\r
-\r
-<pre>\r
-<%parsedinclude(filename.txt)%>\r
-<%parsedinclude(/home/user/myself/filename.txt)%>\r
-</pre>\r
-\r
-</div>\r
-\r
-\r
-\r
-\r
-\r
-\r
-<div class="page">\r
-<a name="skinvar-plugin"></a>\r
-<h1>Skin/Templatevar: plugin</h1>\r
-\r
-<p>\r
-Calls a plugin\r
-</p>\r
-\r
-<h2>Arguments</h2>\r
-<ul>\r
- <li>\r
- <p>Required</p>\r
- <table><tr>\r
- <th>Name</th>\r
- <th>Contents</th>\r
- </tr><tr>\r
- <td>PlugName</td>\r
- <td>Name of the plugin that should be called. <strong>This name is case sensitive!</strong></td>\r
- </tr></table>\r
- </li>\r
- <li><p>Extra parameters can be added, depending on the plugin</p></li>\r
-</ul>\r
-\r
-<h2>Notes</h2>\r
-<ul>\r
- <li>When a plugin name does not conflict with existing variables, it can be called directly using <code><%PluginName(parameters)%></code></li>\r
-</ul>\r
-\r
-<h2>Skintypes</h2>\r
-\r
-<p>\r
-all\r
-</p>\r
-\r
-<h2>Examples</h2>\r
-\r
-<pre>\r
-<%plugin(Calendar)%>\r
-<%plugin(LastComments,myweblog)%>\r
-<%LastComments(myweblog)%>\r
-</pre>\r
-\r
-</div>\r
-\r
-\r
-\r
-\r
-<div class="page">\r
-<a name="skinvar-loginform"></a>\r
-<h1>Skinvar: loginform</h1>\r
-\r
-<p>Adds a loginform, or shows a "You are karma (Log out)" message</p>\r
-\r
-<h2>Arguments</h2>\r
-<p>\r
- None\r
-</p>\r
-\r
-<h2>Skintypes</h2>\r
-\r
-<p>all</p>\r
-\r
-<h2>Examples</h2>\r
-\r
-<pre><code><%loginform%></code></pre>\r
-\r
-</div>\r
-\r
-\r
-\r
-\r
-<div class="page">\r
-<a name="skinvar-commentform"></a>\r
-<h1>Skinvar: commentform</h1>\r
-\r
-<p>\r
-Adds a commentform to an item page.\r
-</p>\r
-\r
-<h2>Arguments</h2>\r
-<p>\r
- Optional:\r
- <ul>\r
- <li><strong><em>destinationurl</em></strong>: sets the URL to where Nucleus needs to redirect after adding the comment (by default, Nucleus redirects to the item detail page for the item)</li>\r
- </ul>\r
-</p>\r
-\r
-<h2>Skintypes</h2>\r
-\r
-<p>\r
-item\r
-</p>\r
-\r
-<h2>Examples</h2>\r
-\r
-<pre>\r
-<%commentform%>\r
-<%commentform(http://host/thanks.html)%>\r
-</pre>\r
-\r
-</div>\r
-\r
-\r
-\r
-<div class="page">\r
-<a name="skinvar-set"></a>\r
-<h1>Skin/Templatevar: set</h1>\r
-\r
-<p>\r
-Sets a <a href="#parser-properties" title="A list of available parser properties">parser property</a>.\r
-</p>\r
-\r
-<h2>Arguments</h2>\r
-<p>\r
- <ul>\r
- <li><strong>property</strong>: name of the property</li>\r
- <li><strong>value</strong>: value of the property</li>\r
- </ul>\r
-</p>\r
-\r
-<h2>Skintypes</h2>\r
-\r
-<p>\r
-all\r
-</p>\r
-\r
-<h2>Examples</h2>\r
-\r
-<pre>\r
-<%set(IncludeMode,skindir)%>\r
-<%set(IncludePrefix,somedir/)%>\r
-</pre>\r
-\r
-</div>\r
-\r
-\r
-<div class="page">\r
-<a name="skinvar-skinfile"></a>\r
-<h1>Skin/Templatevar: skinfile</h1>\r
-\r
-<p>Used by imported skins to put a link relative to the skins-URL. Use it in conjunction with the <tt>IncludePrefix</tt> <a href="#parser-properties">parser property</a> to get the best results</p>\r
-\r
-<h2>Arguments</h2>\r
-<p>\r
- <ul>\r
- <li><strong>filename</strong>: filename of which you want the correct URL</li>\r
- </ul>\r
-</p>\r
-\r
-<h2>Skintypes</h2>\r
-\r
-<p>\r
-all\r
-</p>\r
-\r
-<h2>Examples</h2>\r
-\r
-<pre>\r
-<%skinfile(mystyle.css)%>\r
-</pre>\r
-\r
-</div>\r
-\r
-\r
-\r
-<div class="page">\r
-<a name="skinvar-skinname"></a>\r
-<h1>Skin/Templatevar: skinname</h1>\r
-\r
-<p>Inserts the name of the skin that's currently being used.</p>\r
-\r
-<h2>Arguments</h2>\r
-<p>\r
-None\r
-</p>\r
-\r
-<h2>Skintypes</h2>\r
-\r
-<p>\r
-all\r
-</p>\r
-\r
-<h2>Examples</h2>\r
-\r
-<pre>\r
-<%skinname%>\r
-</pre>\r
-\r
-</div>\r
-\r
-\r
-\r
-<div class="page">\r
-<a name="skinvar-if"></a>\r
-<a name="skinvar-else"></a>\r
-<a name="skinvar-endif"></a>\r
-<h1>Skinvars: if/else/endif</h1>\r
-\r
-<p>Inserts a content block only when certain conditions are fullfilled</p>\r
-\r
-<h2>Arguments</h2>\r
-<p>Only the <code>if</code> skinvar has options</p>\r
-\r
-\r
-<ul>\r
- <li><strong>type</strong>: type of condition</li>\r
- <li><em>name</em>: name of option (optional)</li>\r
- <li><em>value</em>: value to be checked (optional)</li>\r
-</ul>\r
-\r
-<h2>Condition types</h2>\r
-\r
-<ul>\r
- <li><strong>category</strong>: condition is fullfilled when a category is selected\r
- <ul>\r
- <li><strong>category</strong>: checks if any category is selected</li>\r
- <li><strong>category,catname,<em>CategoryName</em></strong>: checks if the current category is <em>CategoryName</em></li>\r
- <li><strong>category,catid,<em>CategoryId</em></strong>: checks if the current category is <em>CategoryId</em></li>\r
- </ul>\r
- </li>\r
- <li><strong>blogsetting</strong>: checks if the value <em>name</em> blogsetting equals <em>value</em> (the name is the column name from the nucleus_blog sql table)</li>\r
- <li><strong>loggedin</strong>: condition is fullfilled if visiting member is currently logged in</li>\r
- <li><strong>onteam</strong>: condition is fullfilled if visiting member is currently logged in & member of the blog team of the current blog (or the blog given in the <em>name</em> parameter)</li>\r
- <li><strong>nextitem</strong>: true if there is a more recent item available for the current weblog (item skintype)</li>\r
- <li><strong>nextitem</strong>: true if there is an older item available for the current weblog (item skintype)</li>\r
- <li><strong>skintype</strong>: checks if the current skin type is equal to <em>value</em> (index, search, item, archive, archivelist, ...)</li>\r
- <li><strong>hasplugin</strong>: checks if the a plugin is installed, or if a plugin option has been set to a specific value\r
- <ul>\r
- <li><strong>hasplugin,<em>PluginName</em></strong>: checks if plugin is available</li>\r
- <li><strong>hasplugin,<em>PluginName</em>,<em>OptionName</em></strong>: checks if a plugin option is not set to 'no'</li>\r
- <li><strong>hasplugin,<em>PluginName</em>,<em>OptionName=value</em></strong>: checks if a plugin option is set to a specific value</li>\r
- </ul>\r
- </li>\r
-</ul>\r
-\r
-<h2>Skintypes</h2>\r
-\r
-<p>\r
-all\r
-</p>\r
-\r
-<h2>Examples</h2>\r
-\r
-<pre>\r
-<%if(loggedin)%>\r
-Welcome back!\r
-<%else%>\r
-Welcom guest!\r
-<%endif%>\r
-</pre>\r
-\r
-<pre>\r
-<%if(category,catname,Off Topic)%>\r
-Welcome to the 'Off Topic' category.\r
-<%endif%>\r
-</pre>\r
-\r
-<h2>Notes</h2>\r
-\r
-<p>If you want something to be displayed only if a condition is not fullfilled, you can use a construct like this:</p>\r
-\r
-<pre>\r
-<%if(skintype,error)%><%else%>\r
-<%blogsetting(name)%>\r
-<%endif%>\r
-</pre>\r
-\r
-</div>\r
-\r
-\r
-\r
-\r
-\r
-\r
-<div class="page">\r
-<a name="skinvar-membermailform"></a>\r
-<h1>Skinvar: membermailform</h1>\r
-\r
-<p>\r
-Shows a form through which a logged-in member can send a message to the member which details are being shown (on member detail pages)\r
-</p>\r
-\r
-<h2>Arguments</h2>\r
-<p>\r
- Optional:\r
- <ul>\r
- <li><strong><em>rows</em></strong>: Amount of rows in the box (default = 10)</li>\r
- <li><strong><em>cols</em></strong>: Amount of columns in the box (default = 40)</li>\r
- <li><strong><em>destination url</em></strong>: URL to where Nucleus needs to redirection after sending the message</li>\r
- </ul>\r
-</p>\r
-\r
-<h2>Skintypes</h2>\r
-\r
-<p>\r
-member\r
-</p>\r
-\r
-<h2>Examples</h2>\r
-\r
-<pre>\r
-<%membermailform%>\r
-</pre>\r
-\r
-</div>\r
-\r
-\r
-\r
-\r
-\r
-\r
-<div class="page">\r
-<a name="skinvar-searchform"></a>\r
-<h1>Skinvar: searchform</h1>\r
-\r
-<p>\r
-Shows a search form for the current blog.\r
-</p>\r
-\r
-<h2>Arguments</h2>\r
-<p>\r
- Optional:\r
- <ul>\r
- <li><strong><em>blogname</em></strong>: The name of the blog for which you want a search form (short blog name)</li>\r
- </ul>\r
-</p>\r
-\r
-<h2>Skintypes</h2>\r
-\r
-<p>\r
-index, archive, archivelist, search, item\r
-</p>\r
-\r
-<h2>Examples</h2>\r
-\r
-<pre>\r
-<%searchform%>\r
-<%searchform(otherweblog)%>\r
-</pre>\r
-\r
-</div>\r
-\r
-\r
-\r
-\r
-\r
-\r
-<div class="page">\r
-<a name="skinvar-nucleusbutton"></a>\r
-<h1>Skinvar: nucleusbutton</h1>\r
-\r
-<p>Inserts a nucleus button, with link to the <a href="http://nucleuscms.org/" class="out" onclick="window.open(this.href);return false;" title="Nucleus website (opens in new window)">Nucleus website</a>.</p>\r
-\r
-<h2>Arguments</h2>\r
-<p>\r
- Optional:\r
- <ul>\r
- <li><strong><em>imgurl</em></strong>: URL of the image (if you don't want the default)</li>\r
- <li><strong><em>imgwidth</em></strong>: width of the image (in pixels)</li>\r
- <li><strong><em>imgheight</em></strong>: height of the image (in pixels)</li>\r
- </ul>\r
-</p>\r
-\r
-<h2>Notes</h2>\r
-<ul>\r
- <li>This tag is affected by the <a href="#parser-properties">parser settings <code>IncludeMode</code> and <code>IncludePrefix</code></a></li>\r
-</ul>\r
-\r
-<h2>Skintypes</h2>\r
-\r
-<p>\r
-all\r
-</p>\r
-\r
-<h2>Examples</h2>\r
-\r
-<pre>\r
-<%nucleusbutton%>\r
-<%nucleusbutton(nucleus/nucleus.gif,46,43)%>\r
-</pre>\r
-\r
-</div>\r
-\r
-\r
-\r
-\r
-<div class="page">\r
-<a name="skinvar-self"></a>\r
-<h1>Skinvar: self</h1>\r
-\r
-<p>\r
-Inserts the filename of the page currently being displayed (index.php or whatever you changed it to)\r
-</p>\r
-\r
-<h2>Arguments</h2>\r
-<p>None</p>\r
-\r
-<h2>Skintypes</h2>\r
-\r
-<p>\r
-all\r
-</p>\r
-\r
-<h2>Examples</h2>\r
-\r
-<pre>\r
-<%self%>\r
-</pre>\r
-\r
-</div>\r
-\r
-\r
-\r
-\r
-\r
-\r
-\r
-\r
-<div class="page">\r
-<a name="templatevars-overview"></a>\r
-<h1>Template variables: Overview</h1>\r
-\r
-<h2>What?</h2>\r
-\r
-<p>Template variables largely work in exact the same way as skin variables, with the only difference that they are being used inside templates. The variables are called using <code><%<i>varname</i>%></code>, and include some text depending on the variable function. Some variables also have extra optional parameters.</p>\r
-\r
-<h2>Available variables</h2>\r
-\r
-<p>\r
-These template variables be used in the following template-parts: <tt>item header, item body, item footer, date header, date footer, morelink, editlink</tt> (The variables <tt>image</tt>, <tt>popup</tt> and <tt>media</tt> can also be used inside weblog items.)\r
-</p>\r
-\r
-<ul>\r
- <li><a href="#templatevars-basic">Basic variables...</a> (title, body, ...)</li>\r
- <li><a href="#templatevars-advanced">Advanced variables...</a> (include, plugin, ...)</li>\r
-</ul>\r
-\r
-<p>Comments-related template-parts (<tt>comments header, comments body, comments footer, one comment, two comments, comments read more, no comments, too much comments</tt>) have a different set of available variables:</p>\r
-\r
-<ul>\r
- <li><a href="#templatevars-comments">Comments-related variables...</a></li>\r
-</ul>\r
-\r
-\r
-</div>\r
-\r
-\r
-\r
-<div class="page">\r
-<a name="templatevars-basic"></a>\r
-<h1>Template variables: Basic variables</h1>\r
-\r
-<p>All these variables concern the item that's currently being parsed.</p>\r
-\r
-<table><tr>\r
- <th>Name</th>\r
- <th>Description</th>\r
-</tr><tr>\r
- <td>title</td>\r
- <td>item title</td>\r
-</tr><tr>\r
- <td>body</td>\r
- <td>body text</td>\r
-</tr><tr>\r
- <td>more</td>\r
- <td>extended text</td>\r
-</tr><tr>\r
- <td>category</td>\r
- <td>name of the category</td>\r
-</tr><tr>\r
- <td>categorylink</td>\r
- <td>raw link to the category</td>\r
-</tr><tr>\r
- <td><a href="#templatevar-karma">karma</a></td>\r
- <td>karma score</td>\r
-</tr><tr>\r
- <td>authorlink</td>\r
- <td>raw link to the author</td>\r
-</tr><tr>\r
- <td>itemlink</td>\r
- <td>raw permanent link for the item</td>\r
-</tr><tr>\r
- <td><a href="#templatevar-author">author</a></td>\r
- <td>name of the author</td>\r
-</tr><tr>\r
- <td><a href="#templatevar-smartbody">smartbody</a></td>\r
- <td>either the body text or the extended text</td>\r
-</tr><tr>\r
- <td><a href="#templatevar-morelink">morelink</a></td>\r
- <td>'read more'-link</td>\r
-</tr><tr>\r
- <td><a href="#templatevar-date">date</a></td>\r
- <td>Formatted date</td>\r
-</tr><tr>\r
- <td><a href="#templatevar-time">time</a></td>\r
- <td>Formatted time</td>\r
-</tr><tr>\r
- <td>daylink</td>\r
- <td>raw link to the daily archive</td>\r
-</tr><tr>\r
- <td><a href="#templatevar-comments">comments</a></td>\r
- <td>comments block or commentcount</td>\r
-</tr><tr>\r
- <td>itemid</td>\r
- <td>ID of the item</td>\r
-</tr><tr>\r
- <td>blogurl</td>\r
- <td>URL of the blog</td>\r
-</tr></table>\r
-\r
-<p><a href="#templatevars-overview">Template variables overview...</a></p>\r
-\r
-\r
-</div>\r
-\r
-\r
-\r
-<div class="page">\r
-<a name="templatevars-advanced"></a>\r
-<h1>Template variables: Advanced variables</h1>\r
-\r
-\r
-<table><tr>\r
- <th>Name</th>\r
- <th>Description</th>\r
-</tr><tr>\r
- <td>authorid</td>\r
- <td>ID of the current items author</td>\r
-</tr><tr>\r
- <td>blogid</td>\r
- <td>ID of the blog</td>\r
-</tr><tr>\r
- <td>catid</td>\r
- <td>ID of the category for the current item</td>\r
-</tr><tr>\r
- <td>query</td>\r
- <td>search query (if there is one)</td>\r
-</tr><tr>\r
- <td><a href="#templatevar-syndicate_title">syndicate_title</a></td>\r
- <td>Syndicated title</td>\r
-</tr><tr>\r
- <td><a href="#templatevar-syndicate_description">syndicate_description</a></td>\r
- <td>Syndicated body text</td>\r
-</tr><tr>\r
- <td>karmaposlink</td>\r
- <td>raw vote link</td>\r
-</tr><tr>\r
- <td>karmaneglink</td>\r
- <td>raw vote link</td>\r
-</tr><tr>\r
- <td>new</td>\r
- <td>'New Item!'-text</td>\r
-</tr><tr>\r
- <td><a href="#skinvar-include">include</a></td>\r
- <td>includes a file, whithout parsing</td>\r
-</tr><tr>\r
- <td><a href="#skinvar-parsedinclude">parsedinclude</a></td>\r
- <td>includes a file, parsing it</td>\r
-</tr><tr>\r
- <td><a href="#skinvar-phpinclude">phpinclude</a></td>\r
- <td>includes a file, parsing by PHP</td>\r
-</tr><tr>\r
- <td><a href="#skinvar-plugin">plugin</a></td>\r
- <td>executes a plugin</td>\r
-</tr><tr>\r
- <td><a href="#templatevar-edit">edit</a></td>\r
- <td>inserts an 'edit this item' link</td>\r
-</tr><tr>\r
- <td><a href="#templatevar-editlink">editlink</a></td>\r
- <td>raw 'edit item' link (links to bookmarklet)</td>\r
-</tr><tr>\r
- <td><a href="#templatevar-editpopupcode">editpopupcode</a></td>\r
- <td>javascript code to open a popup window for editlink</td>\r
-</tr><tr>\r
- <td><a href="#skinvar-skinfile">skinfile</a></td>\r
- <td>includes the correct URL for a file belonging to an imported skin</td>\r
-</tr><tr>\r
- <td><a href="#skinvar-set">set</a></td>\r
- <td>sets a parser property</td>\r
-</tr><tr>\r
- <td><a href="#templatevar-image">image</a></td>\r
- <td>inline image from media library</td>\r
-</tr><tr>\r
- <td><a href="#templatevar-popup">popup</a></td>\r
- <td>popup image from media dir</td>\r
-</tr><tr>\r
- <td><a href="#templatevar-media">media</a></td>\r
- <td>other media object from media dir</td>\r
-</tr><tr>\r
- <td>relevance</td>\r
- <td>Includes the 'search hit relevance' in templates that display search results</td>\r
-</tr></table>\r
-\r
-<p><a href="#templatevars-overview">Template variables overview...</a></p>\r
-\r
-</div>\r
-\r
-\r
-\r
-\r
-<div class="page">\r
-<a name="templatevars-comments"></a>\r
-<h1>Template variables: Comments</h1>\r
-\r
-\r
-<table><tr>\r
- <th>Name</th>\r
- <th>Description</th>\r
-</tr><tr>\r
- <td>body</td>\r
- <td>comment body</td>\r
-</tr><tr>\r
- <td>user</td>\r
- <td>user name</td>\r
-</tr><tr>\r
- <td>userid</td>\r
- <td>users URL or e-mail address</td>\r
-</tr><tr>\r
- <td>userlink</td>\r
- <td>a smart link to either the e-mail or URL for non members, or the member detail page for members. Note: this link already includes the <a href="..."> and </a> tags ! (when no valid URL or e-mail is available, only the name of the member will be shown)</td>\r
-</tr><tr>\r
- <td>userlinkraw</td>\r
- <td>same as above, but without the <a href.., empty when no valid URL or e-mail available</td>\r
-</tr><tr>\r
- <td>memberid</td>\r
- <td>ID of the member (0 for non-members)</td>\r
-</tr><tr>\r
- <td>commentcount</td>\r
- <td>total amount of comments for the item</td>\r
-</tr><tr>\r
- <td><a href="#templatecommentwords" title="commentword()">commentword</a></td>\r
- <td>1 'comment', 2 'comments'</td>\r
-</tr><tr>\r
- <td><a href="#templatevar-date" title="date([format])">date</a></td>\r
- <td>date on which comment was added</td>\r
-</tr><tr>\r
- <td><a href="#templatevar-time" title="time([format])">time</a></td>\r
- <td>time at which comment was added</td>\r
-</tr><tr>\r
- <td>host</td>\r
- <td>host from where comment was added</td>\r
-</tr><tr>\r
- <td>ip</td>\r
- <td>IP-address from where comment was added</td>\r
-</tr><tr>\r
- <td>commentid</td>\r
- <td>ID of the current comment</td>\r
-</tr><tr>\r
- <td>itemid</td>\r
- <td>ID of the current item</td>\r
-</tr><tr>\r
- <td>itemlink</td>\r
- <td>link to the detailed item page</td>\r
-</tr><tr>\r
- <td><a href="#templateitemtitle" title="itemtitle([maxlength])">itemtitle</a></td>\r
- <td>Title of the current item</td>\r
-</tr><tr>\r
- <td>blogid</td>\r
- <td>ID of the weblog</td>\r
-</tr><tr>\r
- <td><a href="#templatememberextra" title="authtext()">authtext</a></td>\r
- <td>the extra text</a> for members, empty for non members</td>\r
-</tr><tr>\r
- <td>short</td>\r
- <td>a cut off version of the body, which truncates after the first line break. <a href="#templatecommentcontinued">A link is added</a> at the end according to the template</td>\r
-</tr><tr>\r
- <td>timestamp</td>\r
- <td>time at which comment was added</td>\r
-</tr><tr>\r
- <td><a href="#skinvar-include" title="include(filename)">include</a></td>\r
- <td>includes a file, whithout parsing</td>\r
-</tr><tr>\r
- <td><a href="#skinvar-parsedinclude" title="parsedinclude(filename)">parsedinclude</a></td>\r
- <td>includes a file, parsing it</td>\r
-</tr><tr>\r
- <td><a href="#skinvar-phpinclude" title="phpinclude(filename)">phpinclude</a></td>\r
- <td>includes a file, parsing by PHP</td>\r
-</tr><tr>\r
- <td><a href="#skinvar-plugin" title="plugin(name,[options...])">plugin</a></td>\r
- <td>executes a plugin</td>\r
-</tr><tr>\r
- <td><a href="#skinvar-skinfile" title="skinfile(filename)">skinfile</a></td>\r
- <td>includes the correct URL for a file belonging to an imported skin</td>\r
-</tr><tr>\r
- <td><a href="#skinvar-set" title="set(property,value)">set</a></td>\r
- <td>sets a parser property</td>\r
-</tr></table>\r
-\r
-\r
-\r
-<p><a href="#templatevars-overview">Template variables overview...</a></p>\r
-\r
-</div>\r
-\r
-\r
-\r
-<div class="page">\r
-<a name="templatevar-karma"></a>\r
-<h1>Templatevar: karma</h1>\r
-\r
-<p>Inserts karma votes data. Karma votes are a method to vote the 'karma' of an item. With a single click, the visitor can vote either positive or negative. The total of all these votes gives an idea of how much an item is liked by the visitors</p>\r
-\r
-<h2>Arguments</h2>\r
-\r
-\r
-<ul>Optional:\r
- <ul>\r
- <li><strong><em>what</em></strong>: Choose a type of information to be displayed:\r
- <ul>\r
- <li><strong>totalscore</strong>: the total karma vote score (=amount of positive votes minus the amount of negative votes) <em>(default)</em></li>\r
- <li><strong>pos</strong>: total number of positive votes</li>\r
- <li><strong>neg</strong>: total number of negative votes</li>\r
- <li><strong>votes</strong>: total number of votes</li>\r
- <li><strong>posp</strong>: percentage of votes that is positive</li>\r
- <li><strong>negp</strong>: percentage of votes that is negative</li>\r
- </ul>\r
- </li>\r
- </ul>\r
-</ul>\r
-\r
-<h2>Examples</h2>\r
-<pre><code><%karma(posp)%> out of <%karma(votes)%> were positive</code></pre>\r
-\r
-\r
-</div>\r
-\r
-\r
-\r
-<div class="page">\r
-<a name="templateitemtitle"></a>\r
-<h1>Templatevar: templateitemtitle</h1>\r
-\r
-<p>On comments-releated templateparts, inserts the title of the associated item.</p>\r
-\r
-<h2>Arguments</h2>\r
-\r
-<ul>Optional:\r
- <ul>\r
- <li><strong><em>maxlength</em></strong>: When provided, makes the itemtitle behave like the <a href="#templatevar-syndicate_title">syndicate_title templatevar</a>.\r
- </li>\r
- </ul>\r
-</ul>\r
-\r
-</div>\r
-\r
-\r
-\r
-\r
-\r
-\r
-<div class="page">\r
-<a name="templatevar-author"></a>\r
-<h1>Templatevar: author</h1>\r
-\r
-<p>Inserts the name of the author</p>\r
-\r
-<h2>Arguments</h2>\r
-<ul>Optional:\r
- <ul>\r
- <li><strong><em>what</em></strong>: Choose a type of information to be displayed:\r
- <ul>\r
- <li><strong>name</strong>: display name <em>(default)</em></li>\r
- <li><strong>realname</strong>: the real name of the author instead of the display name</li>\r
- <li><strong>id</strong>: Nucleus membet ID</li>\r
- <li><strong>url</strong>: URL of members website</li>\r
- <li><strong>email</strong>: email address of member (use of this one should be avoided)</li>\r
- </ul>\r
- </li>\r
- </ul>\r
-</ul>\r
-\r
-<h2>Examples</h2>\r
-\r
-<pre><code><%author%>\r
-<%author(realname)%>\r
-<a href="<%author(url)%>"><%author%></a></code></pre>\r
-\r
-</div>\r
-\r
-\r
-\r
-\r
-<div class="page">\r
-<a name="templatevar-smartbody"></a>\r
-<h1>Templatevar: smartbody</h1>\r
-\r
-<p>\r
-Examines the current item and then decides to show either the body text or the expanded text.\r
-</p>\r
-\r
-<p>When the extended part is empty, the body part is chosen. Otherwise the extended part is shown.</p>\r
-\r
-<table style="text-align: center;"><tr>\r
- <th>Part</th><th colspan="2">Empty?</th>\r
-</tr><tr>\r
- <td>Body</td><td>No</td><td>No</td>\r
-</tr><tr>\r
- <td>Extended</td><td>Yes</td><td>No</td>\r
-</tr><tr>\r
- <th>smartbody=</th><th>body part</th><th>extended part</th>\r
-</tr></table>\r
-\r
-<h2>Example use</h2>\r
-\r
-<p>The body text could be interpreted as your full text, and the extended part could be interpreted as an 'introduction' or 'exerpt', which you want to show on the front page.</p>\r
-<p>In the template used on the front page, you would use <tt><%smartbody%></tt> to insert an excerpt (if there is one), or the full text (if no excerpt). In the template for detailed items, <tt><%body%></tt> can then be used instead of the usual <tt><%body%></tt> + <tt><%more%></tt>, since <tt><%body%></tt> will contain the full item anyway.</p>\r
-\r
-\r
-\r
-\r
-</div>\r
-\r
-\r
-<div class="page">\r
-<a name="templatevar-morelink"></a>\r
-<h1>Templatevar: morelink</h1>\r
-\r
-<p>\r
-Inserts a link to the detail page for the item, as defined in the template (<a href="#templatemorelink">link to extended entry</a>). This is empty when there is no extended part.\r
-</p>\r
-\r
-<p>Note that the contents of the 'link to extended entry' templatepart is also parsed and can thus also contain <a href="#templatevars-overview">templatevariables</a>.</p>\r
-</div>\r
-\r
-\r
-<div class="page">\r
-<a name="templatevar-date"></a>\r
-<h1>Templatevar: date</h1>\r
-\r
-<p>\r
-Inserts a date using the <a href="#templatedatetime">date format specified in the template</a>. Optionally, a custom date format can be given as a parameter.\r
-</p>\r
-\r
-<h2>Arguments</h2>\r
-<ul>Optional\r
- <ul>\r
- <li><strong><i>format</i></strong>: format to be used to format the date</li>\r
- </ul>\r
-</ul>\r
-\r
-<h2>Specials</h2>\r
-\r
-<p>Four special parameters are possible:</p>\r
-<ol>\r
- <li><code>rfc822</code>: RFC822 date in local time</li>\r
- <li><code>rfc822GMT</code>: RFC date in GMT time</li>\r
- <li><code>iso8601</code>: ISO-8601 date (<a href="http://www.w3.org/TR/NOTE-datetime">W3C Date and Time Format</a> profile). Example: 2002-10-02T10:00:00-05:00</li>\r
- <li><code>utc</code>: Same as iso8601, but the date is expressed in UTC, using a "Z" for the timezone indicator.</li>\r
-</ol>\r
-\r
-<h2>Examples</h2>\r
-<pre>\r
-<%date%>\r
-<%date(%x)%>\r
-<%date(rfc822)%>\r
-<%date(rfc822GMT)%>\r
-</pre>\r
-\r
-\r
-</div>\r
-\r
-<div class="page">\r
-<a name="templatevar-time"></a>\r
-<h1>Templatevar: time</h1>\r
-\r
-<p>\r
-Inserts a time using the <a href="#templatedatetime">time format specified in the template</a>. Optionally, a custom time format can be given as a parameter.\r
-</p>\r
-\r
-<h2>Arguments</h2>\r
-<ul>Optional\r
- <ul>\r
- <li><strong><i>format</i></strong>: format to be used to format the time</li>\r
- </ul>\r
-</ul>\r
-\r
-<h2>Examples</h2>\r
-<pre>\r
-<%time%>\r
-<%time(%X)%>\r
-</pre>\r
-\r
-</div>\r
-\r
-\r
-<div class="page">\r
-<a name="templatevar-comments"></a>\r
-<h1>Templatevar: comments</h1>\r
-\r
-<p>\r
-Inserts a comments 'block'. <a href="#templatecomments">More information about the structure of this block</a>.\r
-</p>\r
-\r
-<h2>Arguments</h2>\r
-<ul><p>Optional:</p>\r
- <table><tr>\r
- <th>Name</th>\r
- <th>Contents</th>\r
- </tr><tr>\r
- <td>MaxToShow</td>\r
- <td>Amount of comments to show (when set, this overrides the <a href="#blogmaxcomments">max. comments blogsetting</a>)</td>\r
- </tr></table>\r
-</ul>\r
-\r
-<h2>Examples</h2>\r
-\r
-<pre>\r
-<%comments%>\r
-<%comments(5)%>\r
-</pre>\r
-\r
-</div>\r
-\r
-\r
-<div class="page">\r
-<a name="templatevar-syndicate_title"></a>\r
-<h1>Templatevar: syndicate_title</h1>\r
-\r
-<p>\r
-Inserts the title of the item, with HTML tags-stripped off, and shortened to 100 characters. When the text needs to be shortened, "..." is added at the end of the text.\r
-</p>\r
-\r
-<p>\r
-This variable was originally intended for use in the XML-RSS skin that comes with Nucleus, but can also be of use in other situations.\r
-</p>\r
-\r
-<h2>Arguments</h2>\r
-<ul>\r
- <li>\r
- <p>Optional:</p>\r
- <table><tr>\r
- <th>Name</th>\r
- <th>Contents</th>\r
- </tr><tr>\r
- <td>MaxChars</td>\r
- <td>Maximum amount of characters to keep (defaults to 100)</td>\r
- </tr></table>\r
- </li>\r
-</ul>\r
-\r
-<h2>Examples</h2>\r
-\r
-<pre>\r
-<%syndicate_title%>\r
-<%syndicate_title(25)%>\r
-</pre>\r
-\r
-</div>\r
-\r
-<div class="page">\r
-<a name="templatevar-syndicate_description"></a>\r
-<h1>Templatevar: syndicate_description</h1>\r
-\r
-<p>\r
-Inserts the body of the item, with HTML tags-stripped off, and shortened to 250 characters. When the text needs to be shortened, "..." is added at the end of the text.\r
-</p>\r
-\r
-<p>\r
-This variable was originally intended for use in the XML-RSS skin that comes with Nucleus, but can also be of use in other situations.\r
-</p>\r
-\r
-<h2>Arguments</h2>\r
-<ul>\r
- <li>\r
- <p>Optional:</p>\r
- <table><tr>\r
- <th>Name</th>\r
- <th>Contents</th>\r
- </tr><tr>\r
- <td>MaxChars</td>\r
- <td>Maximum amount of characters to keep (defaults to 250)</td>\r
- </tr></table>\r
- </li>\r
-</ul>\r
-\r
-<h2>Examples</h2>\r
-\r
-<pre>\r
-<%syndicate_description%>\r
-<%syndicate_description(25)%>\r
-</pre>\r
-\r
-</div>\r
-\r
-\r
-<div class="page">\r
-<a name="templatevar-image"></a>\r
-<h1>Templatevar: image</h1>\r
-\r
-<p>Inserts an inline image into an item body or template.</p>\r
-\r
-<p>In normal use, the image-templatevar is generated automatically when adding images through the media library. You can call it from within templates too, though. Note that in this last case, the image will come out of the media dir of the current item's author.</p>\r
-\r
-<h2>Arguments</h2>\r
-<ul>\r
- <li>\r
- <p>Required:</p>\r
- <table><tr>\r
- <th>Name</th>\r
- <th>Contents</th>\r
- </tr><tr>\r
- <td>filename</td>\r
- <td>Name of the image file (file gets)</td>\r
- </tr><tr>\r
- <td>width</td>\r
- <td>Width of the image (pixels or percentage)</td>\r
- </tr><tr>\r
- <td>height</td>\r
- <td>Height of the image</td>\r
- </tr><tr>\r
- <td>text</td>\r
- <td>alt-text for the image</td>\r
- </tr></table>\r
- </li>\r
- <li><strong>Note:</strong> for the image, popup and media tags, the parameters must be separated by the '|' character, <em>not</em> by a comma!</li>\r
-</ul>\r
-\r
-<h2>Examples</h2>\r
-\r
-<pre>\r
-<%image(myphoto.jpg|100|200|this is me)%>\r
-<%image(myphoto.jpg|50%|50%|this is me, but smaller)%>\r
-</pre>\r
-\r
-</div>\r
-\r
-\r
-\r
-<div class="page">\r
-<a name="templatevar-popup"></a>\r
-<h1>Templatevar: popup</h1>\r
-\r
-<p>Inserts a popup image into an item body or template.</p>\r
-\r
-<p>In normal use, the popup-templatevar is generated automatically when adding images through the media library. You can call it from within templates too, though. Note that in this last case, the image will come out of the media dir of the current item's author.</p>\r
-\r
-<h2>Arguments</h2>\r
-<ul>\r
- <li>\r
- <p>Required:</p>\r
- <table><tr>\r
- <th>Name</th>\r
- <th>Contents</th>\r
- </tr><tr>\r
- <td>filename</td>\r
- <td>Name of the image file (file gets)</td>\r
- </tr><tr>\r
- <td>width</td>\r
- <td>Width of the image (pixels or percentage)</td>\r
- </tr><tr>\r
- <td>height</td>\r
- <td>Height of the image</td>\r
- </tr><tr>\r
- <td>text</td>\r
- <td>alt-text for the image</td>\r
- </tr></table>\r
- </li>\r
- <li><strong>Note:</strong> for the image, popup and media tags, the parameters must be separated by the '|' character, <em>not</em> by a comma!</li>\r
-</ul>\r
-\r
-<h2>Examples</h2>\r
-\r
-<pre>\r
-<%popup(myphoto.jpg|100|200|this is me)%>\r
-<%popup(myphoto.jpg|50%|50%|this is me, but smaller)%>\r
-</pre>\r
-\r
-</div>\r
-\r
-\r
-\r
-<div class="page">\r
-<a name="templatevar-media"></a>\r
-<h1>Templatevar: media</h1>\r
-\r
-<p>Inserts a media object into an item body or template.</p>\r
-\r
-<p>In normal use, the media-templatevar is generated automatically when adding images through the media library. You can call it from within templates too, though. Note that in this last case, the object will come out of the media dir of the current item's author.</p>\r
-\r
-<h2>Arguments</h2>\r
-<ul>\r
- <li>\r
- <p>Required:</p>\r
- <table><tr>\r
- <th>Name</th>\r
- <th>Contents</th>\r
- </tr><tr>\r
- <td>filename</td>\r
- <td>Name of the image file (file gets)</td>\r
- </tr><tr>\r
- <td>text</td>\r
- <td>descriptive text for the media object</td>\r
- </tr></table>\r
- </li>\r
- <li><strong>Note:</strong> for the image, popup and media tags, the parameters must be separated by the '|' character, <em>not</em> by a comma!</li>\r
-</ul>\r
-\r
-<h2>Examples</h2>\r
-\r
-<pre><code><%media(mysong.mp3|listen to my new song)%></code></pre>\r
-\r
-</div>\r
-\r
-\r
-<div class="page">\r
-<a name="templatevar-edit"></a>\r
-<h1>Templatevar: edit</h1>\r
-\r
-<p>\r
-From within your template, you can add an 'edit item' link by using this template variable. By default, it will link to a popup-bookmarklet-window, but that behaviour can be changed through the <a href="#templateeditlink">editlink template</a>.\r
-</p>\r
-\r
-<p><strong>Note:</strong> only logged in members that are allowed to edit the item will see this link. In other cases, the edit-templatevar does nothing at all.</p>\r
-\r
-<h2>Example</h2>\r
-<p>An example for the item body template</p>\r
-<pre><code><h1><%title%></h1>\r
-<p><%body%> <%morelink%></p>\r
-<div class="metadata">\r
- <%edit%> <%comments%>\r
-</div></code></pre>\r
-\r
-<h2>Results in</h2>\r
-\r
-<div class="example">\r
-<h4 style="margin:2px;">Title</h4>\r
-<p style="margin:2px;">This is an item</p>\r
-<div style="margin:2px;"><a href="#templatevar-edit">edit</a> - <a href="#templatevar-edit">5 comments</a></div>\r
-</div>\r
-\r
-</div>\r
-\r
-\r
-<div class="page">\r
-<a name="templatevar-editlink"></a>\r
-<h1>Templatevar: editlink</h1>\r
-\r
-<p>\r
-Insert a link to the 'edit item' bookmarklet. This can be used in the <a href="#templateeditlink">editlink template</a> for simplicity.\r
-</p>\r
-\r
-<h2>Example</h2>\r
-\r
-<p>The <a href="#templateeditlink">'edit link'-template</a> could look like this:</p>\r
-<pre>\r
-<a href="<%editlink%>"\r
- onclick="<%editpopupcode%>">edit</a> -\r
-</pre>\r
-\r
-</div>\r
-\r
-\r
-<div class="page">\r
-<a name="templatevar-editpopupcode"></a>\r
-<h1>Templatevar: editpopupcode</h1>\r
-\r
-<p>\r
-To open a popup window for the 'edit link' window, you'll need to add some javascript code to your link. To avoid having to enter this code in the 'edit link'-template, you can insert it using the editpopupcode-templatevar.\r
-</p>\r
-\r
-<h2>Example</h2>\r
-<p>See the example for the <a href="#templatevar-editlink">editlink templatevar</a></p>\r
-</div>\r
-\r
-\r
-\r
-<div class="page">\r
-<a name="plugins"></a>\r
-<h1>Plugins</h1>\r
-<p>\r
-Nucleus allows you to install custom plugins, adding extra functionality. Plugins can do different things:\r
-</p>\r
-<ol>\r
- <li>Act as a skin variable</li>\r
- <li>Act as a template variable</li>\r
- <li>Hook into events generated by Nucleus. The 'move up' and 'move down' links in 'manage plugins' screen can be used to define the order in which plugins will be called when such an event occurs. The first plugin in the list will be called first, the last one will be called last.</li>\r
- <li>Act as actors when called through <tt>action.php</tt></li>\r
-</ol>\r
-<p>\r
-Note that the responsibility for plugins is entirely with the plugin author. He should make sure that everything works fine.\r
-</p>\r
-</div>\r
-\r
-<div class="page">\r
-<a name="parser-properties"></a>\r
-<a name="includemode"></a>\r
-<a name="includeprefix"></a>\r
-<h1>Parser Properties</h1>\r
-\r
-<p>The available parser options are described below.</p>\r
-\r
-<table>\r
- <caption>Parser properties</caption>\r
- <tr>\r
- <th>Option Name</th>\r
- <th>Values</th>\r
- </tr><tr>\r
- <td>IncludeMode</td>\r
- <td>\r
- <ul>\r
- <li><strong>normal</strong>: normal behaviour; included files are taken relative to the directory/url of the .php file generating the page.</li>\r
- <li><strong>skindir</strong>: included files are taken relative to the skindir/skinurl</li>\r
- </ul>\r
- <p>This property affects the following skinvars: <a href="#skinvar-include">include</a>, <a href="#skinvar-phpinclude">phpinclude</a>, <a href="#skinvar-parsedinclude">parsedinclude</a>, <a href="#skinvar-nucleusbutton">nucleusbutton</a></p>\r
- </td>\r
- </tr><tr>\r
- <td>IncludePrefix</td>\r
- <td>\r
- <p>This property is a prefix that get's added in front of each filename you want to include. For example, if the prefix is <tt>base/</tt> and you want to include <tt>somefile.txt</tt>, you'll end up including <tt>base/somefile.txt</tt></p>\r
- <p>This property is intended to be used in conjunction with the IncludeMode property. This way, a skin imported to <tt><em>skindir/</em>somename/</tt> can set <tt>IncludeMode</tt> to <tt>skindir</tt> and <tt>IncludePrefix</tt> to <tt>somename/</tt></p>\r
- <p>This property affects the following skinvars: <a href="#skinvar-include">include</a>, <a href="#skinvar-phpinclude">phpinclude</a>, <a href="#skinvar-parsedinclude">parsedinclude</a>, <a href="#skinvar-nucleusbutton">nucleusbutton</a></p>\r
- </td>\r
- </tr>\r
-</table>\r
-\r
-<p>The <tt>IncludePrefix</tt> and <tt>IncludeMode</tt> properties can be set globally for a skin in the general settings of a skin. Also note that from the moment a property is set, it applies to all parsed data, thus also for templates.</p>\r
-\r
-</div>\r
-\r
-</body>\r
-</html>\r
+++ /dev/null
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">\r
-<html xmlns="http://www.w3.org/1999/xhtml">\r
-<head>\r
- <!-- $Id: history.html,v 1.3 2005-03-19 07:28:32 kimitake Exp $ -->\r
- <title>Nucleus - History</title>\r
- <link rel="stylesheet" type="text/css" href="styles/manual.css" />\r
-</head>\r
-<body>\r
-\r
-<h1>Version History</h1>\r
-\r
-<p>\r
- <a href="index.html">Back to manual</a>\r
-</p>\r
-\r
-<ul>\r
- <li>\r
- <b>Nucleus v3.2 (March 7, 2005)</b>\r
- <ul>\r
- <li>ADDED: <a href="http://wiki.gednet.com/NPSkinFiles">NP_SkinFiles</a> plugin installed on full install</li>\r
- <li>FIXED: Installing plugins through install.php failed (karma)</li>\r
- <li>FIXED: whitespace at start/end got trimmed on skin edit/import (karma)</li>\r
- <li>ADDED: <code>title</code>-attributes on inline/popup images (moraes)</li>\r
- <li>ADDED: New default skin (Ivan, hcgtv, moraes, ...)</li>\r
- <li>ADDED: fr 1081569, <code><%if(category,catid,1)%></code> support (moraes)</li>\r
- <li>ADDED: support for <code>rel="nofollow"</code> (Rakaz)</li>\r
- <li>FIXED: bug 1058978, subscription list of updated plugin showed the updated subscriptions while the old subscription-list was still in the database. Nucleus now gives a warning (TeRanEX)</li>\r
- <li>FIXED: bug 1083959, closed site still allowed posting comments (karma)</li>\r
- <li>FIXED: bug 1083971, editing blog settings was not possible on PHP versions < 4.2.0 (floatval) (karma)</li>\r
- <li>FIXED: In v3.15, deleting an item via the bookmarklet failed (karma)</li>\r
- <li>ADDED: Support for <code><%blogsetting(short)%></code>, as suggested by caw (karma)</li>\r
- <li>FIXED: Default skin used <code>application/xml+rss</code> instead of <code>application/rss+xml</code>, causing RSS autodiscovery to fail. (karma)</li>\r
- <li>FIXED: Moved more hardcoded text into language files</li>\r
- <li>FIXED: Made it so malicious users cannot trick a logged in site member/admin into visiting a specifically crafted URL that performs some admin area task. (karma).</li>\r
- <li>FIXED: bug 976777, weblogs.com was not ping when posting draft (admun)</li>\r
- <li>ADDED: bug 1008171, cookie-prefix (karma)</li>\r
- <li>CHANGED: bug 1008175, move <code>getTemplate</code> into <code>MANAGER</code> class + some other performance tweaks (karma)</li>\r
- <li>ADDED: add plugin dependency check (admun)</li>\r
- <li>CHANGED: Sending out activation links rather than new passwords on new accounts, forgotten passwords, etc. (karma)</li>\r
- <li>ADDED: Plugins can now make text- and textarea-optiontypes readonly (TeRanEX)</li>\r
- <li>CHANGED: new plugin event <code>FormExtra</code> (for use with <code>ValidateForm</code>) (karma)</li>\r
- <li>CHANGED: better error handling when commenting. Errors now displayed together with comment form. (karma)</li>\r
- <li>CHANGED: actions (commenting, membermail, ...) can be done using any entry point, not just through <code>action.php</code> (karma)</li>\r
- <li>CHANGED: Added <code>$</code><code>Id$</code> info in sourcefiles (karma)</li>\r
- <li>CHANGED: PrePluginOptionsEdit-event now has an <code>extra</code>-field which can be used to add option-specific code to the page (TeRanEX)</li>\r
- <li>ADDED: new event, PrePluginOptionsUpdate, can be used by plugins to verify/modify the new value for an option (TeRanEX)</li>\r
- <li>ADDED: Plugins can now provide a documentation page, which is shown inside the admin area (TeRanEX)</li>\r
- <li>ADDED: Plugins can now limit values for an option to be only numeric (<code>datatype=numerical</code>) (TeRanEX)</li>\r
- <li>ADDED: OptionTop-methods, to let a plugin retreive an array of the x-highest (or lowest) values of an option (TeRanEX)</li>\r
- <li>ADDED: Plugins can now make specific options for items. These options can be edited directly from the item add or edit page (TeRanEX)</li>\r
- </ul>\r
- </li>\r
- <li>\r
- <b>Nucleus v3.15 (November 14, 2004)</b>\r
- <ul>\r
- <li>FIXED: Some XSS issues, as reported by Alexander Antipov</li>\r
- <li>FIXED: Validate data that is sent as HTTP headers (redirects etc) (karma)</li>\r
- <li>FIXED: bug 1029057, parsed include doesn't accept empty files (karma)</li>\r
- <li>FIXED: bug 1036849, 'relevance' listed in list of available skinvars, while it's a templatevar (karma)</li>\r
- <li>FIXED: It was possible to spoof the username on comments, even when "protect member names" was turned on. Reported by bigmouth. (karma)</li>\r
- <li>FIXED: bug 1025675, if(hasplugin) causes warnings in action log when plugin does not exist (karma)</li>\r
- <li>FIXED: bug 1008700, taking away admin attribute from a member was disallowed when that member did not have logon rights (karma)</li>\r
- <li>FIXED: bug 968925, member edit leak out repeat password box while it should be hidden (admun)</li>\r
- <li>FIXED: bug 933580, URLs in comments followed with a comma should not have the comma in the generated hyperlink (karma)</li>\r
- <li>FIXED: bug 1019584, separating search terms with a '+' character caused SQL errors (karma)</li>\r
- <li>FIXED: bug 1016217, superadmin should be allowed to edit all items/comments (karma)</li>\r
- <li>FIXED: bug 1019191, <code><%if(blogsetting,..)%></code> / <code><%if(category,...)%></code> broken on error pages (karma)</li>\r
- <li>FIXED: Made sure no code relies on the PHP5 setting <code>register_long_arrays</code> to be <code>On</code> (karma)</li>\r
- <li>FIXED: <code>Call to undefined function</code> when user specified a language in its profile (jef pober)</li>\r
- <li>FIXED: Quickmenu didn't show up after login from <code>index.php?action=showlogin</code> (karma)</li>\r
- <li>CHANGED: new plugin event <code>ValidateForm</code> (karma)</li>\r
- <li>CHANGED: Extra whitespace to make skin exports easier to read in text editors (karma)</li>\r
- <li>CHANGED: e-mail notifications are now sent as <code>utf-8</code> rather than <code>iso-8859-1</code> (karma)</li>\r
- <li>ADDED: Admin members can click the version number in the admin area to check for a newer version (karma)</li>\r
- <li>ADDED: <code><%if(admin)%></code> and <code><%if(admin,blogname)%></code> in skins (karma)</li>\r
- <li>ADDED: In the admin area, a list of all comments for a blog is now available (karma)</li>\r
- <li>ADDED: <code>ITEM::getitem</code> returns blogid, as suggested by leonbloy (karma)</li>\r
- </ul>\r
- </li>\r
- <li>\r
- <b>Nucleus v3.1 (July 28, 2004)</b>\r
- <ul>\r
- <li>FIXED: Nucleus v3.01 was missing a fix in <code>backup.php</code>, which could cause fulltext key info not to be backed up correctly</li>\r
- <li>ADDED: support for patch levels, so plugin API enhancements can be distributed to power users earlier (<a href="http://forum.nucleuscms.org/viewtopic.php?t=4142" title="More info...">suggested</a> by TeRanEX)</li>\r
- <li>FIXED: bug 974090, multiple identical SQL queries were executed when checking if a plugin is available (karma)</li>\r
- <li>FIXED: Default language wasn't always respected (fushimi)</li>\r
- <li>CHANGED: new bookmarklet style (TeRanEX / moraes)</li>\r
- <li>FIXED: After a karma vote, redirection to referer URL failed if <code>register_globals</code> is turned off (karma)</li>\r
- <li>FIXED: SQL Injection Vulnerability, reported by aCiDBiTS</li>\r
- <li>FIXED: bug 689468, moved PostAddComment from action.php to COMMENTS.php(admun)</li>\r
- <li>FIXED: bug 967580, Class variables were not explicitly defined in PHP classes (karma)</li>\r
- <li>FIXED: IE6 unreadable Admin menu textarea (admun)</li>\r
- <li>FIXED: Skin exports for skins containing CDATA sections (like the RSS feeds) caused the <code>skinbackup.xml</code> to contain invalid XML. (Import still worked, however) (karma)</li>\r
- <li>FIXED: German language file wrong translation (admun)</li>\r
- <li>CHANGED: replaced <code>split</code> by <code>preg_split</code> in the parser class. Should be faster according to PHP docs (karma)</li>\r
- <li>FIXED: documentation typo (admun)</li>\r
- <li>FIXED: PHP5: Install script failed to discover install path automatically (karma)</li>\r
- <li>FIXED: Skin parser no longer parses skinvars when they are inside a non-displayed <code>if</code>-section (karma)</li>\r
- <li>FIXED: bug 817361, prefix http:// to member's URL if missing (admun)</li>\r
- </ul>\r
- </li>\r
- <li>\r
- <b>Nucleus v3.01 (July 13, 2004)</b>\r
- <ul>\r
- <li>FIXED: PHP5: Links to plugin admin area broken (radekradek)</li>\r
- <li>FIXED: bug 966011, skins created with v2.0 could not be imported (karma)</li>\r
- <li>FIXED: Security issue spotted by rADo2</li>\r
- </ul>\r
- </li>\r
- <li>\r
- <b>Nucleus v3.0 (May 30, 2004)</b>\r
- <ul>\r
- <li>FIXED: When adding a weblog, select globally defined default skin by default (TeRanEX)</li>\r
- <li>FIXED: CSS conflict in default skin (moraes)</li>\r
- <li>FIXED: ADMIN.php no-cache after doctype added to support dynamic content for plugins in admin area (rADo2)</li>\r
- <li>FIXED: vars4.1.0.php fixed a strange bug for some PHP installs having empty $_REQUEST[] (rADo2)</li>\r
- <li>FIXED: globalfunctions.php - added a flag preventing include of vars...php twice for custom install (rADo2)</li>\r
- <li>FIXED: install.php - added a flag preventing include of vars...php twice for custom install (rADo2)</li>\r
- <li>FIXED: install.php - installCustomSkins skinbackup.xml renamed (rADo2)</li>\r
- <li>FIXED: install.php - installCustomPlugs now correctly syncs plugin events (rADo2)</li>\r
- <li>FIXED: Forcing focus on add/edit window after closing media library (nakahara21)</li>\r
- <li>ADDED: <code>class</code> attributes on textareas that allow skins/templates to be edited (karma)</li>\r
- <li>FIXED: Documentation and errors now tell to chmod config.php to 444 instead of 644 (hcgtv)</li>\r
- <li>CHANGED: Admin area style power-up (Radek)</li>\r
- <li>FIXED: Install script used $PHP_SELF, which is not available when register_globals is off (nakahara21)</li>\r
- <li>FIXED; Skin import failed if there were CDATA sections (Nucleus Japan)</li>\r
- <li>FIXED: <code>undoMagic</code> choked on array variables (Nucleus Japan)</li>\r
- <li>FIXED: htmlspecialchars causes broken url like "&amp;amp;" (Nucleus Japan)</li>\r
- <li>FIXED: PostAddCategory event was never called (Nucleus Japan)</li>\r
- <li>FIXED: PostAddCategory event was not called when creating a new weblog (Nucleus Japan)</li>\r
- <li>FIXED: <%blogurl%> problem on category lists (nakahara21)</li>\r
- <li>CHANGED: Took out the HTTP Authentication part for now (it has no real use yet, and caused problems when Nucleus is installed in a protected directory)</li>\r
- <li>FIXED: When the 'Allow login edit' option was disabled, the e-mail address was not checked for validity when a user edited his/her settings. This would cause an e-mail with new password to be sent out to an invalid address. (Frankenstein)</li>\r
- <li>FIXED: Some PHP files were missing the closing <code>?></code> tag (ikeizer)</li>\r
- <li>FIXED: Plugins were inable to delete options (leonbloy)</li>\r
- <li>FIXED: XML-RPC: <code>metaWeblog.newPost</code> fails when an empty array is passed as list of categories (caused problems with Ecto)</li>\r
- <li>FIXED: Eliminated 2 SQL queries on most requests.</li>\r
- </ul>\r
- </li>\r
- <li>\r
- <b>Nucleus v3.0 RC (April 27, 2004)</b>\r
- <ul>\r
- <li>CHANGED: Labeled it v3.0, since users started believing "2.5 beta == 25 final"</li>\r
- <li>FIXED: XML-RPC: <code>metaWeblog.editPost</code> assigned the default category again when no categories were passed along (karma).</li>\r
- <li>FIXED: XML-RPC: <code>mt.getPostCategories</code> returned an invalid result (karma)</li>\r
- <li>CHANGED: On clean install, RSS and Atom feeds contain full items rather than excerpts only (karma)</li>\r
- <li>REMOVED: Clean installation does not include RSS 0.91 feed anymore. Only the RSS 2.0 and Atom 0.3 feeds are included (karma)</li>\r
- <li>ADDED: When a skin provides a preview thumbnail, it is displayed in the skin overview (include prefix required, 100x75 preview.png, preview-large.png). Also, when a readme.html file is present in the skin include dir, a link to that file is added (karma)</li>\r
- <li>CHANGED: Allowed skin names to have slashes (<code>/</code>) in them (karma)</li>\r
- <li>FIXED: When adding media in non-IE browsers, all text was removed</li>\r
- <li>FIXED: Wrong times displayed / 'no such item' errors when MySQL server and PHP server are in different timezones (karma)</li>\r
- <li>ADDED: Made sure language files for v2.5beta can be used with v2.5final without strange strings (e.g. _SETTINGS_EXTAUTH) showing up in the admin area (karma)</li>\r
- <li>FIXED: No CSS styles were applied on 'insert media' popup (karma)</li>\r
- <li>FIXED: Some more possible problems with URL linking in comments (karma)</li>\r
- <li>FIXED: In Opera, buttons on the extended area added text to the main body text instead (karma)</li>\r
- <li>CHANGED: Admin pages are being sent as <code>text/html</code> instead of <code>application/xhtml+xml</code> again, since it caused too much javascript problems. When <code>$CONF['debug']</code> is <code>1</code> however, the pages are still sent as <code>application/xhtml+xml</code> (karma)</li>\r
- <li>FIXED: <code>itemlink</code> in templatevars didn't include itemid when used on item skins (mas)</li>\r
- <li>FIXED: Errors when deleting plugins with options (Curtis)</li>\r
- <li>FIXED: & not encoded in category names/descriptions in admin area (karma)</li>\r
- <li>ADDED: <code>hasplugin</code> option on <code>if</code> skinvars (Kazuhiko)</li>\r
- <li><del>ADDED: External Authentication (plugin contains authentication code) (Frankenstein)</del> <ins>(not in 3.0 final)</ins></li>\r
- <li><del>ADDED: HTTP Authentication (Frankenstein)</del> <ins>(not in 3.0 final)</ins></li>\r
- <li>FIXED: When using the JavaScript buttons to add images/bold text/... to the extended text area, the text was added to the main text body instead if JavaScript toolbar style was set to 'simple' (karma)</li>\r
- <li>FIXED: XML-RPC: Added <code>postid</code> in structs returned by <code>metaWeblog.getPost</code> and <code>metaWeblog.getRecentPosts</code> (karma)</li>\r
- <li>FIXED: XML-RPC: <code>metaWeblog.getRecentPosts</code> expected a <code>string</code> instead of an <code>int</code> for the <code>amountOfPosts</code> parameter. (karma)</li>\r
- <li>FIXED: convert linebreaks broke <code>\r\n</code> linebreaks (jmuto)</li>\r
- <li>FIXED: On <code>index</code> and <code>search</code> skinparts, <code>nextlink</code>/<code>prevlink</code> could not be used before a <code>blog</code> or <code>searchresults</code> skinvar was called (karma)</li>\r
- <li>FIXED: SQL errors when search query contained single quotes (<code>'</code>) (karma)</li>\r
- <li>FIXED: Backup did not store information about FULLTEXT keys. (karma)</li>\r
- <li>ADDED: Extended the <code>date</code> templatevariables with pre-defined formats <code>utc</code> and <code>iso8601</code> (needed for Atom syndication; karma)</li>\r
- <li>FIXED: super-admins that were not on a blog team did not see the categories when trying to add an item to that blog (karma)</li>\r
- <li>FIXED: <code>nextresults</code> and <code>prevresults</code> were listed as available skunvars, while they don't exist (karma)</li>\r
- <li>FIXED: XML-RPC library wrote <code><?phpxml version="1.0"?></code> as XML header (jmuto)</li>\r
- <li>FIXED: not longer showing comment form when comments disabled for blog (jmuto)</li>\r
- <li>CHANGED: Plugin options are no longer limited to 128 characters (karma)</li>\r
- <li>CHANGED: Exported skins are now saved as <code>skinbackup.xml</code> instead of <code>skindata.xml</code> to avoid confusion. (karma)</li>\r
- <li>ADDED: New plugin events <code>AdminPrePageHead</code>, <code>AdminPrePageFoot</code>, <code>PreSendContentType</code>, <code>QuickMenu</code>, <code>BookmarkletExtraHead</code> (karma)</li>\r
- <li>FIXED: Fix for bookmarklet, which failed in Opera (jmuto)</li>\r
- <li>FIXED: <code>nextitemtitle</code> and <code>previtemtitle</code> skinvars did not htmlencode their output (karma)</li>\r
- <li>CHANGED/ADDED: make all skinvars that insert links consistent. They can now all take a linktext parameter to insert a full link instead of a raw link. The <code>nextlink</code>/<code>prevlink</code> on search/index pages (introduced 2.5 beta) had to change for this. Skinvars that can take a linktext: <code>todaylink</code>, <code>archivelink</code>, <code>prevlink</code>, <code>nextlink</code> and <code>itemlink</code> (karma)</li>\r
- <li>FIXED: XML-RPC: <code>mt.setPostCategories</code> asumed that <code>isPrimary</code> was always present (karma)</li>\r
- <li>FIXED: Plugins that generate output when they are loaded can not longer break backups. (Xiffy)</li>\r
- <li>FIXED: The test that auto-disabled fancy URLs was incorrect, and also applied to top-level domains that use 3 characters (like .com) (karma)</li>\r
- </ul>\r
- </li>\r
- <li>\r
- <b>Nucleus v2.5 beta (October 11, 2003)</b>\r
- <ul>\r
- <li>ADDED: <code>if(previtem)</code>, <code>if(nextitem)</code> and <code>if(skintype,<em>typename</em>)</code> skinvars.</li>\r
- <li>FIXED: RSS conditional GET wasn't working correctly (Visa Kopu)</li>\r
- <li>ADDED: Templatevar <code>relevance</code> available when displaying search results (Xiffy)</li>\r
- <li>CHANGED: <code>nextlink</code> and <code>prevlink</code> skinvar now also available on <code>search</code> and <code>index</code> skins. (Xiffy)</li>\r
- <li>ADDED: Skinvars <code>nextitemtitle</code> and <code>previtemtitle</code> on <code>item</code> skins (Xiffy)</li>\r
- <li>FIXED: Upload did not notice duplicates correctly</li>\r
- <li>ADDED: XML-RPC: Support for <code>metaWeblog.newMediaObject</code> and <code>metaWeblog.getRecentPosts</code> methods</li>\r
- <li>ADDED: XML-RPC: Support for the <a href="http://www.movabletype.org/docs/mtmanual_programmatic.html">Movable Type API</a> (except for <code>mt.getTrackbackPings</code>)</li>\r
- <li>CHANGED: Fulltext search, prev/next links on search pages, ... (Xiffy)</li>\r
- <li>FIXED/CHANGED: Action log size drops back to 250 when more than 500 entries.</li>\r
- <li>FIXED: No more restrictions on category names</li>\r
- <li>ADDED: possibility to create <a href="http://nucleuscms.org/documentation/devdocs/custominstall.html">custom installs</a></li>\r
- <li>FIXED: XHTML admin documents now have a proper <code>xmlns</code> attribute set; <del>admin pages are now sent as <code>application/xhtml+xml</code> if the client browser accepts it.</del> <ins>Removed again in 3.5final</ins></li>\r
- <li>ADDED: Plugins can now make specific options for blogs, categories and members. These options can be edited directly from the blogsettings or member settings page.</li>\r
- <li>FIXED: It's no longer possible to select an item from an other weblog through <code>?itemid=</code> when there is a different <code>blogid=</code> parameter set in the request (or set using <code>selectBlog</code>)</li>\r
- <li>FIXED: Disallowed while trying to create a new category on item edit</li>\r
- <li>FIXED: Date/Time variables in date footer were not parsed</li>\r
- <li>FIXED: Adding an item while creating a new category prevented ping to be sent to weblogs.com</li>\r
- <li>FIXED: Right-click bookmarklet for IE (re-install to get it working with IE6)</li>\r
- <li>FIXED/CHANGED: hyperlink conversion in comments: ftp/http/mailto supported</li>\r
- <li>FIXED: spaces in between multiple notify e-mail addresses caused ar error message saying the e-mail address is invalid.</li>\r
- <li>FIXED: <code>archivedate</code> skinvar ignored the 'locale' parameter that was passed to it</li>\r
- <li>FIXED: <code>selectBlog</code> did not protect for changes in <code>?archivelist</code></li>\r
- <li>FIXED: <code>selectCategory</code> now takes a category id instead of a name (multiple categories can have the same name)</li>\r
- <li>CHANGED: Fancy URLs are only generated when <code>$CONF['Self']</code> does not end in <code>.php</code> (this avoids URLs like <code>index.php/item/95/item/94/member/1</code> when turning fancy URLs on without further configuration)</li>\r
- <li>CHANGED: Install script updates <em>config.php</em> automatically when it is writable</li>\r
- <li>CHANGED: When the content type of a skin is <code>application/xhtml+xml</code>, only send this to browsers that specify this type in their <code>HTTP_ACCEPT</code> header (otherwise, send <code>text/html</code> instead)</li>\r
- <li>CHANGED: More intelligent search keywords highlighting (multiple separate keywords etc), also available inside comment bodies now</li>\r
- <li>ADDED: Possibility to filter on filename in media library</li>\r
- <li>FIXED: <code>include('config.php')</code> caused problems when another <code>config.php</code> was in the PHP include path (nils bernhard)</li>\r
- <li>ADDED: LiveJournal conversion (moraes)</li>\r
- <li>FIXED: Karma Vote URLs used relative links to <code>action.php</code></li>\r
- <li>CHANGED: Support for PHP versions having <code>short_open_tag = Off</code> (Andrew Brampton/Terry Chay)</li>\r
- <li>ADDED: Plugin options can now also use a <code>textarea</code> type. (max. size for data is still 128 bytes though)</li>\r
- <li>FIXED: When unable to load a plugin, an error message is added to the actionlog</li>\r
- <li>FIXED: Not all messages sent to the actionlog actually appeared there</li>\r
- <li>ADDED: Made it possible to install more than one Nucleus installation in the same database (using a prefix to the tablenames)</li>\r
- <li>ADDED: Nucleus does not longer allow access to the Admin Area when files like <code>install.php</code>, <code>install.sql</code> or the <code>nucleus/upgrades</code> directory are still on the server.</li>\r
- <li>ADDED: <code><%member%></code> skinvar now also accepts <code>id</code> and <code>yourid</code> as parameter</li>\r
- <li>FIXED: JavaScript toolbar works better in Gecko-based browsers (Mozilla Firebird/Netscape 7)</li>\r
- <li>ADDED: <code>supportsFeature</code> method to plugin interface</li>\r
- <li>FIXED: Destination URL parameter on <code>membermailform</code> skinvar didn't work</li>\r
- <li>FIXED: Encoding of the window title of popup images (Osamu Higuchi)</li>\r
- <li>FIXED: Link at end of install sequence was pointing to install.php</li>\r
- </ul>\r
- </li>\r
- <li>\r
- <b>Nucleus v2.0 Final (April 3, 2003)</b>\r
- <ul>\r
- <li>FIXED: renamed the <code>xmlrpc_encode</code> and <code>xmlrpc_decode</code> methods in <code>xmlrpc.inc.php</code>, avoiding naming conflicts on some PHP configurations that are compiled with XMLRPC support</li>\r
- <li>FIXED: restore did not work on some PHP configurations, and did not correctly recognize <code>application/x-gzip</code> encoding type</li>\r
- <li>ADDED: <code>if(onteam[,blogname])</code> skinvar</li>\r
- <li>ADDED: automatic warning when headers have already been sent, with filename and linenumber included</li>\r
- <li>ADDED: About 40 extra plugin events</li>\r
- <li>ADDED: Made <code><%member%></code> available on all skin parts, and added <em>yourname</em>, <em>yoururl</em>, ... parameters</li>\r
- <li>FIXED: plugin loading is now a little more robust (non-fatal errors in the plugin PHP file used to cause a fatal error afterwards)</li>\r
- <li>ADDED: extra variables inside popup code/image code/media code template-parts: <code>width</code>, <code>height</code>, <code>link</code> and <code>text</code></li>\r
- <li>ADDED: Extra optional parameter for <code>image</code> skinvar, indicating which information to insert on the page</li>\r
- <li>CHANGED: Marked the <code>imagetext</code> skinvar as deprecated (use <code>image(caption)</code> instead)</li>\r
- <li>CHANGED: Marked the <code>ifcat</code> skinvar as deprecated (use <code>if(category)</code> instead)</li>\r
- <li>CHANGED: Marked the <code>vars</code> skinvar as deprecated (if anyone needs a hidden 'itemid' formfield [are there?], the itemid skinvar can be used instead)</li>\r
- <li>ADDED: <code>doTemplateCommentsVar(&$item, &$comment)</code> method in plugin interface</li>\r
- <li>CHANGED: comments are now also parsed using the same method as skins and items, allowing plugins, includes and more to be used there as well</li>\r
- <li>FIXED: guests cannot longer place 'fake' comments (making it look as if a regsitered memeber made the comment)</li>\r
- <li>FIXED: item contents is no longer trimmed</li>\r
- <li>FIXED: Made install script look less messy</li>\r
- <li>ADDED: <code>selectItem($id)</code> method</li>\r
- <li>FIXED: Unable to disable comments through 'edit item'</li>\r
- <li>ADDED: Plugins: EditItemFormExtras event gets itemid as separate parameter</li>\r
- <li>FIXED: missing ; in presented new blog code</li>\r
- <li>FIXED: PHP 4.0.6 didn't show item/member/... lists on admin area (PHP bug)</li>\r
- <li>ADDED: Plugin Hook: BlogSettingsFormExtras</li>\r
- <li>FIXED: <%if(blogsetting,bcomments,1)%> skinvars were not working</li>\r
- <li>ADDED: <%if(loggedin)%> skinvars were not working</li>\r
- </ul>\r
- </li>\r
- <li>\r
- <b>Nucleus v2.0 beta (January 18, 2003)</b>\r
- <ul>\r
- <li>FIXED: Highlighted text no longer has <!--h--> in it</li>\r
- <li>ADDED; Plugin hook: PostAuthentication</li>\r
- <li>ADDED: Plugin hooks PreAddItemForm, AddItemFormExtras and EditItemFormExtras</li>\r
- <li>CHANGED: Notifications emails (new comment, etc) are not sent to the person causing the notification (comment author)</li>\r
- <li>ADDED: plugins can access global variables <code>$currentTemplateName</code> and <code>$currentSkinName</code></li>\r
- <li>CHANGED: Spaces after commas in <%image%>, <%popup%>, <%media%> </li>\r
- <li>FIXED: HTML to Text conversion didn't always work</li>\r
- <li>ADDED: <%date%> templatevars extras (rfc822 & rfc822GMT) (Xiffy)</li>\r
- <li>ADDED: ranges for <%blog(...)%> and <%otherblog(...)%> skinvars</li>\r
- <li>ADDED: templatevars <%author(email)%>, <%author(url)%> and <%author(id)%<</li>\r
- <li>CHANGED: Added info on new weblog creation (split up creation process into two steps)</li>\r
- <li>FIXED: Login screen after email address change did not work correctly</li>\r
- <li>ADDED: Plugin Hook: PrePluginOptionsEdit</li>\r
- <li>ADDED: Added a getMinNucleusVersion method to the plugin interface</li>\r
- <li>ADDED: PostPluginOptionsUpdate plugin event</li>\r
- <li>ADDED: Javascript toolbar: align left/center/right buttons (Irmo)</li>\r
- <li>ADDED: RSD skin/template</li>\r
- <li>ADDED: 'Fancy' URLs option & support files. Allows for URLs like http://hostname/archive/1/2003-01-05 instead of http://hostname/index.php?blogid=1&archive=2003-01-05</li>\r
- <li>ADDED: RSS 2.0 skin/template (Xiffy)</li>\r
- <li>ADDED: skinvar <%skinname%></li>\r
- <li>ADDED: if/else in skins. parameters for 'if' are currently 'category' (=ifcat) or 'blogsetting/settingname' (settingname = columnname from database...)</li>\r
- <li>ADDED: Etag/If-None-Match support for xml-rss.php (needs some more work)</li>\r
- <li>FIXED: more friendly bookmarklet for Opera 6 users (all tabs are visible, editing through bookmarklet works)</li>\r
- <li>ADDED: on edit item, the post time can be changed (only if 'allow post to past' is enabled)</li>\r
- <li>ADDED: 'Allow Post to Past' option on weblog basis</li>\r
- <li>ADDED: IncludeMode and IncludePrefix settings in nucleus_skin_desc + interface to change these settings + user IncludePrefix while parsing includes.</li>\r
- <li>CHANGED: nucleusbutton skinvar now takes into account IncludeMode</li>\r
- <li>CHANGED: btimeoffset column is now DECIMAL instead of INT </li>\r
- <li>CHANGED: took away actionurl parameters from commentform and membermailform skinvars (it's a global setting now)</li>\r
- <li>ADDED: <%set(property,value)%< skin/template-var to set global parser properties. Only one option defined so far: 'IncludeMode'. Can be 'skindir' or 'normal' and affects the include/parseinclude/phpinclude skin/templatevars</li>\r
- <li>ADDED: <%skinfile(filename)%> skinvar (to be used on imported skins)</li>\r
- <li>ADDED: $CONF['SkinsURL'] and $DIR_SKINS (config.php)</li>\r
- <li>CHANGED: friendly names used on skin edit (instead of 'index', 'item' etc)</li>\r
- <li>ADDED: action url to global settings (action.php location)</li>\r
- <li>ADDED: $desturl and $actionurl parameters on membermailform skinvar</li>\r
- <li>ADDED: skin import/export class</li>\r
- <li>CHANGED: media library now works with multiple collections, of which one is private to the site member, and the rest is globally shared.</li>\r
- <li>CHANGED: base skin can now be changed (it's now a config setting). This skin is ONLY used in two cased: when all else fails, and when the selected skin does not have contents for the needed skinpart</li>\r
- <li>CHANGED: positive and negative karma votes are now kept separately, since that works better and is more flexible. The <%karma%> templatevar received an extra parameter to select which information to show</li>\r
- <li>ADDED: skinvars archivenext/archiveprev/archivetype</li>\r
- <li>CHANGED: skinvars nextlink/prevlink now also work on archive skins</li>\r
- <li>CHANGED: move item now also allows to choose a category</li>\r
- <li>CHANGED: new items can be added to other blogs also now</li>\r
- <li>FIXED: archivedate skinvar displaying wrong date</li>\r
- <li>FIXED: serverVar function was not working when using vars4.0.6.php</li>\r
- <li>ADDED: now also listing category in itemlist</li>\r
- <li>CHANGED: Admin Area now uses the Site Name instead of Nucleus</li>\r
- <li>CHANGED: admin.css and admin area: corrected h1, h2, h3 depth levels</li>\r
- <li>ADDED: batch operations</li>\r
- <li>FIXED: when language settings are changed, the new language is used immediately (only for global settings, not for member settings)</li>\r
- <li>CHANGED: archivelist query now uses the SUBSTRING MySQL function instead of the YEAR/DAYOFMONTH/MONTH functions (caused trouble for some people)</li>\r
- <li>ADDED: maxlength attributes on forms</li>\r
- <li>CHANGED: commentlists: placed time/author in same table cell </li>\r
- <li>ADDED: extra convertor for Blogger blogs that use YACCS comments (exportable in CAIF format)</li>\r
- <li>FIXED: some possible security issues (thanks to Morgan Tocker)</li>\r
- <li>FIXED: shortening of strings does not corrupt HTML entities anymore (e.g. in RSS-feeds)</li>\r
- <li>CHANGED: links in comments are now handled differently. Part of the URL is now displayed instead of just http://.../</li>\r
- <li>ADDED: Opera version of bookmarklet</li>\r
- <li>ADDED: selectLanguage() function to force the use of a certain language file</li>\r
- <li>REMOVED: there was a plugin event AddItem which was actually not needed at all (wasn't included in the documentation too)</li>\r
- <li>ADDED: archivelist skinvars now takes an extra limit-parameter</li>\r
- <li>CHANGED: moved all forms which can be included through skinvar out of SKIN.php and into .template files in the nucleus/forms directory.</li>\r
- <li>FIXED: 'clone skin' did not copy contenttype</li>\r
- <li>FIXED: Errors in XML-RSS template (upgrading users might need to change this manually or by importing an updated skin)</li>\r
- </ul>\r
- </li>\r
- <li>\r
- <b>Nucleus v1.55 (August 26, 2002)</b>\r
- <ul>\r
- <li>ADDED: <%archivedaylist%> and <%otherarchivedaylist%> skinvars (to show archives by day instead of by month)</li>\r
- <li>FIXED: PHP error on createAccount through action.php</li>\r
- <li>ADDED: new parseFile-method available in index.php. Allows to parse non-blog pages with skinvars</li>\r
- <li>FIXED: editing comments with hyperreffed links</li>\r
- <li>ADDED: 'delete item' option on edit item, plus 'delete item' confirmation screens (also on bookmarklet)</li>\r
- <li>CHANGED: on multi-blog systems, the admin now only gets to see the blogs for which (s)he is on the team. All other blogs are available through an 'show all blogs...' link</li>\r
- <li>FIXED: link to recent items after weblogs.com ping was broken</li>\r
- <li>CHANGED: plugin event call 'PreAddComment' moved to immediately before the item is added to the database</li>\r
- <li>FIXED: tab-orders were not correct on multiple admin pages</li>\r
- <li>ADDED: <%itemid%> and <%itemlink%> available on item pages</li>\r
- <li>FIXED: install.php now works when the PHP option magic_quotes_runtime is enabled</li>\r
- <li>CHANGED: install.php gives an error when PHP is compiled without MySQL installed</li>\r
- <li>CHANGED: install.php automatically fills the 'mysql hostname' field when PHP option mysql.default_host is set.</li>\r
- <li>FIXED: greymatter convert was not putting a reference to the weblog in the comments table.</li>\r
- <li>CHANGED: added some linebreaks in the login screen of the admin area</li>\r
- <li>ADDED: new plugin events: PreAddItem, PreUpdateItem, PrepareItemForEdit, PreUpdateComment, PrepareCommentForEdit</li>\r
- <li>ADDED: JavaScript to hide empty fields when editing templates</li>\r
- <li>CHANGED: Admin area CSS now uses relative fontsizes and fontsize-keywords (also added trick to make IE5 get it right)</li>\r
- <li>FIXED: backup was broken :(</li>\r
- <li>CHANGED: replaced an SQL query that caused problems (NATURAL JOIN replaced by implicit inner join)</li>\r
- <li>ADDED: <%self%> available in categorylist templates</li>\r
- <li>ADDED: <%itemtitle%> skinvar available on item-skins</li>\r
- <li>FIXED: editing a comment you made in a blog that's not your own resulted in a 'disallowed action' error </li>\r
- <li>FIXED: plugin was listed twice in the list of available skinvars</li>\r
- <li>ADDED: <%archivedate%> skinvar on archive skins</li>\r
- <li>FIXED: admininstrators could not edit details of other members</li>\r
- </ul>\r
- </li>\r
- <li>\r
- <b>Nucleus v1.5 (August 13, 2002)</b>\r
- <ul>\r
- <li>ADDED: Introducing plugins (define your own skinvars and templatevars, add event listeners, ...)</li>\r
- <li>CHANGED: simpler and more accessible default templates/skins</li>\r
- <li>FIXED: GreyMatter convert now works when the <tt>asp_tags</tt> option in PHP is enabled</li>\r
- <li>ADDED: title and authorName fields in Blogger API getRecentItems call</li>\r
- <li>ADDED: HTML label tags for radio buttons and checkboxes (this way you can click anywhere on the text instead of only on the radio button/checkbox itself)</li>\r
- <li>FIXED: deleting a comment you made in a blog that's not your own resulted in a 'disallowed action' error (thanks moraes)</li>\r
- <li>CHANGED: the place where comments are inserted can now be chosen from within the template. Just include <%comments%> in the ITEM templatepart whereever you want the comment count (or comments) to appear. In upgrading, the old ordening is imitated by adding '<%comments%>' to the end of the ITEM template part.</li>\r
- <li>CHANGED: now trimming parameters that were passed to skinvars/templatevars</li>\r
- <li>ADDED: <%referer%> skinvar, which inserts HTTP_REFERER</li>\r
- <li>ADDED: '- New Category -' can now be chosen on add/edit item (only for blog admins). A new category is then created, and the chance is given to edit the category details.</li>\r
- <li>ADDED: optional attributes for templatevars <%time(format)%>, <%date(format)%>, <%syndicate_title(maxLength)%>, <%syndicate_description(maxLength)%></li>\r
- <li>ADDED: new user registrations show up in action log</li>\r
- <li>ADDED: new option to allow non-members to send messages (the membermailform)</li>\r
- <li>FIXED: when an admin edits an item written by someone else, and uploads an image, the image is now saved under the original authors media directory</li>\r
- <li>CHANGED: <%author(realname)%> in item templates now inserts the real name of the author</li>\r
- <li>FIXED: install.php now works when magic_quotes_gpc is disabled</li>\r
- <li>ADDED: New settings: PluginURL, MaxUploadSize, ProtectMemNames</li>\r
- <li>ADDED: hotlinks to the defined skinparts from the skin overview (also gives a good view on which skinparts have been defined and which have not been defined)</li>\r
- <li>ADDED: <%smartbody%> for item templates, which chooses between showing the body and extended part, based on the extended part being empty or not. Using this, the body text can be your full text, and the extended part could be seen as an 'introduction', which you want to show on the front page. (request from smarko)</li>\r
- <li>ADDED: <%edit%>, <%editlink%> and <%editpopupcode%> can be used in item templates (and in items themselves) to insert a link to where the item can be edited/deleted. (default setting uses bookmarklet to do this). The edit links only get shown when the user is allowed to edit a certain item (blog admin or item author). </li>\r
- <li>FIXED: bookmarklet now works correctly when magic_quotes_gpc and register_globals are turned off </li>\r
- <li>ADDED: PHP and MySQL versions are listed during the installation proces, with warnings when those version numbers are lower than what Nucleus requires</li>\r
- <li>CHANGED: item parsing method changed, so it's more easily extensible. plugin, parsedinclude, include and phpinclude are now also allowed in some templates. Inside items, there are also 3 allowed variables: 'image', 'media' and 'popup'</li>\r
- <li>FIXED: image popups didn't work with register_globals disabled</li>\r
- <li>CHANGED: renamed method: getBlogidFromName -> getBlogIDFromName (consistency)</li>\r
- <li>ADDED: method selectCategory($name)</li>\r
- <li>FIXED: Nucleus now handles data correctly when magic_quotes_gpc is disabled (solves some problems with template editing)</li>\r
- <li>CHANGED: categories in selection box are now sorted by name (tip from katatonik)</li>\r
- <li>FIXED: Not all tables got exported on backup :( (thanks Xiffy!)</li>\r
- <li>FIXED: add item form didn't handle keyboard shortcuts correctly (thanks Hop!)</li>\r
- <li>CHANGED: 'remember me' checkbox is now checked when the information was remembered from before (this way, the cookie gets set again and does not expire)</li>\r
- <li>FIXED: after a category got selected through skinvar parameters, skinvars applying to all categories also got applied only to the last category that was selected (thanks Xiffy!)</li>\r
- <li>ADDED: table nucleus_comment got an extra cblog column (redundant) to allow to find the blog that goes with a comment more easily.</li>\r
- <li>FIXED: email address checking routine (false email addresses like foo@@bar.com were allowed)</li>\r
- <li>CHANGED: New installations now get a robots.txt file (disallows karma voting/commenting/... by bots)</li>\r
- <li>CHANGED: JavaScript preview now shows image outlines and popup image links</li>\r
- <li>CHANGED: searchform now available on ALL skintypes</li>\r
- <li>FIXED: headers in globalfunctions/SKIN.php now sent _only_ when no other headers have been sent before. Should make including easier.</li>\r
- <li>CHANGED: RSS-auto-discovery tag in default skin</li>\r
- <li>CHANGED: formfields got labels (accessibility issue). Also access keys have been defined: L for login, 4 for Search (on windows, actions keys are used together with the ALT key)</li>\r
- <li>ADDED: left and right box buttons on JS toolbar</li>\r
- <li>FIXED: truncated entry when login is requested after adding (data didn't get passed on correctly)</li>\r
- <li>ADDED: <%authorlink%> to template vars for item templates (this one can take catid into account)</li>\r
- <li>ADDED: $CONF['Self'] => $CONF['ItemURL'], $CONF['IndexURL'], ... to optionally allow people to use different files for items/archives/...</li>\r
- <li>CHANGED: Now using mysql_fetch_assoc instead of mysql_fetch_array (efficiency)</li>\r
- <li>CHANGED: The <%searchresults%> and <%othersearchresults%> skintags got an extra parameter to limit the number of results (defaults to 50)</li>\r
- <li>FIXED: doError did not take into account chosen skin</li>\r
- <li>FIXED: Commentform not shown anymore for closed items (a message is shown instead)</li>\r
- <li>CHANGED: Removed all unneccessary javascript: links (deprecated)</li>\r
- <li>CHANGED: Media: Procentual width and height values are now allowed in image and inline constructs (e.g. <%image(bla.gif|50%|50%|lala)%>)</li>\r
- <li>FIXED: Blogger API: getPost wasn't returning category name</li>\r
- <li>FIXED: Blogger API: getRecentPosts wasn't converting linebreaks</li>\r
- <li>FIXED: surpressed warning on mysql_close</li>\r
- <li>FIXED: install-script now also accepts email addresses that contain uppercase characters</li>\r
- <li>FIXED: imported items did not show up in the weblog</li>\r
- <li>FIXED: blogger api <title> thingie didn't work</li>\r
- <li>CHANGED: Made all uploaded files be chmodded to 644</li>\r
- <li>FIXED: template cloning didn't clone all parts</li>\r
- <li>FIXED: After new user registration, there was a redirect to the members url (use 'desturl' now to indicate destination url)</li>\r
- <li>...and a lot of small changes</li>\r
- </ul>\r
- </li>\r
- <li>\r
- <b>Nucleus v1.1 (April 30, 2002)</b>\r
- <ul>\r
- <li>Started assuming that at least PHP 4.0.5 is available. (for older PHP versions, some small code-changes should do the trick)</li>\r
- <li>Added bookmarklets for Mac/IE5 users and Mozilla. Also, made the title of the page also show up in the title field of the new item. Makes more sense. <small>(thanks to <a href="http://www.35mm.org">Ricardo Lamego</a>)</small></li>\r
- <li>Made the <a href="http://www.php.net/manual/en/language.variables.predefined.php" title="see PHP doc">predefined PHP variables</a> available in scripts called through <%phpinclude(..)%> <small>(thanks to <a href="http://www.polskaya.be/">Polskaya</a> for noticing the problem)</small></li>\r
- <li>Fixed: <%additemform%> and <%nucleusbutton%> didn't work when admin area was not in a dir named 'nucleus'</li>\r
- <li>Added: <%sitevar(adminurl)%> and shortcut <%adminurl%> to include the URL of the admin area</li>\r
- <li>Changed all references to nucleus.demuynck.org into references to <a href="http://nucleuscms.org/">nucleuscms.org</a></li>\r
- <li>Extra settings: cookie domain, cookie path, secure cookie (for https)</li>\r
- <li>Instead of stripping tags in comments, < and > are now replaced by their entities (&lt; and &gt;). This way, greater than and lower than signs can be used in comments <small>(inspiration by <a href="http://www.adfundum.be/">Steven Verbruggen</a>)</small></li>\r
- <li>Added charset to language files, so international character sets can be used when needed <small>(<a href="http://forum.nucleuscms.org/viewtopic.php?t=56">forum</a>)</small></li>\r
- <li>Added an extra content-type attribute to skins, so the output type can be set correctly by Nucleus</li>\r
- <li>Removed the 'headlines' skin and templates. Don't want new users to get too confused.</li>\r
- <li>Notification emails now also get the senders display name</li>\r
- <li>All errors now handled by doError method in globalfunctions.php (makes it easier when you want to use your own error handler instead of the error skin)</li>\r
- <li>Site-members can now override the default site-language setting for the pages they visit</li>\r
- <li>Added skinvars <%otherarchive%> and <%othersearchresults%> for use on archive/search pages.</li>\r
- <li>Skinvar <%searchform%> now takes an optional parameter: blogname (for which you want a search form)</li>\r
- <li>Introducing categories! (new settings; new skinvars category, categorylist and ifcat; new template vars <%category%>, <%catid%> and <%categorylink%>; new optional category params for skinvars blog, otherblog, archive, otherarchive, archivelist, otherarchivelist)</li>\r
- <li>Fixed: error skin didn't get copied on skin cloning</li>\r
- <li>Even more new skinvars to make skinning easier: <%todaylink%>, <%archivelink%>, <%prevlink%> and <%nextlink%> <small>(<a href="http://forum.nucleuscms.org/viewtopic.php?t=67">forum</a>)</small></li>\r
- <li>Fixed: The install script was giving warnings about uninitialized variables on some PHP configurations</li>\r
- <li>Moved version history to separate file</li>\r
- <li>Made upgrade scripts a little more robust and more verbose</li>\r
- <li>XML-RPC: <a href="http://www.xmlrpc.com/metaWeblogApi">metaWeblog API</a> support</li>\r
- <li>XML-RPC: <title> and <category> tags can now be used with the Blogger API (similar to b2)</li>\r
- <li>Fixed problem with create account <small>(<a href="http://forum.nucleuscms.org/viewtopic.php?t=92">forum</a>)</small></li>\r
- <li>Made it so Nucleus still works when using PHP >4.1.0 with register_globals turned off, which is the default setting for new installations <small>(<a href="http://forum.nucleuscms.org/viewtopic.php?t=95">forum</a>)</small></li>\r
- <li>Media library: popup now requests login when needed</li>\r
- <li>Media library: option to auto-prefix uploaded files with date (turned on by default)</li>\r
- <li>Backup/Restore: backup file name now has date + nucleus.sql renamed to install.sql + extra "I'm sure"-checkbox on restore to avoid errors <small>(<a href="http://forum.nucleuscms.org/viewtopic.php?t=100">forum</a>)</small></li>\r
- <li>Javascript toolbar: simpler version available that works in Mozilla</li>\r
- <li>Fixed: Closed items don't show 'no comments' link anymore <small>(forum)</small></li>\r
- <li>Fixed: Drafts items don't result in 'January 1970' entries in archivelist</li>\r
- <li>Fixed: Added <image> tag to xmlrss skin for new installs. It's required. (defaults to a nucleus logo, up to you to change it)</li>\r
- <li>Fixed: Error with restore (content with semicolons in it would not get restored)</li>\r
- <li>Added: Extra notification options</li>\r
- <li>Archives can now also be accessed by day, and an extra daylink template var is available in date headers</li>\r
- <li>Fixes in default skin</li>\r
- <li>As always, lots of small fixes & code rewrites</li>\r
- <li>\r
- Changes (additions to and <del>deletions</del> from) language file:\r
- <ul>\r
- <li>_SETTINGS_COOKIES_TITLE</li>\r
- <li>_SETTINGS_COOKIEDOMAIN</li>\r
- <li>_SETTINGS_COOKIEPATH</li>\r
- <li>_SETTINGS_COOKIESECURE</li>\r
- <li>_SKIN_UPDATED</li>\r
- <li>_TEMPLATE_UPDATED</li>\r
- <li>_CHARSET</li>\r
- <li>_MEMBERS_DEFLANG</li>\r
- <li>_MEMBERS_USESITELANG</li>\r
- <li>_ADD_CATEGORY</li>\r
- <li>_ADD_DRAFTNFUTURE</li>\r
- <li>_ERROR_NOSUCHLANGUAGE</li>\r
- <li>_ERROR_NOSUCHCATEGORY</li>\r
- <li>_ERROR_DELETEDEFCATEGORY</li>\r
- <li>_ERROR_DELETELASTCATEGORY</li>\r
- <li>_ERROR_BADCATEGORYNAME</li>\r
- <li>_ERROR_DUPCATEGORYNAME</li>\r
- <li>_CONFIRMTXT_CATEGORY</li>\r
- <li>_DELETED_CATEGORY</li>\r
- <li>_LISTS_TYPE</li>\r
- <li>_SKIN_TYPE</li>\r
- <li>_YOURSITE</li>\r
- <li><del>_LIST_COMMENT_HOST</del></li>\r
- <li>_SETTINGS_MEDIA</li>\r
- <li>_SETTINGS_MEDIAPREFIX</li>\r
- <li>_SETTINGS_MEMBERS</li>\r
- <li>_LOGIN_FORGOT</li>\r
- <li>_TEMPLATE_CATEGORYLIST</li>\r
- <li>_TEMPLATE_CATHEADER</li>\r
- <li>_TEMPLATE_CATITEM</li>\r
- <li>_TEMPLATE_CATFOOTER</li>\r
- <li>_EBLOG_DEFCAT</li>\r
- <li>_EBLOG_CAT_TITLE</li>\r
- <li>_EBLOG_CAT_NAME</li>\r
- <li>_EBLOG_CAT_DESC</li>\r
- <li>_EBLOG_CAT_CREATE</li>\r
- <li>_EBLOG_CAT_UPDATE</li>\r
- <li>_EBLOG_CAT_UPDATE_BTN</li>\r
- <li>_EBLOG_NOTIFY_ON</li>\r
- <li>_EBLOG_NOTIFY_COMMENT</li>\r
- <li>_EBLOG_NOTIFY_KARMA</li>\r
- <li>_EBLOG_NOTIFY_ITEM</li>\r
-\r
- </ul>\r
- </li>\r
- </ul>\r
- </li>\r
- <li>\r
- <b>Nucleus v1.0 (March 6, 2002)</b>\r
- <ul>\r
- <li>Fixed: width & height of <%image()%> construct</li>\r
- <li>Changed: windows in popup windows don't have a white border anymore <small>(<a href="http://www.nucleuscms.org/forum/viewtopic.php?t=3">see forum</a>)</small>\r
- </li>\r
- <li>Fixed: bug with single quotes in image/popup constructs <small>(<a href="http://www.nucleuscms.org/index.php?itemid=1812">see message</a>)</small></li>\r
- <li>Fixed: fatal error in 'send password' method <small>(thanks to <a href="http://modder.org/HANK!">HANK!</a>)</small></li>\r
- <li>Fixed: removed some illegal characters from code documentation since they caused parse errors on some systems <small>(thanks to Martin Belle-Isle and Rodrigo Moraes; see <a href="http://www.nucleuscms.org/forum/viewtopic.php?t=5">forum</a> for extra details)</small></li>\r
- <li>Refined: added a note about spaces to the install-script <small>(see <a href="http://www.nucleuscms.org/forum/viewtopic.php?t=14">forum</a>)</small></li>\r
- <li>Added: donate-link on admin page <small>(hey! it's free, I have the right to bug you with this sort of things ;-)</small></li>\r
- <li>Changed: it's not possible anymore to create a draft future item. That didn't make sense. You can now choose whether you want to publish a draft item either immediately or in the future when editing the item</li>\r
- <li>Changed: made it so that the 'disable comments' choice is not offered anymore on add/edit item form when commenting is disabled in the blogsettings</li>\r
- <li>Fixed: where possible, redirection after commenting is now done to the correct file (instead of index.php)</li>\r
- <li>Fixed: bug where only superadmins could change usernames/passwords, even if the corresponding option in the settings was set <small>(thx <a href="http://www.sneppah.be/">slekke</a>)</small></li>\r
- <li>Added: allowed variables for a skinpart now shown when editing skin</li>\r
- <li>Wrote new re-usable parser that does skin parsing in a way that is more flexible and less prone to errors.</li>\r
- <li>Changed: passwords now stored in encrypted form</li>\r
- <li>Optimizing: optimized some queries</li>\r
- <li>Added: <%otherarchivelist(blogname,templatename)%> in skins</li>\r
- <li>Added: Blogger Convert</li>\r
- <li>Added: "shared computer" checkbox on login. Checking this box will make your cookie expire at the end of the session (instead of taking the global site setting) <small>(see <a href="http://www.nucleuscms.org/forum/viewtopic.php?t=33">forum</a>)</small></li>\r
- <li>Added: "remember me" checkbox on comment forms for non-members</li>\r
- <li>Most language related things are now moved to language files. Now you can roll your own :)</li>\r
- <li>Added: optional parameters rows/cols in membermailform skinvar</li>\r
- <li>Added: skinvars: <%phpinclude(file)%> and <%parsedinclude(file)%>. <%plugin%> is now deprecated (in favor of phpinclude). The plugins directory should also not be used anymore (it'll get another function in a later version)</li>\r
- <li>Added: skinvar <%self%> which includes the filename of the currently executing script (index.php or whatever is sen in $CONF['Self'])</li>\r
- <li>Automatich hyperlink detection in comments now also recognizes comma's</li>\r
- <li>Added: selectSkin('name') and selectBlog('name') functions available for use in index.php</li>\r
- <li>Added: Small <a href="tips.html#backups">restore-guide</a> for the worst case scenario</li>\r
- <li>Added: A toolbar with markup buttons on add/edit item, plus option to disable it in the settings. When Mozilla is used, Nucleus tries to disable it automatically (since it doesn't work there anyway)</li>\r
- <li>Fixed: media were not expanded in extended text <small>(thx <a href="http://www.elrado.nl/">raoul</a>)</small></li>\r
- <li>Changed javascript code of popup help so it works better in Mozilla <small>(thanks to <a href="http://idontsmoke.co.uk/">Paul Sowden</a>)</small></li>\r
- <li>UI improvements</li>\r
- <li>New default skin (the old one was just plain ugly :-)</li>\r
- <li>Small bug-fixes</li>\r
- </ul>\r
- </li>\r
- <li>\r
- <b>Nucleus v0.96 (December 13, 2001)</b>\r
- <ul>\r
- <li>Added: add-item-preview now also in admin area</li>\r
- <li>Added: action log</li>\r
- <li>Added: media library and file-upload</li>\r
- <li>Added: karma votes</li>\r
- <li>Added: Option to disable loginname/password changing by members</li>\r
- <li>Added: simple popup windows for image viewing</li>\r
- <li>Fixed: E-mail address validation check does not longer require addresses to be all lowercase</li>\r
- <li>Fixed: magic_quotes are now explicitly disabled, solving escaping problems (thanks to <a href="http://www.aroundmyroom.com/">Dennis Slagers</a>)</li>\r
- <li>Fixed: error handling when pinging weblogs.com</li>\r
- <li>Added: now also storing IP with comments (next to hostname)</li>\r
- <li>Added: IP banlist (to prevent nasty people from commenting/voting)</li>\r
- <li>Changed: Notification mails now include the item's title</li>\r
- <li>Changed: Weblogs can only be deleted by super-admins</li>\r
- <li>Changed: <a href="http://xmlrpc.usefulinc.com/">XML-RPC for PHP</a> v1.02</li>\r
- <li>Added: Small <a href="tips.html#filepermissions">guide to changing/setting filepermission</a> in docs</li>\r
- <li>Changed: Upgrade and conversion scripts now get packed separately</li>\r
- <li>Fixed: For error skins, the default skin is used now instead of 'default' (thanks to <a href="http://www.sneppah.be/">Slekke</a>)</li>\r
- <li>Fixed: The code to insert the Nucleus button was not XHTML (strict) compliant, oh my!</li>\r
- <li>GM Conversion: The conversion of {{popup}} now works correctly (and copies image files to the media dir)</li>\r
- <li>Fixed: a minor bug in XML-RPC call blogger.getUsersBlogs</li>\r
- <li>Fixed: a major bug in XML-RPC call blogger.getRecentPosts</li>\r
- <li>Fixed: problem concerning template editing and the XML-RPC call blogger.setTemplate</li>\r
- </ul>\r
- </li>\r
- <li>\r
- <b>Nucleus v0.95 (October 10, 2001)</b>\r
- <ul>\r
- <li>Added: per-blog setting to enable/disable line break conversion</li>\r
- <li>Added: per-blog setting to send a ping to Userland (weblogs.com) when you update your blog. This way, you'll be able to end up in the weblogs.com update-list</li>\r
- <li>Switched to v1.01 of the XML-RPC for PHP libs (was v1.0)</li>\r
- <li>Upgrade scripts are available (for upgrade from versions < 0.95 to v0.95)</li>\r
- <li>Added: <%previtem%> and <%nextitem%> can be used in item-skins</li>\r
- <li>Some changes in the default database dump</li>\r
- </ul>\r
- </li>\r
- <li>\r
- <b>Nucleus v0.94 (September 27, 2001)</b>\r
- <ul>\r
- <li>Changed: 'Add Item' in admin-area now redirects to blog url (if available)</li>\r
- <li>Changed: <i>headlines.php</i> and <i>xml-rss.php</i> adapted to behave better in disabled-site situations</li>\r
- <li>Changed: <%userlink%> got smarter in recognizing e-mail addresses</li>\r
- <li>Added: tabindices in forms to make traversal with the TAB-button more natural</li>\r
- <li>Fixed: bookmarklet login did not pass data correctly</li>\r
- <li>Added: JavaScript to open links in new window (javascrip/opennew.js)</li>\r
- <li>Added: <%year%> and <%month%> in templates for archivelist-items</li>\r
- <li>CSS lightly changed because IE6 is a little bit more picky (which is actually a good thing)</li>\r
- <li>Fixed: popup code (JavaScript) for help-windows (didn't work ok in IE6)</li>\r
- <li>Added: Description or summary of what you are going to delete on the confirmation screens</li>\r
- <li>Added: Workaround (for advanced users) to get your archives into search engines (on tips & suggestions page)</li>\r
- <li>Fixed: A bug in the XML-RPC server</li>\r
- </ul>\r
- </li>\r
- <li>\r
- <b>Nucleus v0.93 (September 19, 2001)</b>\r
- <ul>\r
- <li>Added: friendly error message on error with nucleusdir definition in config.php</li>\r
- <li>Changed: call_user_func instead of eval</li>\r
- <li>Added: forms included by skin variables now have class="formfield" and class="formbutton" arguments, to allow more control on the layout</li>\r
- <li>Created a <a href="tips.html">'Tips & Suggestions'</a> page next to this manual</li>\r
- <li>XML-RPC API: added nucleus.addDatedItem method</li>\r
- <li>XML-RPC API: added nucleus.editItem method</li>\r
- <li>XML-RPC API: added nucleus.getRecentItems method</li>\r
- <li>XML-RPC API: added nucleus.getItem method</li>\r
- <li>Added documentation for XML-RPC nucleus.* methods</li>\r
- <li>Fix: Search results didn't show the amount of comments. Now they do.</li>\r
- </ul>\r
- </li>\r
- <li>\r
- <b>Nucleus v0.92 (September 18, 2001)</b>\r
- <ul>\r
- <li>GM conversion: {{linkmo and {{emailmo conversion now also works with PHP versions < 4.0.4</li>\r
- <li>GM conversion: Fixed occasional JavaScript errors with {{linkmo and {{emailmo</li>\r
- <li>GM conversion: Fixed [read more] bug</li>\r
- <li>GM conversion: Extra intelligence in choosing URL or e-mail to save as userid for comments</li>\r
- <li>Added: ?archivelist can now be used without arguments to show the list of archives for the default weblog</li>\r
- <li>Fixed: Editing comments now does not allow the use of HTML anymore. The same checks as when adding new comments are performed on update attempts.</li>\r
- <li>Added: check to find out if update file is writable (on changing blogsettings and creating new weblog)</li>\r
- <li>Changed: hard returns in add item now get converted to line breaks (<br />), Also, modified javascript code that handles preview to behave in the same way.</li>\r
- <li>Changed: <%commentform%> does not show user and userid fields for logged in users. Instead, it shows the name of the user.</li>\r
- <li>GM Conversion: {{popup command now also translated (will be converted into a link to the image, not into a popup window!)</li>\r
- <li>Updated: default templates (?archivelist)</li>\r
- <li>Changed: E-mail Address Validation Check</li>\r
- </ul>\r
- </li>\r
- <li>\r
- <b>Nucleus v0.91 (September 15, 2001)</b>\r
- <ul>\r
- <li>Improved conversion for GreyMatter blogs. Special markup commands are now recognized. (thanks to <a href="http://www.elrado.nl/">Raoul</a> for pointing this out)</li>\r
- </ul>\r
- </li>\r
- <li>\r
- <b>Nucleus v0.90 [beta 2 release] (September 14, 2001)</b>\r
- <ul>\r
- <li>an install-script is now available, no more messing around in shells</li>\r
- <li>created default skins/templates for a release version</li>\r
- <li>option to store 'last visit' cookie and to use 'new' indication on items</li>\r
- <li>?archivelist=.. request can now also be used with a blogid instead of a blog shortname</li>\r
- <li>forgotten password reminder</li>\r
- <li>Bookmarklet can be used without being logged in. A login prompt is shown in that case.</li>\r
- <li>When not being logged in to the admin area, requested actions are now completed after passing login information. Before, you would always end up at the action overview after passing login information, and your requested action would have gone lost.</li>\r
- <li>Super-admins now have access to all blogs, even if they are not on the team</li>\r
- <li>Logtext passed to bookmarklet now gets <br /> added before each newline</li>\r
- <li>Added little JavaScript to prevent submitting form data twice</li>\r
- <li>Sample plugin: google referer check</li>\r
- <li>Conversion script to import GreyMatter blogs included</li>\r
- <li>Removed 'assign comment to member' feature</li>\r
- <li>Added toolbar to popup help windows (because of the back/forward buttons)</li>\r
- <li>Added <%blogurl%> variable for item templates</li>\r
- <li>bug-fixes</li>\r
- <li>small esthetic changes</li>\r
- <li>...</li>\r
- </ul>\r
- </li>\r
- <li>\r
- <b>Nucleus v0.80 [beta 1 release] (September 2, 2001)</b>\r
- <ul>\r
- <li>XML-RPC Interface implementing the blogger methods</li>\r
- <li>fixes and code-reorganisation</li>\r
- <li>popup-help on item pages</li>\r
- <li>bookmarklets/right click blogging</li>\r
- <li>the start of something that looks like documentation</li>\r
- </ul>\r
- </li>\r
- <li>\r
- <b>Nucleus v0.70 [not released] (August 20, 2001)</b>\r
- <ul>\r
- <li>mySQL instead of XML</li>\r
- <li>extensive admin area</li>\r
- <li>'member' concept, including blog teams/admins/...</li>\r
- <li>rewrote most of the code</li>\r
- <li>skin format slightly changed</li>\r
- <li>almost ready for public release :)</li>\r
- <li>adding items with instant preview (when viewing the weblog)</li>\r
- <li>LOCALE used for time/date notations.</li>\r
- </ul>\r
- </li>\r
- <li>\r
- <b>Nucleus v0.60 and earlier (since February 2001)</b>\r
- <br />\r
- no history (XML versions with limited functions)\r
- </li>\r
-</ul>\r
-\r
-\r
-</body>\r
-</html>\r
+++ /dev/null
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">\r
-<html xmlns="http://www.w3.org/1999/xhtml">\r
-<head>\r
- <!-- $Id: index.html,v 1.4 2005-03-19 07:28:32 kimitake Exp $ -->\r
- <title>Nucleus CMS - Manual</title>\r
- <link rel="stylesheet" type="text/css" href="styles/manual.css" />\r
-</head>\r
-<body>\r
-\r
-<div class="heading">\r
-Nucleus CMS Manual\r
-<i>(v3.2)</i>\r
-</div>\r
-\r
-<div class="note">\r
-<b>Notes:</b>\r
-<ul>\r
- <li>This manual only contains information that is not already contained in the popup-help (<a href="help.html">help.html</a>) available from the administration area. This document also contains instruction for the <a href="#installation">installation</a> of Nucleus.</li>\r
- <li>If you're a developer, <a href="devdocs/index.html">extra developer documentation</a> is available.</li>\r
-</ul>\r
-</div>\r
-\r
-<h1><a name="toc"></a>Table Of Contents</h1>\r
-\r
-<ul>\r
- <li><a href="#about">About Nucleus CMS</a></li>\r
- <li><a href="#license">License: GPL</a></li>\r
- <li><a href="#installation">Installation</a></li>\r
- <li><a href="skins.html">Modifying skins and templates</a> (separate file)</li>\r
- <li><a href="#security">Security Aspects</a></li>\r
- <li><a href="#performance">Performance Aspects</a></li>\r
-<!-- <li><a href="#import">Importing from other tools</a></li> -->\r
- <li><a href="#comments">What's allowed/disallowed in comments?</a></li>\r
- <li><a href="#xmlrpc">XML-RPC Interface</a></li>\r
- <li><a href="#trouble">Troubleshooting (FAQ)</a></li>\r
- <li><a href="tips.html">Tips & Suggestions</a> (separate file)</li>\r
- <li><a href="#known">Known Problems</a></li>\r
- <li><a href="history.html">Version History</a> (separate file)</li>\r
- <li><a href="#credits">Credits & Thanks</a></li>\r
-</ul>\r
-\r
-<h1>About Nucleus <a name="about" href="#top" class="toplink"><img src="icon-up.gif" width="15" height="15" alt="back to top" /></a></h1>\r
-\r
-<p>\r
-Nucleus is a Content Management System (CMS): a powerful set of PHP scripts that allow you to maintain one or more weblogs or online journals. A short summary of the most important features is given below:\r
-</p>\r
-\r
-<ul>\r
- <li>Runs on your own server</li>\r
- <li>One or more weblogs, even on the same page</li>\r
- <li>Plugin-interface to add extra functionality</li>\r
- <li>Comments</li>\r
- <li>Archives</li>\r
- <li>Categories</li>\r
- <li>Search</li>\r
- <li>Multiple authors</li>\r
- <li>Future items</li>\r
- <li>Drafts</li>\r
- <li>Extensive administration area</li>\r
- <li>Media library and file upload</li>\r
- <li>Fully customizable skins and templates</li>\r
- <li>Skin import/export</li>\r
- <li>Banlist against commenting system abuse</li>\r
- <li>RSS syndication</li>\r
- <li>Easy installation</li>\r
- <li>Easy backups</li>\r
- <li>XML-RPC interface (implementing the <a href="http://plant.blogger.com/api/">Blogger API</a> and <a href="http://www.xmlrpc.com/metaWeblogApi">metaWeblog API</a>)</li>\r
- <li>XHTML-ready</li>\r
- <li>Tools to import Blogger and GreyMatter blogs</li>\r
- <li>...</li>\r
-</ul>\r
-\r
-<p>\r
-Requirements in order to run Nucleus: <small>(If you don't know if you fit the requirements, ask your system administrator)</small>\r
-</p>\r
-\r
-<ul>\r
- <li><a href="http://www.php.net/">PHP</a> (version 4.0.6 or higher)</li>\r
- <li>Access to a <a href="http://www.mysql.com/">MySQL</a> database (version 3.23.38 or higher)</li>\r
- <li>Some <acronym title="Hypertext Markup Language">HTML</acronym> and <acronym title="Cascading Style Sheets">CSS</acronym> knowledge, to edit skins and templates</li>\r
-</ul>\r
-\r
-\r
-\r
-<p>\r
-Nucleus is intended for the people that want full control and 'tweakability' over their sites. If you're just looking for a very simple way to put up a site, or don't know any HTML, you might want to use a 'simpler' service such as <a href="http://www.blogger.com/">Blogger</a>.\r
-</p>\r
-\r
-\r
-\r
-\r
-<a name="license"></a>\r
-<h1>License <a name="copyright" href="#top" class="toplink"><img src="icon-up.gif" width="15" height="15" alt="back to top" /></a></h1>\r
-\r
-<p>\r
-Nucleus: PHP/MySQL Weblog CMS (http://nucleuscms.org/)\r
-<br />\r
-Copyright (C) 2002-2005 The Nucleus Group\r
-</p>\r
-\r
-<p>This program is free software; you can redistribute it and/or\r
-modify it under the terms of the GNU General Public License\r
-as published by the Free Software Foundation; either version 2\r
-of the License, or (at your option) any later version.</p>\r
-\r
-<p>This program is distributed in the hope that it will be useful,\r
-but WITHOUT ANY WARRANTY; without even the implied warranty of\r
-MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\r
-GNU General Public License for more details.</p>\r
-\r
-<p>You should have received a <a href="../../license.txt">copy of the GNU General Public License</a>\r
-along with this program; if not, write to the Free Software\r
-Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.</p>\r
-\r
-<p>\r
-Your possession of this software signifies that you agree to these terms. Please delete your copy of this software if you don't agree to these terms.\r
-</p>\r
-\r
-\r
-<h1>Installation <a name="installation" href="#top" class="toplink"><img src="icon-up.gif" width="15" height="15" alt="back to top" /></a></h1>\r
-\r
-<div class="note">\r
-<b>Note:</b> If you are upgrading, you should see the <a href="http://www.nucleuscms.org/upgrade.php">upgrade instructions</a> on the Nucleus website.\r
-</div>\r
-\r
-<p>\r
-Installing Nucleus is done through some steps:\r
-</p>\r
-\r
-<h2>1. Unzip</h2>\r
-\r
-<p>\r
-Unzip all files to a directory of your computer. Make sure the path names are used when unzipping. You should end up with the following directory structure (* stands for a number of files):\r
-</p>\r
-\r
-<pre>\r
-/* (main files for site)\r
-/nucleus/* (main files for admin-area)\r
-/nucleus/javascript/* (javascript helper scripts)\r
-/nucleus/libs/* (Nucleus core libs)\r
-/nucleus/language/* (definitions of languages)\r
-/nucleus/plugins/* (plugin-dir)\r
-/nucleus/xmlrpc/* (XML-RPC interface)\r
-/nucleus/documentation/* (Documentation + admin-area help)\r
-/nucleus/styles/* (stylesheets for docs & admin-area)\r
-/nucleus/forms/* (skeletons for commentforms etc)\r
-/extra/* (extra goodies, e.g. needed files to enable fancy URLs)\r
-/skins/* (skins directory [imported skins will go here])\r
-/media/* (media library directory [emtpy])\r
-</pre>\r
-\r
-\r
-<h2>2. Upload files</h2>\r
-\r
-<p>\r
-Upload all files to your server, using your favorite FTP program. Make sure to upload .php files in ASCII mode! It might not work otherwise.\r
-</p>\r
-\r
-<h3>Optional:</h3>\r
-\r
-<ol>\r
- <li>\r
- To make your install process even easier, you can change the file permissions on <em>config.php</em> to <strong>666</strong>. This way, the install script will be able to update it automatically instead of you having it to do manually. (<a href="tips.html#filepermissions">Quick guide on how to change file permissions</a>)\r
- </li>\r
- <li>\r
- If you want to use file upload, you'll need to add write permissions to the /media/ directory. This is needed in order to allow PHP to write uploaded files into that directory. The directory should be <i>chmod</i>ded to <strong>777</strong> (<a href="tips.html#filepermissions">Quick guide on how to change file permissions</a>). (If you have root access, you can instead <tt>chgrp</tt> the directory to the user that is running the <tt>httpd</tt> process (usually <tt>httpd</tt> or <tt>nobody</tt>, then <tt>chmod 775</tt> the directory).\r
- </li>\r
- <li>\r
- If you want to use the SkinFiles plugin to edit files, you'll need to change the permissions on all files and directories under the /skins/ directory. To be able to edit files, they should be <i>chmod</i>ded to <strong>666</strong> (<a href="tips.html#filepermissions">Quick guide on how to change file permissions</a>). To be able to create new files or directories, the parent directory should be <i>chmod</i>ded to <strong>777</strong>.\r
- </li>\r
-</ol>\r
-\r
-\r
-<h2>3. Run install.php</h2>\r
-\r
-<p>\r
-Open your web browser open the URL below, where you adapt the <i>yoursite</i> and <i>yourpath</i> parts.\r
-</p>\r
-\r
-<pre>\r
-http://www.yoursite.com/yourpath/install.php\r
-</pre>\r
-\r
-<p>\r
-This install-script will prompt you for some information, and perform most of the installation for you. When everything has succeeded, <i>install.php</i> will provide you with further instructions. (you'll still need to delete some files manually)\r
-</p>\r
-\r
-<div class="note">\r
-<b>Note:</b> When you open <i>install.php</i> in your browser and you see the text "If you see this text in your browser...", or you are prompted to download 'install.php', then your web server does not support PHP, and you won't be able to run Nucleus there.\r
-</div>\r
-\r
-<h2>4. Done!</h2>\r
-\r
-<p>\r
-You should now be able to visit your site at http://yoursite.com/weblog/ (or whatever URL maps to the location where you uploaded the Nucleus site main files)\r
-</p>\r
-\r
-\r
-\r
-\r
-\r
-\r
-\r
-<h1>Security Aspects <a name="security" href="#top" class="toplink"><img src="icon-up.gif" width="15" height="15" alt="back to top" /></a></h1>\r
-\r
-<h2>mySQL passwords</h2>\r
-\r
-<p>\r
-Since Nucleus needs to connect to a mySQL database from a PHP-script, the password for that database must be stored inside a PHP-file. On multi-user systems, this might cause an unevitable security risk: On some systems, other users will be able to read your login information. You might want to contact your system operator to find out how secure it is to store sensible information inside PHP-scripts.\r
-</p>\r
-\r
-<p>\r
-The problem above is common to all PHP scripts that need to connect to a database. As a user, there's usually nothing you can do about it in order to make things 100% secure. We just want you to be aware of this potential danger.\r
-</p>\r
-\r
-<h2>Cookies</h2>\r
-\r
-<p>\r
-Nucleus uses cookies to store user login information. This could cause a security risk when your cookies are stolen. Although your password is not derivable from the cookie <small>(the values stored in the cookie are the username and a randomly generated string)</small>, there could be ways to 'fake' the cookie on another computer and thus to get logged in.\r
-</p>\r
-\r
-<h2>Media dir</h2>\r
-\r
-<p>\r
-When you want to enable file upload, you'll need to set the permissions of the media dir to 777, which means that <b>everyone</b> on that server will be able to delete/add/... files. The reason why this is needed, is that PHP mostly runs as the httpd user, and that user needs to be able to access this dir and write to it. Here also, there's no way around this.\r
-</p>\r
-\r
-\r
-\r
-\r
-\r
-<h1>Performance Aspects <a name="performance" href="#top" class="toplink"><img src="icon-up.gif" width="15" height="15" alt="back to top" /></a></h1>\r
-\r
-<p>\r
-Contradictory to some other weblog/online journal scripts, Nucleus does not generate a static version of all items. This means that every time a page is requested, the PHP parser is called and the database is accessed to dynamically create the requested page.\r
-</p>\r
-\r
-<p>\r
-For small web sites, this should not cause any problem. For web sites that get dozens of hits per second, the effect on the systems performance isn't really known. So far, no problems have been reported by Nucleus users (some are running pretty big sites on it, with 30 or more weblogs on a single installation).\r
-</p>\r
-\r
-\r
-\r
-\r
-<!--\r
-<h1>Importing From Other Tools <a name="import" href="#top" class="toplink"><img src="icon-up.gif" width="15" height="15" alt="back to top" /></a></h1>\r
-\r
-<p>\r
-Nucleus contains some conversion scripts that allow you to import the data from your 'old' weblog tool into your Nucleus weblog. No data is destroyed during this process.\r
-</p>\r
-\r
-<p>\r
-More information is available on the <a href="http://www.nucleuscms.org/convert.php">Nucleus website</a>. At the time of release, the only available conversion tools are those for Blogger and GreyMatter blogs.\r
-</p>\r
--->\r
-\r
-\r
-<h1>What's allowed/disallowed in comments? <a name="comments" href="#top" class="toplink"><img src="icon-up.gif" width="15" height="15" alt="back to top" /></a></h1>\r
-\r
-<p>\r
-Nucleus has some built-in rules concerning comments:\r
-</p>\r
-\r
-<ul>\r
- <li>words longer than 90 characters are not allowed (why: layout might get messed up when people do that) </li>\r
- <li>the actual comment should be at least 3 characters long</li>\r
- <li>comments cannot be longer than 5000 characters </li>\r
- <li>guests need to enter a username of at least 2 characters </li>\r
- <li>guests cannot use quotes or newlines in username/email </li>\r
- <li>each sequence of 3 newlines in the body gets replaced by a single newline (why: layout)</li>\r
- <li>HTML tags are replaced by entities</li>\r
- <li>the comment is trimmed (leading and trailing whitespace is left of)</li>\r
- <li>URLs are 'hreffed'. To avoid layout mess-ups, the URLs are shortened.</li>\r
-</ul>\r
-\r
-<p>\r
-As for now, all of these rules and parameters are hardwired into the code.\r
-</p>\r
-\r
-\r
-\r
-\r
-\r
-\r
-<h1>XML-RPC Interface <a name="xmlrpc" href="#top" class="toplink"><img src="icon-up.gif" width="15" height="15" alt="back to top" /></a></h1>\r
-\r
-<div class="note">\r
-The URL for the Nucleus XML-RPC interface is:\r
-<br />\r
-<b>http://www.yourserver.com/yourpath/nucleus/xmlrpc/server.php</b>\r
-</div>\r
-\r
-<p>\r
-<a href="http://www.xmlrpc.com/">XML-RPC</a> is a format for remote calls using XML messages. Sounds complex, but implementing an XML-RPC interface into an application allows other services to communicate with it.\r
-</p>\r
-\r
-<p>\r
-Currently, there are three APIs supported: the <a href="http://plant.blogger.com/api/">Blogger API</a>, the <a href="http://www.xmlrpc.com/metaWeblogApi">metaWeblog API</a>, and the <a href="http://www.movabletype.org/docs/mtmanual_programmatic.html#xmlrpc%20api">Movable Type API</a>. If you want an examples of a client that uses these interfaces, try <a href="http://www.wbloggar.com/">w.Bloggar</a> (Windows) or <a href="http://www.kung-foo.tv/ecto/">Ecto</a> (MacOS).\r
-</p>\r
-\r
-<p>\r
-The available calls to the interface are described in the development documentation, which can be <a href="http://nucleuscms.org/download.php">separately downloaded</a>, or <a href="http://nucleuscms.org/documentation/devdocs/xmlrpc.html">viewed online</a>.\r
-</p>\r
-\r
-\r
-\r
-<h1>Troubleshooting (FAQ) <a name="trouble" href="#top" class="toplink"><img src="icon-up.gif" width="15" height="15" alt="back to top" /></a></h1>\r
-\r
-<p>Below, some of the most common problems with and questions about Nucleus are answered. Please read these first before you ask for help. In many cases, the solution can be found here.\r
-</p>\r
-\r
-<div class="faq">\r
-<div class="question">I get an error: <q>Cannot send headers. Headers already sent...</q></div>\r
-<div class="answer">\r
-This problem is usually caused by whitespace at the beginning or end of <code>config.php</code>. Check if it has spaces or newlines before the starting <tt><?</tt> or after the ending <tt>?></tt>. If there are, remove them. The problem can also have to do with spaces in the language file or one of the installed plugins.\r
-</div>\r
-</div>\r
-\r
-<div class="faq">\r
-<div class="question">When I try to run install.php, I'm prompted if I want to download install.php</div>\r
-<div class="answer">Your web server is not set up to support PHP scripts. You won't be able to install Nucleus on such a system.</div>\r
-</div>\r
-\r
-<div class="faq">\r
-<div class="question">When I try to visit my website, I get a 'Connection Error'. Why?</div>\r
-<div class="answer">\r
-The reason why this error is shown is that Nucleus cannot connect to your database server for one reason or another, or it cannot select the database. One possible reason is that your login information in <i>config.php</i> is incorrect. Another is that the mySQL server is down.\r
-</div>\r
-</div>\r
-\r
-<div class="faq">\r
-<div class="question">I can't get my update file to work!</div>\r
-<div class="answer">\r
-File permissions need to be set correctly in order for the update file to work. The update file also needs to exist prior to changing the blogsettings. (e.g. you can create an empty file and upload it). About the file permissions, make sure the update file is <i>chmod</i>ded to 666 and the directories are <i>chmod</i>ded to 755. (<a href="tips.html#filepermissions">Quick guide on changing file permissions</a>)\r
-</div>\r
-</div>\r
-\r
-<div class="faq">\r
-<div class="question">I don't want the XML-RPC interface to be available</div>\r
-<div class="answer">You can simply delete the xmlrpc/ directory without causing trouble.</div>\r
-</div>\r
-\r
-<div class="faq">\r
-<div class="question">I don't want RSS syndication (headlines) to be available</div>\r
-<div class="answer">You can safely delete the xml-rss.php (headlines.php) file and the 'xmlrss' (headlines) skin/template</div>\r
-</div>\r
-\r
-\r
-<h1>Known Problems <a name="known" href="#top" class="toplink"><img src="icon-up.gif" width="15" height="15" alt="back to top" /></a></h1>\r
-\r
-<p>Some known issues/bugs:\r
-</p>\r
-\r
-<ul>\r
- <li>At the time of release, there are officially supported blog conversion tools available for Nucleus v3.0. We do have a set of code with which you can start, and are providing <a href="http://nucleuscms.org/convert.php">pointers to the import tools created by others</a>.</li>\r
- <li>Ctrl + Shift + A shortcut might conflict with ICQ/Trillian</li>\r
- <li>When PHP is running in SAFE mode, it's very likely that there will be problems when using the media directory (Nucleus will not be able to automatically detect image sizes, or disallow uploading)</li>\r
- <li>Entities can get messed up in the RSS channel (e.g. &amp; becomes &amp;amp;)</li>\r
- <li>The notify-address option in blogsettings has a preset limit of 255 chars, which means you can't put too many e-mail addresses in there.</li>\r
- <li>Live preview doesn't work correctly in Mozilla</li>\r
- <li>Internet Explorer 6 seems to be occasionally closing itsself after adding an item. The item is added, though. (it's been a while since the last complaint about that, so it <em>might</em> have disappeared)</li>\r
-</ul>\r
-\r
-\r
-\r
-<h1>Credits & Thanks <a name="credits" href="#top" class="toplink"><img src="icon-up.gif" width="15" height="15" alt="back to top" /></a></h1>\r
-\r
-<p>No matter how hard we try, some people will be unintentionally overlooked in this section.</p>\r
-\r
-<h2>Founder</h2>\r
-\r
-<ul>\r
- <li>Wouter Demuynck</li>\r
-</ul>\r
-\r
-<h2>Code submissions</h2>\r
-\r
-<ul>\r
- <li>Jeroen Budts</li>\r
- <li>Edmond Hui</li>\r
- <li>Appie Verschoor (Fulltext search)</li>\r
- <li>Many others... (check the <a href="history.html">history</a>)</li>\r
-</ul>\r
-\r
-<h2>Libraries etc</h2>\r
-\r
-<ul>\r
- <li>Jeff MacMichael (NP_SkinFiles plugin)</li>\r
- <li>Ivan Fong, Roel, Moraes, Hcgtv (Nucleus 3.2 default skin)</li>\r
- <li>Plugins are written by their respective authors.</li>\r
- <li>Thanks should go out to the people that wrote language-files for Nucleus. You can <a href="http://nucleuscms.org/languages.php">download extra language files on the Nucleus website</a>.</li>\r
- <li>The logo (the one with the yellow rays) was created by Rodrigo Moraes</li>\r
- <li>The RSS 2.0 skin was created by <a href="http://www.xiffy.nl">Xiffy</a></li>\r
- <li>The XML-RPC interface uses the <a href="http://phpxmlrpc.sourceforge.net/">'XML-RPC for PHP'</a> implementation from <a href="http://www.usefulinc.com/">Useful Inc.</a>.</li>\r
- <li>The backup/restore code is largely inspired on the code used in <a href="http://phpbb.sourceforge.net/">phpBB</a>. </li>\r
- <li>The JavaScript code used for the instant preview was originally inspired on the code used by <a href="http://www.mijnkopthee.nl/">Mijn Kop Thee</a> <small>(dutch)</small> and <a href="http://www.milov.nl/">milov.nl</a>.</li>\r
- <li>The globe bullet next to links in the admin screen, comes from <a href="http://www.matterform.com/qbullets/legend.html">QBullets</a></li>\r
-</ul>\r
-\r
-<h2>Thanks!</h2>\r
-\r
-<p>\r
-Many thanks should also go to all people who have helped Nucleus to become what it is today.</p>\r
-\r
-<ul>\r
- <li>A list of <a href="http://nucleuscms.org/donators.php">donators</a> is available on the Nucleus website.</li>\r
- <li>Special thanks to the <a href="http://forum.nucleuscms.org/groupcp.php?g=3">forum moderators</a> and <a href="http://forum.nucleuscms.org/memberlist.php?mode=posts&order=DESC">frequent forum visitors</a>.</li>\r
-</ul>\r
-\r
-\r
-\r
-</body>\r
-</html>
\ No newline at end of file
+++ /dev/null
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">\r
-<html xml:lang="en" xmlns="http://www.w3.org/1999/xhtml">\r
-<head>\r
- <!-- $Id: skins.html,v 1.4 2005-03-19 07:28:32 kimitake Exp $ -->\r
- <title>Nucleus - Skins and Templates</title>\r
- <link rel="stylesheet" type="text/css" href="styles/manual.css" />\r
-</head>\r
-<body>\r
-\r
-<div class="heading">\r
-Skins & Templates\r
-</div>\r
-\r
-<h1>Introduction</h1>\r
-\r
-<p>\r
-<a href="index.html">Back to the manual</a>\r
-</p>\r
-\r
-<p>So, you've installed Nucleus... You've got several options now concerning the look of your site:</p>\r
-<ol>\r
- <li>Go with the default skin/templates that comes with Nucleus</li>\r
- <li>Start from the default skin/templates, and modify it to your needs (colors, etc...)</li>\r
- <li>Start your own skin/templates, and define your own CSS stylesheets</li>\r
-</ol>\r
-<p>This document tries to help you with doing this.</p>\r
-\r
-<h1><a id="toc"></a>Table Of Contents</h1>\r
-\r
-<ul>\r
- <li><a href="#htmlcss">HTML and CSS</a></li>\r
- <li><a href="#defaultskin">The default skin</a></li>\r
- <li><a href="#templatesvsskins">Templates vs. Skins</a></li>\r
- <li><a href="#skincascade">How skins are chosen</a></li>\r
- <li>Howto:\r
- <ul>\r
- <li><a href="#howto-additem">An 'add item' form on your website</a></li>\r
- <li><a href="#howto-cssforms">Using CSS to define the look of forms</a></li>\r
- <li><a href="#howto-karma">Enabling karma votes</a></li>\r
- <li><a href="#howto-edit">'Edit item'-links</a></li>\r
- </ul>\r
- </li>\r
- <li><a href="#export">Writing skins with Export/Import in mind</a></li>\r
-</ul>\r
-\r
-<h1>HTML and CSS <a id="htmlcss" href="#top" class="toplink"><img src="icon-up.gif" width="15" height="15" alt="back to top" /></a></h1>\r
-\r
-<p>\r
-When editing skins and templates, you'll need at least some basic knowledge about HTML and CSS. This section provides some pointers to online tutorials and references:\r
-</p>\r
-\r
-<ul>\r
- <li><a href="http://www.w3schools.com/">W3Schools</a>: online web building tutorials (HTML, XHTML, CSS)</li>\r
- <li><a href="http://thenoodleincident.com/tutorials/css/">CSS Panic Guide</a>: links to various CSS resources</li>\r
- <li><a href="http://hotwired.lycos.com/webmonkey/authoring/html_basics/index.html">Webmonkey: HTML Basics</a></li>\r
- <li><a href="http://hotwired.lycos.com/webmonkey/authoring/stylesheets/">Webmonkey: Stylesheets</a></li>\r
- <li><a href="http://diveintoaccessibility.org">Dive Into Accessibility</a>: Online book, not really about HTML, but about accessibility and how to make your site more accessible.</li>\r
-</ul>\r
-\r
-\r
-\r
-\r
-\r
-\r
-\r
-<h1>The default skin <a id="defaultskin" href="#top" class="toplink"><img src="icon-up.gif" width="15" height="15" alt="back to top" /></a></h1>\r
-\r
-<p>This section briefly explains which files are used by the default skin, and how you can edit them.</p>\r
-\r
-<p>The default skin uses three files:</p>\r
-<ol>\r
- <li><tt>default.css</tt>: CSS stylesheet that defines the page style. Colors, layout etc. are defined in this file</li>\r
- <li><tt>atom.gif</tt>: The logo that appears in the upper left corner of the screen</li>\r
- <li><tt>nucleus2.gif</tt>: Nucleus logo</li>\r
-</ol>\r
-\r
-<p>The CSS file <tt>default.css</tt> contains extra information about how pages are built up by the default skins and templates. Basically, it comes down to three <tt>div</tt>-containers: <tt>.contents</tt>, <tt>.logo</tt> and <tt>.menu</tt></p>\r
-\r
-<p>To edit the <tt>default.css</tt> file, you'll need a simple texteditor that does not add extra data, like Notepad (comes with windows),emacs or TextPad. Do <strong>not</strong> use WordPad, Word, OpenOffice Writer, ... since those add extra markup data.</p>\r
-\r
-\r
-\r
-\r
-\r
-\r
-<h1>Templates vs. Skins <a id="templatesvsskins" href="#top" class="toplink"><img src="icon-up.gif" width="15" height="15" alt="back to top" /></a></h1>\r
-\r
-<p>\r
-In Nucleus, both templates and skins are used to determine the way your blog looks. So, what is the difference between these two?\r
-</p>\r
-\r
-<ol>\r
- <li>\r
- <b>Skins</b> define how your sites look. Each skin consists of several types: one for the main index, one for the detailed item pages, one for the archive, ...\r
- The skins also contain instructions of where to include a weblog, and which template should be used to do so.\r
- </li>\r
- <li>\r
- Ha! This means <b>templates</b> are used to define the way the weblog block in your page looks like. The reason why templates aren't included in the skins themselves, is that several skins can use the same template to display a blog.\r
- </li>\r
-</ol>\r
-\r
-<p>An example is given in the image below. The whole page is defined by a skin, while the parts in the red rectangles (category list and blog contents) are formatted according to the templates. It's the skin that defines where the red rectangles will appear.</p>\r
-\r
-<div class="screenshot">\r
-<img src="pics/skinsandtemplates.png" width="300" height="283" alt="Skins and Templates example" />\r
-</div>\r
-\r
-\r
-\r
-\r
-\r
-\r
-\r
-\r
-\r
-<h1>How skins are chosen <a id="skincascade" href="#top" class="toplink"><img src="icon-up.gif" width="15" height="15" alt="back to top" /></a></h1>\r
-\r
-<p>\r
-This section tries to explain how Nucleus chooses the skin to use when you request a page.\r
-</p>\r
-\r
-<h2>Skin Types</h2>\r
-\r
-<p>\r
-First of all, there are several skin types between which Nucleus makes a choice according to the request URL: see the list below. This should be very obvious.\r
-</p>\r
-\r
-<table>\r
- <tr><th>Query String Format</th><th>Which skin type?</th><th>Which weblog is shown?</th></tr>\r
- <tr><td>?itemid=..</td><td>item</td><td>Deducted from <i>itemid</i></td></tr>\r
- <tr><td>?archive=..</td><td>archive</td><td>Default weblog, or <i>blogid</i> attribute</td></tr>\r
- <tr><td>?archivelist=...</td><td>archivelist</td><td><i>archivelist</i>-attribute</td></tr>\r
- <tr><td>?archivelist</td><td>archivelist</td><td>Default weblog</td></tr>\r
- <tr><td>?query=...</td><td>search</td><td>Default weblog, or <i>blogid</i> attribute</td></tr>\r
- <tr><td>?memberid=..</td><td>member</td><td>None</td></tr>\r
- <tr><td>?imagepopup=..</td><td>imagepopup</td><td>None (popup window with image)</td></tr>\r
- <tr><td><i>(other or empty)</i></td><td>index</td><td>Default weblog, or <i>blogid</i> attribute</td\r
- ></tr>\r
-</table>\r
-\r
-<p>\r
-Next to these 7 types, there is an <i>error</i> type, which is used when errors occur.\r
-</p>\r
-\r
-<h2>The Skin Cascade</h2>\r
-\r
-<p>\r
-The table above also indicates how the blog to be displayed is chosen. The skin that will be used, is the default skin for that weblog, as selected in the settings for that weblog.\r
-</p>\r
-\r
-<p>\r
-Not every skin needs to have definitions for all skin parts. When a part is missing, the skin called 'default' will be used instead (see below). This allows you for example to only create one error page and one member page.\r
-</p>\r
-\r
-<h2>The 'default' Skin</h2>\r
-\r
-<p>\r
-Nucleus requires that at all times there exists a skin called '<b>default</b>'. This is the skin to which is backed up when a skinpart is missing. If the same skinpart is also missing from the 'default' skin, the error message 'no appropriate skin found' will be shown.\r
-</p>\r
-\r
-<p>\r
-Another reason why the 'default' skin is required, is to be able to display error messages when no blog is selected (e.g. the 'no such blog' error)\r
-</p>\r
-\r
-\r
-\r
-\r
-\r
-\r
-\r
-\r
-<h1>Howto: An 'add item' form on your website <a id="howto-additem" href="#top" class="toplink"><img src="icon-up.gif" width="15" height="15" alt="back to top" /></a></h1>\r
-\r
-<p>\r
-Nucleus provides facilities to add an 'add item' form to your weblog. It adds an 'add item' link that shows and hides the 'add item' form right above the current contents of your weblog. Entering text in this form results into an instant preview, so you can immediately see how the actual weblog item will look like.\r
-</p>\r
-\r
-<p>\r
-All modifications below apply to the <b>skin</b> for the <b>main index</b> page. You don't need to alter any templates.\r
-</p>\r
-\r
-<h2>1. JavaScript code</h2>\r
-<p>\r
-First of all, you need to include the edit.js Javascript code by putting the following line somewhere in between the <head> and </head> tags. This file contains the functions that are needed to make the preview work and to hide/show the 'add item' form.\r
-</p>\r
-\r
-<pre>\r
-<script type="text/javascript"\r
- src="nucleus/javascript/edit.js"></script>\r
-</pre>\r
-\r
-<h2>2. Indicate where the form will show up</h2>\r
-\r
-<p>\r
-The, you add a logical container somewhere on your page, where you want to have the 'add item' form. The "display:none;" makes sure it is hidden.\r
-</p>\r
-\r
-<pre>\r
-<div id="edit" style="display:none;">\r
-...\r
-</div>\r
-</pre>\r
-\r
-<h2>3. Code that inserts the form and preview</h2>\r
-\r
-<p>\r
-Now, you can add your custom HTML into this container, and use <%additemform%> and <%preview(<i>templatename</i>)%> to insert the 'add item' form and the preview code respectively. An example is given below\r
-</p>\r
-\r
-<pre>\r
-<h2>Add Item</h2>\r
-<%additemform%>\r
-\r
-<h2>Preview</h2>\r
-<%preview(mytemplate)%>\r
-</pre>\r
-\r
-<h2>4. The 'add item'-link</h2>\r
-<p>\r
-And the finishing touch: a link or button to trigger the visibility of the form. Two examples are given. The first one is a simple link:\r
-</p>\r
-\r
-<pre>\r
-<a href="javascript:showedit();">add item</a>\r
-</pre>\r
-\r
-<p>\r
-The second example is a hidden button in the topleft corner\r
-</p>\r
-\r
-<pre>\r
-<div style="position: absolute; left: 0px;\r
- top: 0px; width: 10px; height: 10px"\r
- onclick="javascript:showedit();">\r
-</div>\r
-</pre>\r
-\r
-\r
-\r
-\r
-\r
-\r
-<h1>Howto: CSS to define the look of forms <a id="howto-cssforms" href="#top" class="toplink"><img src="icon-up.gif" width="15" height="15" alt="back to top" /></a></h1>\r
-\r
-<p>\r
-Through variables such as <%searchform%> and <%commentform%>, forms can easily be included into your skin. To allow styles to be applied on those forms, CSS classes have been assigned to the input fields and buttons, and to a surrounding DIV-container.\r
-</p>\r
-\r
-<p>\r
-Below is a list of which CSS class corresponds to which form. These are the classes assigned to the surrounding DIV-container.\r
-</p>\r
-\r
-<table>\r
- <tr>\r
- <th>Form Type</th>\r
- <th>Skin Variable</th>\r
- <th>CSS Class Name</th>\r
- </tr>\r
- <tr>\r
- <td>Add Item to Blog</td>\r
- <td><%additemform%></td>\r
- <td>.blogform</td>\r
- </tr>\r
- <tr>\r
- <td>Add Comment</td>\r
- <td><%commentform%></td>\r
- <td>.commentform</td>\r
- </tr>\r
- <tr>\r
- <td>Login Form</td>\r
- <td><%loginform%></td>\r
- <td>.loginform</td>\r
- </tr>\r
- <tr>\r
- <td>Search Form</td>\r
- <td><%searchform%></td>\r
- <td>.searchform</td>\r
- </tr>\r
- <tr>\r
- <td>Member to Member Mail</td>\r
- <td><%membermailform%></td>\r
- <td>.mailform</td>\r
- </tr>\r
-</table>\r
-\r
-<p>\r
-Below is an overview of the CSS classes assigned to buttons and input fields.\r
-</p>\r
-\r
-<table>\r
- <tr>\r
- <th>Type</th>\r
- <th>CSS Class Name</th>\r
- </tr>\r
- <tr>\r
- <td>Input fields (text and textarea)</td>\r
- <td>.formfield</td>\r
- </tr>\r
- <tr>\r
- <td>Buttons</td>\r
- <td>.formbutton</td>\r
- </tr>\r
-</table>\r
-\r
-<p>\r
-An example of how to use these classes in you stylesheets is given below:\r
-</p>\r
-\r
-<pre>\r
-/* applies to all input fields */\r
-.formfield {\r
- background-color: gray;\r
-}\r
-\r
-/* only applies to buttons for comment forms */\r
-.commentform .formbutton {\r
- border: 1px solid #000;\r
- background-color: #ddd;\r
- color: #000;\r
- font-size: xx-large;\r
-}\r
-</pre>\r
-\r
-<p>In the example above, all formfields that nucleus generates are given a gray background, and the submit button on the comment form has large text, a black 1px border, black text and a light-gray background.</p>\r
-\r
-\r
-<h1>Howto: Enabling karma votes <a id="howto-karma" href="#top" class="toplink"><img src="icon-up.gif" width="15" height="15" alt="back to top" /></a></h1>\r
-\r
-<p>The default skins and templates have karma votes disabled (better: left out). Here's how to add them to your <i>template</i>.</p>\r
-\r
-<h2>1. Open the template for the main index</h2>\r
-\r
-<p>Start editing the template named <tt>'default'</tt> (when starting from the default skins/templates that come with Nucleus)</p>\r
-\r
-<h2>2. Edit the 'Item body' template-part</h2>\r
-\r
-<p>Edit the <i>bottom part</i> of the item body templatepart to be as follows:</p>\r
-\r
-<pre>\r
-<div class="iteminfo">\r
- <%time%> -\r
- <a href="<%authorlink%>"><%author%></a> -\r
- karma: <%karma%>\r
- [<a href="<%karmaposlink%>">+</a>/<a href="<%karmaneglink%>">-</a>] -\r
- <%edit%>\r
- <%comments%>\r
-</div>\r
-</pre>\r
-\r
-<p>On the main page, the iteminfo line for the items will now look like:</p>\r
-\r
-<div><i>9:00:39 PM - <a href="">God</a> - karma: 5 [<a href="">+</a>/<a href="">-</a>] - <a href="">edit</a></i></div>\r
-\r
-<h2>3. Template for the detailed pages</h2>\r
-\r
-<p>At this time, the karma score is only listed on the main page. To make it appear on the detailed page also, the same change needs to be applied to the template with name '<tt>detailed</tt>'</p>\r
-\r
-\r
-\r
-\r
-\r
-\r
-<h1>Howto: 'edit item' links <a id="howto-edit" href="#top" class="toplink"><img src="icon-up.gif" width="15" height="15" alt="back to top" /></a></h1>\r
-\r
-<p>The default Nucleus skin includes 'edit item'-links that are only visible to the author of a item and to the people having the right to alter the item. This section explains which template-parts are needed for this feature to work.</p>\r
-\r
-<h2>'editlink'-template</h2>\r
-\r
-<p>The 'Edit Link'-templatepart defines how an 'edit item'-link is formatted. By default, the contents is:</p>\r
-<pre><code><a href="<%editlink%>" onclick="<%editpopupcode%>">edit</a></code></pre>\r
-\r
-<p>If you would rather edit the item in the admin area, instead of in the popup bookmarklet, use the following code instead:</p>\r
-\r
-<pre><code><a href="nucleus/index.php?action=itemedit&amp;itemid=<%itemid%>">edit</a>\r
-</code></pre>\r
-\r
-<h2>Positioning the edit-link</h2>\r
-\r
-<p>Next to the 'editlink' template, there's the <code><%edit%></code>-templatevar that, when placed somewhere in the 'item body'-templatepart, inserts the editlink.</p>\r
-\r
-<p>See the example from the <a href="#howto-karma">karma votes howto</a> to see an example.</p>\r
-\r
-\r
-\r
-\r
-<h1>Writing skins with Export/Import in mind <a id="export" href="#top" class="toplink"><img src="icon-up.gif" width="15" height="15" alt="back to top" /></a></h1>\r
-\r
-<p>Nucleus v2.0 introduced the ability to import and export skins and templates. This section describes the creation of a simple skin, highlighting the features involved.</p>\r
-\r
-<h2>Creating a new skin</h2>\r
-\r
-<ol>\r
- <li>\r
- <p>First, we're going to create a new skin from the admin area. Browse to <code>Nucleus Management > Edit Skins</code> and scroll to the bottom of the page. Let's call this skin '<strong>vista</strong>'</p>\r
- </li>\r
- <li>\r
- <p>Now look up the 'vista' skin in the skin list and go to the <code>Edit</code> screen. The content type is set to <code>text/html</code>. That's what we want, so no need to change that</p>\r
- <p>The <code>Include Mode</code> and <code>Include Prefix</code> setting reuire more attention. To export a skin, we like to have all files (images, stylesheets, etc...) under one single directory. Remember the <code>$DIR_SKINS</code> setting in <code>config.php</code> and the <code>Skins URL</code> in the general site settings? Suppose these were as follows:</p>\r
- <pre><code>/home/user/example/htdocs/skins/\r
-http://example.org/skins/</code></pre>\r
- <p>Then we would like to put our files in</p>\r
- <pre><code>/home/user/example/htdocs/skins/vista/\r
-http://example.org/skins/vista/</code></pre>\r
- <p>And this is what the <strong><code>Include Mode</code></strong> is for. Setting it to <strong>Use skin dir</strong> will do this.</p>\r
- <p>The <strong><code>Include Prefix</code></strong> also plays a role. This is the <strong>vista/</strong> part</p>\r
- <p>An overview of the correct settings:</p>\r
- <ul>\r
- <li><strong>Name</strong>: vista</li>\r
- <li><strong>Content Type</strong>: text/html</li>\r
- <li><strong>Include Mode</strong>: Use skin dir</li>\r
- <li><strong>Include Prefix</strong>: vista/</li>\r
- </ul>\r
- </li>\r
-</ol>\r
-\r
-<h2>Edit the skin</h2>\r
-\r
-<p>The <code>IncludeMode</code> and <code>IncludePrefix</code> settings will cause the <code>include</code>, <code>phpinclude</code> and <code>parsedinclude</code> skinvars to get their files from the skindir. Next to that, there's the <code>skinfile</code> skinvar, which translates its argument to an URL relative to the skinsdir.</p>\r
-\r
-<p>In our case:</p>\r
-\r
-<pre><code><%skinfile(myFile.jpg)%></code></pre>\r
-\r
-<p>Will get expanded to:</p>\r
-\r
-<pre><code>http://example.org/skins/vista/myFile.jpg</code></pre>\r
-\r
-<p>Lets go easy on ourselves and define the global layout in two files called <code>pagefoot.inc</code> and <code>pagehead.inc</code>, which we place in our <code>vista/</code> directory:</p>\r
-\r
-<h3>pagehead.inc</h3>\r
-\r
-<pre><code><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">\r
-<html xml:lang="en" xmlns="http://www.w3.org/1999/xhtml">\r
-<head>\r
- <title>My Site</title>\r
- <link rel="stylesheet" type="text/css" href="<%skinfile(layout.css)%>" />\r
-</head>\r
-<body>\r
-\r
-<div id="contents"></code></pre>\r
-\r
-<h3>pagefoot.inc</h3>\r
-\r
-<pre><code></div><!-- contents div end -->\r
-\r
-<div id="stuffbar">\r
- <h2>Navigation</h2>\r
-\r
- <ul>\r
- <li><a href="<%todaylink%>">Today</a></li>\r
- <li><a href="<%archivelink%>">Archives</a></li>\r
- </ul>\r
-\r
- <h2>About</h2>\r
-\r
- <ul>\r
- <li><a href="http://www.nucleuscms.org/">Nucleus</a> Power!</li>\r
- </ul>\r
-</div><!-- stuffbar end -->\r
-\r
-</body>\r
-</html></code></pre>\r
-\r
-<p>The contents of the skinparts then becomes kind of trivial: (I'm not defining them all, you'll get the point by seeing the most important ones)</p>\r
-\r
-<h3>Main Index</h3>\r
-<pre><code><%parsedinclude(pagehead.inc)%>\r
-\r
-<h1>My Blog</h1>\r
-\r
-<%blog(vista/main,10)%>\r
-\r
-<%parsedinclude(pagefoot.inc)%></code></pre>\r
-\r
-<h3>Item Pages</h3>\r
-\r
-<pre><code><%parsedinclude(pagehead.inc)%>\r
-\r
-<h1>My Blog</h1>\r
-\r
-<h2>Item</h2>\r
-<%item(vista/detailed)%>\r
-\r
-<h2>Comments</h2>\r
-<%comments(vista/detailed)%>\r
-\r
-<h2>Add Comment</h2>\r
-<%commentform%>\r
-\r
-<%parsedinclude(pagefoot.inc)%></code></pre>\r
-\r
-<p>Note that I named my templates <strong>vista/main</strong> and <strong>vista/detailed</strong>. Makes it easier to see things together six months later. Both templates are actually clones that I made of the <strong>default</strong> and <strong>detailed</strong> templates that come with Nucleus.</p>\r
-\r
-<h3>Archive List</h3>\r
-\r
-<pre><code><%parsedinclude(pagehead.inc)%>\r
-\r
-<h1>My Blog</h1>\r
-\r
-<%archivelist(vista/main)%>\r
-\r
-<%parsedinclude(pagefoot.inc)%></code></pre>\r
-\r
-<h3>Archive</h3>\r
-\r
-<pre><code><%parsedinclude(pagehead.inc)%>\r
-\r
-<h1>My Blog</h1>\r
-\r
-<%archive(vista/main)%>\r
-\r
-<%parsedinclude(pagefoot.inc)%></code></pre>\r
-\r
-<h2>Export the skin</h2>\r
-\r
-<p>When all is done, you can export the skin from the <code>Skin Import/Export</code> page in the admin area. Here's what to do:</p>\r
-\r
-<ol>\r
- <li>Select vista, vista/detailed and vista/main from the skins and template list</li>\r
- <li>Add some textual description and hit the <code>Export selected skins/templates</code> button. It will generate a <code>skinbackup.xml</code> for you.</li>\r
- <li>Save this <code>skinbackup.xml</code> file together with the other files in the <code>vista/</code> directory.</li>\r
- <li>Package all files from the vista directory inside a zipfile</li>\r
- <li>All done! Your skin can now be shared with others</li>\r
-</ol>\r
-\r
-<h2>Importing a skin</h2>\r
-\r
-<p>Importing is the reverse process:</p>\r
-\r
-<ol>\r
- <li>Unzip the zip file under your skins directory, so you end up with a <code>vista/</code> dir (there will be one directory per skin)</li>\r
- <li>From the <code>Skin Import/Export</code> page in the admin area, select <code>vista</code> from the dropdown, and click the <code>Import</code> button.</li>\r
- <li>Follow the instructions</li>\r
- <li>The skin is now installed. It can be selected from the blogsettings.</li>\r
-</ol>\r
-\r
-</body>\r
-</html>
\ No newline at end of file
+++ /dev/null
-body {\r
- background-color: #fff;\r
- color: #000;\r
- font-family: verdana, arial;\r
- font-size: small;\r
-}\r
-\r
-@media screen {\r
- body {\r
- margin-left: 10%;\r
- margin-right: 10%;\r
- }\r
-}\r
-\r
-@media print {\r
- pre, .note, td, th {\r
- border: 1px dashed gray;\r
- }\r
-}\r
-\r
-img {\r
- border: none;\r
-}\r
-\r
-a:link, a:visited {\r
- color: #1D3565; \r
- font-weight: bold;\r
- text-decoration: none;\r
-}\r
-a: hover {\r
- text-decoration: underline;\r
-}\r
-\r
-.heading {\r
- text-align: center;\r
- font-size: xx-large;\r
- font-weight: bold;\r
- color: gray; \r
-}\r
-\r
-.heading i {\r
- position: absolute;\r
- top: 5px;\r
- right: 5px;\r
- font-size: small;\r
- font-style: normal;\r
- font-weight: normal;\r
-}\r
-\r
-\r
-p {\r
- text-indent: 20px;\r
-}\r
-\r
-h1 {\r
- border-bottom: 1px dotted gray;\r
- font-size: x-large;\r
- color: #596d9d;\r
-}\r
-\r
-h2 {\r
- color: gray;\r
- font-size: large;\r
- margin-left: 20px;\r
- text-indent: 10px;\r
- border-bottom: 1px solid #ddd;\r
-}\r
-\r
-pre, .note, .faq .answer {\r
- background-color: #ddd;\r
- padding: 10px;\r
- font-size: small;\r
-}\r
-\r
-.screenshot {\r
- text-align: center;\r
- background-color: #ddd;\r
- padding: 10px;\r
-}\r
-\r
-.faq .question {\r
- font-weight: bold;\r
- margin-bottom: 0px;\r
-}\r
-\r
-.faq .answer {\r
-\r
-}\r
-\r
-.faq {\r
- margin-bottom: 20px;\r
-}\r
-\r
-table {\r
- border: none;\r
-}\r
-\r
-th {\r
- background-color: linen;\r
- font-size: medium;\r
-}\r
-\r
-th, td {\r
- padding: 5px;\r
-}\r
-\r
-td {\r
- background-color: #dddddd;\r
- font-size: small;\r
- vertical-align: top;\r
- text-align: left;\r
-}\r
-\r
-.deprecated {\r
- border: 3px solid red;\r
- padding: 5px;\r
- font-size: medium;\r
-}\r
-\r
-tt, code, samp {\r
- font-size: small;\r
-}\r
-\r
-.warning {\r
- color: red;\r
-}\r
-.ok {\r
- color: green;\r
-}\r
-\r
-acronym, abbr {\r
- border-bottom: 1px dotted gray;\r
- cursor: help;\r
-}\r
-\r
-label {\r
- cursor: hand;\r
-}
\ No newline at end of file
+++ /dev/null
-<!DOCTYPE html\r
-PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"\r
-"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">\r
-<html xmlns="http://www.w3.org/1999/xhtml">\r
-<head>\r
- <!-- $Id: tips.html,v 1.4 2005-03-19 07:28:32 kimitake Exp $ -->\r
- <title>Nucleus - Tips and suggestions</title>\r
- <link rel="stylesheet" type="text/css" href="styles/manual.css" />\r
-</head>\r
-<body>\r
-\r
-<div class="heading">\r
-Tips & Suggestions\r
-</div>\r
-\r
-<h1>Introduction</h1>\r
-\r
-<p>\r
-<a href="index.html">Back to the manual</a>\r
-</p>\r
-\r
-<p>\r
-This file contains tips and suggestions that might prove useful.\r
-</p>\r
-\r
-<h1><a name="toc"></a>Table Of Contents</h1>\r
-\r
-<ul>\r
- <li>\r
- <a href="#searchengines">How to get your archives into search engines?</a>\r
- <ul>\r
- <li><a href="#searchengines-fancyurls">Fancy URLs</a></li>\r
- <li><a href="#searchengines-rewrite">mod_rewrite</a></li>\r
- </ul>\r
- </li>\r
- <li><a href="#filepermissions">How to set file/dir permissions?</a></li>\r
- <li><a href="#backups">How to restore backups</a></li>\r
- <li><a href="#newblog">How to create a new weblogs</a></li>\r
- <li><a href="#xhtml">XHTML support</a></li>\r
-<!--\r
- <li><a href="#"></a></li>\r
- <li><a href="#"></a></li>\r
- <li><a href="#"></a></li>\r
- <li><a href="#"></a></li>\r
--->\r
-</ul>\r
-\r
-\r
-\r
-\r
-\r
-\r
-\r
-\r
-\r
-\r
-<h1>Getting your archives into search engines like Google <a name="searchengines" href="#top" class="toplink"><img src="icon-up.gif" width="15" height="15" alt="back to top" /></a></h1>\r
-\r
-<div class="note">\r
-<b>Note:</b> The solutions described here might not work on your system.\r
-</div>\r
-\r
-<p>\r
-Nucleus creates archives dynamically on users requests. The URL is then of the form <code>index.php?archive=2001-09&blogid=1</code>. Unfortunately, Google and other search engines don't like to index pages with a question mark in it, or with too much arguments. This is because their spiders might get trapped going too deep.\r
-</p>\r
-\r
-<p>Two solutions are listed below. They're not guaranteed to work, however (wether they work or not depends on the webserver configuration)</p>\r
-\r
-<ol>\r
- <li><a href="#searchengines-fancyurls">Fancy URLs</a></li>\r
- <li><a href="#searchengines-rewrite">mod_rewrite</a></li>\r
-</ol>\r
-\r
-<a name="searchengines-fancyurls"></a>\r
-<h2>Fancy URLs</h2>\r
-\r
-<p>Nucleus v2.0 has a new option in the global settings 'URL mode'. Setting it to 'Fancy URL' mode, and performing the steps below, will make your URLs look like <code>http://example.org/item/1234</code> instead of <code>http://example.org/index.php?itemid=1234</code>. Search engines like these URLs better.</p>\r
-\r
-<p>Installation steps:</p>\r
-\r
-<ol>\r
- <li>Copy all files from the <code>/extra/fancyurls</code> directory (except for <code>index.html</code>) to your main nucleus dir (that's where your <code>index.php</code> and <code>action.php</code> file are)</li>\r
- <li>If you have an already existing <code>.htaccess</code> file (most ftp-programs don't show hidden files by default, so don't start uploading it without checking your server). If you do, download that old one first, and copy the contents of the new <code>.htaccess</code> file (from the fancyurls folder) in your old one, and upload that...</li>\r
- <li>Edit the <code>fancyurls.config.php</code> file so that <code>$CONF['Self']</code> points to your main directory. <br /><strong>NOTE: this time, and only this time, the URL should <em>NOT</em> end in a slash</strong></li>\r
- <li>Also edit the <code>$CONF['Self']</code> variable in your <code>index.php</code>, if you don't want to end up with <code>index.php/item/1234</code> urls when people come via that way</li>\r
- <li>Enable 'Fancy URLs' in the Nucleus admin area (nucleus management / edit settings)</li>\r
- <li>Off you go!</li>\r
-</ol>\r
-\r
-<p>When it doesn't work (e.g. you receive an Internal Server Error): bad luck... Remove the files again (don't forget the hidden file <code>.htaccess</code>) and reset the Fancy URLs setting in the admin area.</p>\r
-\r
-\r
-<a name="searchengines-rewrite"></a>\r
-<h2>mod_rewrite</h2>\r
-\r
-<p>\r
-This second possible solution will only work on servers running Apache, and when you have the right to do so. What we will do is 'disguise' the archives as regular HTML pages\r
-</p>\r
-\r
-<p>\r
-Create a file called <code>.htaccess</code> (leading dot!) with the following contents:\r
-</p>\r
-\r
-<pre>\r
-RewriteEngine On\r
-RewriteRule ^archive-([0-9]+)-([0-9]+)-([0-9]+).html+ index.php?archive=$2-$3&blogid=$1\r
-RewriteRule ^item-([0-9]+).html+ index.php?itemid=$1\r
-RewriteRule ^archivelist-([a-z]+).html+ index.php?archivelist=$1\r
-</pre>\r
-\r
-<p>\r
-Now upload this file to the directory that contains <i>index.php</i> and <i>config.php</i>. Open your browser and try to open <code>archive-1-2001-09.html</code>. If it works, continue to read. If you get a 500 error (internal server error), it does not work on your server, so delete the .htaccess file.\r
-</p>\r
-\r
-<p>\r
-Now all you have to do is to update the link to your blog archives into <code>archivelist-<i>shortblogname</i>.html</code> and make the following changes to your archivelist item template:\r
-</p>\r
-\r
-<pre>\r
-<a href="archive-<%blogid%>-<%year%>-<%month%>.html">...</a>\r
-</pre>\r
-\r
-<p>\r
-And now, wait until Google comes spidering again...\r
-</p>\r
-\r
-\r
-<h1>How to set file/dir permissions <a name="filepermissions" href="#top" class="toplink"><img src="icon-up.gif" width="15" height="15" alt="back to top" /></a></h1>\r
-\r
-<p>\r
-To enable some features of Nucleus, changing file permissions is required. A small guide on how to do this using an FTP client is given below.\r
-</p>\r
-\r
-<p>\r
-First of all, you'll need an FTP client that supports file permission changing. In this example, we'll use CuteFTP. You can <a href="http://www.cuteftp.com/products/cuteftp/">download a free trial version</a> if you don't have it.\r
-</p>\r
-\r
-<p>\r
-To change the permissions of a file or directory, create an FTP connection to your website and search for that file or directory in the hierarchy. Select the file by clicking on it.\r
-</p>\r
-\r
-<p>\r
-Open the menu <tt>Commands > File Actions > CHMOD...</tt> for a file, or <tt>Commands > Directory > CHMOD...</tt> for a directory.\r
-</p>\r
-\r
-<div class="screenshot">\r
- <img src="pics/chmod_menu.png" width="381" height="218" alt="menu" />\r
-</div>\r
-\r
-<p>\r
-A window will pop up:\r
-</p>\r
-\r
-<div class="screenshot">\r
- <img src="pics/chmod_window.png" width="260" height="326" alt="The window that pops up" />\r
-</div>\r
-\r
-<p>\r
-On the bottom, you can enter the code that's given in the documentation (e.g. 755 or 444). Click the <tt>OK</tt> button and the changes will be applied. You're finished now.\r
-</p>\r
-\r
-<h1>How to restore backups <a name="backups" href="#top" class="toplink"><img src="icon-up.gif" width="15" height="15" alt="back to top" /></a></h1>\r
-\r
-<p>\r
-Nucleus has a backup/restore option that super-admins can use to create a backup of the database. It's strongly encouraged to take a backup regularly (weekly or so). The backup-files that are returned are files containing standard SQL-queries, that reconstruct the state of the database as it was when the backup was created.\r
-</p>\r
-\r
-<p>\r
-While backing up is easy, and restoring should also be easy, problems might pop up when your database is fucked up beyond repair. In that case, the repair function might become unaccessible. Below are some ways you can restore your database in that case:\r
-</p>\r
-\r
-<div class="note">\r
-If you're backup was gzipped, unzip if first (it contains an sql file)\r
-</div>\r
-\r
-\r
-<h2>Possibility 1: Web-based</h2>\r
-\r
-<p>\r
-If you have a web-based interface through which you can manage your database (e.g. <a href="http://phpmyadmin.sourceforge.net/">PHPMyAdmin</a>), there's most likely an option where you can import a file into the database. Use this function to restore your database.\r
-</p>\r
-\r
-<h2>Possibility 2: Shell-access</h2>\r
-\r
-<p>\r
-If you have a shell account, restoring a backup can be done by running the <tt>mysql</tt> program with the following arguments:\r
-</p>\r
-\r
-<pre>\r
-mysql -u <i>username</i> -p -h <i>hostname</i> <i>databasename</i> < <i>backupfile.sql</i>\r
-</pre>\r
-\r
-\r
-<h1>How to create a new weblog <a name="newblog" href="#top" class="toplink"><img src="icon-up.gif" width="15" height="15" alt="back to top" /></a></h1>\r
-\r
-<h2>1. Creating the weblog</h2>\r
-\r
-<p>As a superadmin, you can create new weblogs from the 'Nucleus Management' screen. They will then show up on the admin area.</p>\r
-\r
-<h2>2. Accessing your new weblog</h2>\r
-\r
-<p>There are several ways in which you can make your new weblog accessible.</p>\r
-\r
-<ol>\r
- <li>Using a <strong><code>blogid</code> attribute</strong> in the URL:\r
- <pre><code>http://yourhost.com/index.php?blogid=<i>2</i></code></pre>\r
- (You can find the blogid in the admin area, when hovering over the blog name in the blog list)\r
- </li>\r
- <li>\r
- By creating a <strong>copy of the <code>index.php</code> file</strong> (in this example, our file is named <tt>copy.php</tt>), and editing the contents of the file to look like this:\r
- <pre><code>$CONF['Self'] = '<i>copy.php</i>';\r
-include('./config.php');\r
-selectBlog('<i>shortblogname</i>');\r
-selector();\r
-\r
-?></code></pre>\r
- (You can find the short blog name in the admin area, when hovering over the blog name in the blog list)\r
- </li>\r
-</ol>\r
-\r
-<h2>Extra methods to use in copy.php</h2>\r
-\r
-<p>The <tt>selectBlog</tt> is only one of the methods which you can use in copies of <tt>index.php</tt> files. Here's a list of the available calls:</p>\r
-\r
-<table><tr>\r
- <th>Method</th>\r
- <th>Description</th>\r
-</tr><tr>\r
- <td><code>selectBlog('shortblogname');</code></td>\r
- <td>Makes sure a certain blog gets selected</td>\r
-</tr><tr>\r
- <td><code>selectSkin('skinname');</code></td>\r
- <td>Makes sure a certain skin gets selected</td>\r
-</tr><tr>\r
- <td><code>selectCategory(1234);</code></td>\r
- <td>Makes sure a certain category gets selected. Takes a category id as argument. Also accepts a category name (keep in mind that this can cause problems if multiple categories have the same name)</td>\r
-</tr><tr>\r
- <td><code>selectItem(1234);</code></td>\r
- <td>Makes sure a certain item gets selected</td>\r
-</tr><tr>\r
- <td><code>selectLanguage('french');</code></td>\r
- <td>Makes sure a certain language gets used (note: might produce PHP warnings)</td>\r
-</tr></table>\r
-\r
-<p>\r
-Make sure that these methods are called <strong>after</strong> the <code>include('./config.php')</code> statement, and <strong>before</strong> the <code>selector();</code> statement!\r
-</p>\r
-\r
-<h2>Creating a blog in a subdirectory</h2>\r
-\r
-<p>The process for creating a blog in a subdirectory (<tt>http://yourhost.com/sub/</tt> where the main weblog is in <tt>http://yourhost.com/</tt>) is similar, with the only change that you'll need to replace <code>include('./config.php');</code> by <code>include('../config.php');</code></p>\r
-\r
-\r
-\r
-\r
-\r
-\r
-\r
-\r
-\r
-\r
-\r
-\r
-\r
-\r
-\r
-<h1>XHTML Support <a name="xhtml" href="#top" class="toplink"><img src="icon-up.gif" width="15" height="15" alt="back to top" /></a></h1>\r
-\r
-<p>\r
-If you see tags like <code><br /></code> in the source code of your webpage, it's because the output of Nucleus <small>(except the things defined by templates and skins, of course)</small> is compliant to the XHTML 1.0 standard from the W3C, which is the successor of HTML 4. This way, Nucleus is ready for the future of the web. As far as I know, this XHTML support does not cause any trouble with older browsers and is correctly interpreted.\r
-</p>\r
-\r
-<p>\r
-What this means, is that you can perfectly create an XHTML-compliant site by using correct skins and templates. The default Nucleus skin is XHTML-compliant, but uses the "HTML 4 Loose" doctype. This way, users not knowing XHTML can not create documents with a false XHTML doctype.\r
-</p>\r
-\r
-\r
-\r
-</body>\r
-</html>
\ No newline at end of file
OSDN Git Service
