Block type
Inline type
**
#online
&online;
Display the approximate number of the current visitors to the wiki.
The visitors are determined by recording the IP addresses and timestamps, and counting the number of unique accesses within the past 5 minutes (by default).
The visitors are counted throughout the entire wiki, not per page, so it makes more sense to place this plugin in the MenuBar, the skin, etc.
(Command type)
Block type
*
Upload and display the image drawn by the Java applet. This plugin requires BBSPainter.jar distributed at this website. (The site is written in Japanese only. Just look for the link to bbspainter_120.zip and download it. Put the BBSPainter.jar file in the directory where PukiWiki is installed.)
width and height are the default campus size. By default, (80,60) is used.
Put the BBSPainter.jar file in the directory where PukiWiki is installed. Otherwise this plugin does not work.
(Command type)
Block type
***
Record comments on a separate page. It can display only the recent comments on the place the plugin is placed, or it can display a radio button to specify where to display the comment.
CommentPage - the page to record comments. If omitted, the page specified by the PLUGIN_PCOMMENT_PAGE constant is used. The default value is [Comment/(current page name)]. If the specified page does not exist, it will be created when the first comment is posted.
num_items - the number of top-level items to be displayed. If omitted, the default value specified by the PLUGIN_PCOMMENT_NUM_COMMENTS constant is used.
This parameter must be placed after the comment page name. If you don't want to specify CommentPage, just put a camma before num_items (e.g., #pcomment(,15))
noname,nodate,above,below,reply - parameters to specify how to enter/display the comments
When there is a conflict (i.e., multiple comments were posted at the same time), the comment is displayed at the top or at the bottom (according to the setting) even if the radio button is checked. This is to prevent the comment from being inserted to a strange place.
When a comment is posted, the plugin displays the message indicating that the page where the plugin is placed has been updated. However, it is the comment page that has been actually updated.
Since the page containing #pcomment is not updated, it doesn't show up on the "recent changes" page.
Avoid using a relative reference (e.g. [ [../] ]) in comments, as it may not be converted as expected. (Keep in mind that the page in which you are writing comment is different from the page that will display it.)
The logging of the old comments is invoked when the number of comments reached to (PLUGIN_PCOMMENT_AUTO_LOG + PLUGIN_PCOMMENT_NUM_COMMENTS).
Block type
**
The list of frequently visited pages
num_pages - the number of pages to be displayed. The default value is defined as the PLUGIN_POPULAR_DEFAULT constant.
ExcludedPage - the regular expression that definees the pages which should be excluded from the list. The typical examples are FrontPage, MenuBar, etc.
true, false - whether to use the number of today's visitors only. The default is false.
Since this plugin depends on the information recorded by the counter plugin, the page without the counter plugin is excluded from the list. A simple way to ensure that all pages are counted is to put the plugin in the Menubar or the skin.
(Command type)
Block type
*
Display the link to a randomly selected page.
The pages to be selected from are those under the page where the plugin is placed.
string the message string displayed on the link. The default value is 'press here.'
When the page is reloaded, a different random link is displayed.
Command type
*****
Display the specified page. If the page doesn't exist, it will be opened in the edit mode. If the page name is an InterWiki, the plugin will resolve it.
This plugin is internally used when plugin= and cmd= are not specified. Users usually don't have to use it explicitly.
PageName - the page name to be displayed. This must be URL-encoded.
Block type
*****
show an updated page recently.
num_pages - the number of pages to be displayed. The default value is defined as the PLUGIN_POPULAR_DEFAULT constant.
Block type
Inline type
****
#ref( Attached file name| PageName/Attached file name| URL [,PageName] {, [left|center|right], [wrap|nowrap], [around], [noicon], [noimg], [nolink], [zoom], [999x999], [999%] } [,Title] )
&ref( Attached file name| PageName/Attached file name| URL [,PageName] {, [noicon], [noimg], [nolink], [zoom], [999x999], [999%] } [,Title] );
The file appended to the page by '#attach' is developed with a specified position. The image is displayed when the attached file is an image, and the link for download is displayed besides.
The attached file name to the page is specified for the attached file name (When omitting it, become an error). The attached file on another page can be specified by the thing assumed to be another PageName/attached file name.
The page that appends the file is specified for PageName with WikiName or BracketName. Please describe this option first (following of the attached file name). Omitting it is a page set up.
The method of developing the file can be specified for the parameter.
Please use the clear plug-in or the img plug-in to release specification with around ..going.. turning and crowding.
The method of describing two following kinds of when the attached file "fuga.jpg" on another page "hoge" is referred by the in-line plug-in form exists.
(1) &ref(hoge/fuga.jpg); (2) &ref(fuga.jpg,[[hoge]]);
The description method recommended by the one prepared to maintain the previous version and interchangeability is (1) in the description method of (2) among two above-mentioned kinds of descriptions.
Operation general even if it is which description method is the same. However, it is likely not to function normally when the following specification is done so that the image displayed like a so-called banner image may become a link to another page.
(1) [[&ref(hoge/fuga.jpg,nolink,Site name);>URL of target site]] (2) [[&ref(fuga.jpg,[[hoge]],nolink,Site name);>URL of target site]]
(3) &ref(./fuga.jpg,50%); (4) &ref(hoge/fuga.jpg,50%); (5) &ref(fuga.jpg,[[hoge]],50%); (6) &ref(fuga.jpg,50%);
(7) &ref(fuga.jpg);
Command type
***
Reference former URL(Referer) of the user who inquires the page list is displayed.
PageName that displays Referer is specified for PageName. It is necessary to encode PageName. When omitting it, the list of the page where Referer is recorded is displayed.
The order of sorting of the Referer list is specified with sort.
It is necessary to do the setting ($referer=1 is specified) that uses Referer with pukiwiki.ini.php.
Command type
PseudoBlock type
***
?plugin=related [&page=PageName]
#related
The list of the page to refer to the page of the object is displayed.
When executing it by the block type, the page set up becomes an object.
When executing it with Command type, the page that becomes an object can be specified for PageName. It is considered that top page is specified when omitting it.
Command type
***
The name of an existing page is changed. The admin authority is necessary for execution.
The difference, the backup, the attached file, and the counter of specified PageName besides the text on the page are renamed at a dash. :Parameters|
The name of the changed page is specified for PageName. When omitting it, the selection of PageName or the character string input screen for the regular expression substitution is displayed.
The execution result is a page of the conversion result. (It specifies it with PLUGIN_RENAME_LOGPAGE. The standard: RenameLog. )Is added.
The link is not rewritten in the page. Please deal with yetlist etc. by making good use of.
Information on TrackBack and Referer is not updated.
It is not checked whether the page to be renamed has been frozen.
When two or more charactors to be renamed are included in a related page, the correspondence is lost.
Command type
*
?plugin=rss [&ver=0.91| 1.0| 2.0]
RecentChanges is converted into RSS and it outputs it.
RSS output with ver is specified. When omitting it, 0.91 is output.
RSS is XML format used to deliver the summary of the site. RSS 1.0 is a succession of RSS 0.9 based on RDF(Resource Description Framework) format. In RSS 0.91, it is mounting RSS not to be original, and RSS 2.0 is a succession of RSS 0.91 and 0.92 format to RDF. It is different respectively what abbreviation the acronym named RSS is.
RSS 0.9 and 1.0: RDF Site Summary
RSS 0.91 and 0.92: Rich Site Summary
RSS 2.0: Really Simple Syndication
Command type
*
?cmd=rss10
RecentChanges is converted into RSS(RDF Site Summary) 1.0 and it outputs it.
This plug-in exists only for interchangeability with the past because the function of the rss10 plug-in was merged with the rss plug-in. (There is a possibility to be deleted in the future. )
It is redirected to URI of the rss plug-in that specifies the ver=1.0 option that it accesses this plug-in with HTTP status code 301(Moved Permanently).
Inline type
*
The ruby is put on the word.
The displayed ruby is specified for the ruby.
The word to which the ruby is put is specified for the word.
If it is not a browser corresponding to the ruby of XHTML 1.1, it is not displayed as a ruby. It is possible to display it in IE5.5/6. If XHTML Ruby Support: (white.sakura.ne.jp) is built in in Netscape 7/Mozilla, it is possible to display it.
The ruby is put in () and displayed just behind the word to which the ruby is put in a browser that doesn't correspond to the ruby.
ぺージ情報 | |
---|---|
ぺージ名 : | 英訳のお願い/PukiWiki/1.4/Manual/Plugin/O-R |
ページ別名 : | 未設定 |
ページオーナー : | nao-pon |
閲覧可 | |
グループ : | すべての訪問者 |
ユーザー : | すべての訪問者 |
編集可 | |
グループ : | すべての訪問者 |
ユーザー : | すべての訪問者 |