====== Formatting Syntax ====== [[doku>DokuWiki]] supports some simple markup language, which tries to make the datafiles to be as readable as possible. This page contains all possible syntax you may use when editing the pages. Simply have a look at the source of this page by pressing "Edit this page". If you want to try something, just use the playground page. The simpler markup is easily accessible via [[doku>toolbar|quickbuttons]], too. ===== Basic Text Formatting ===== DokuWiki supports **bold**, //italic//, __underlined__ and ''monospaced'' texts. Of course you can **__//''combine''//__** all these. DokuWiki supports **bold**, //italic//, __underlined__ and ''monospaced'' texts. Of course you can **__//''combine''//__** all these. You can use subscript and superscript, too. You can use subscript and superscript, too. You can mark something as deleted as well. You can mark something as deleted as well. **Paragraphs** are created from blank lines. If you want to **force a newline** without a paragraph, you can use two backslashes followed by a whitespace or the end of line. This is some text with some linebreaks\\ Note that the two backslashes are only recognized at the end of a line\\ or followed by\\ a whitespace \\this happens without it. This is some text with some linebreaks\\ Note that the two backslashes are only recognized at the end of a line\\ or followed by\\ a whitespace \\this happens without it. You should use forced newlines only if really needed. ===== Links ===== DokuWiki supports multiple ways of creating links. ==== External ==== External links are recognized automagically: http://www.google.com or simply www.google.com - You can set the link text as well: This Link points to google. Email addresses like this one: are recognized, too. DokuWiki supports multiple ways of creating links. External links are recognized automagically: http://www.google.com or simply www.google.com - You can set link text as well: This Link points to google. Email addresses like this one: are recognized, too. ==== Internal ==== Internal links are created by using square brackets. You can either just give a pagename or use an additional link text. Internal links are created by using square brackets. You can either just give a pagename or use an additional link text. [[doku>pagename|Wiki pagenames]] are converted to lowercase automatically, special characters are not allowed. You can use some:namespaces by using a colon in the pagename. You can use some:namespaces by using a colon in the pagename. For details about namespaces see [[doku>namespaces]]. Linking to a specific section is possible, too. Just add the section name behind a hash character as known from HTML. This links to this Section. This links to this Section. Notes: * Links to existing pages are shown in a different style from nonexisting ones. * DokuWiki does not use [[wp>CamelCase]] to automatically create links by default, but this behavior can be enabled in the [[doku>config]] file. Hint: If DokuWiki is a link, then it's enabled. * When a section's heading is changed, its bookmark changes, too. So don't rely on section linking too much. ==== Interwiki ==== DokuWiki supports [[doku>Interwiki]] links. These are quick links to other Wikis. For example this is a link to Wikipedia's page about Wikis: [[wp>Wiki]]. DokuWiki supports [[doku>Interwiki]] links. These are quick links to other Wikis. For example this is a link to Wikipedia's page about Wikis: [[wp>Wiki]]. ==== Windows Shares ==== Windows shares like this are recognized, too. Please note that these only make sense in a homogeneous user group like a corporate [[wp>Intranet]]. Windows Shares like this are recognized, too. Notes: * For security reasons direct browsing of windows shares only works in Microsoft Internet Explorer per default (and only in the "local zone"). * For Mozilla and Firefox it can be enabled through different workaround mentioned in the Mozilla Knowledge Base. However, there will still be a JavaScript warning about trying to open a Windows Share. To remove this warning (for all users), put the following line in ''conf/lang/en/lang.php'' (more details at [[doku>localization#changing_some_localized_texts_and_strings_in_your_installation|localization]]):
Formatting Syntax DokuWiki supports some simple markup language, which tries to make the datafiles to be as readable as possible. This page contains all possible syntax you may use when editing the pages. Simply have a look at the source of this page by pressing “Edit this page”. If you want to try something, just use the playground page. The simpler markup is easily accessible via quickbuttons, too. Basic Text Formatting DokuWiki supports bold, italic, underlined and monospaced texts. Of course you can combine all these. DokuWiki supports **bold**, //italic//, __underlined__ and ''monospaced'' texts. Of course you can **__//''combine''//__** all these. You can use subscript and superscript, too. You can use subscript and superscript, too. You can mark something as deleted as well. You can mark something as deleted as well. Paragraphs are created from blank lines. If you want to force a newline without a paragraph, you can use two backslashes followed by a whitespace or the end of line. This is some text with some linebreaks Note that the two backslashes are only recognized at the end of a line or followed by a whitespace \\this happens without it. This is some text with some linebreaks\\ Note that the two backslashes are only recognized at the end of a line\\ or followed by\\ a whitespace \\this happens without it. You should use forced newlines only if really needed. Links DokuWiki supports multiple ways of creating links. External External links are recognized automagically: http://www.google.com or simply www.google.com - You can set the link text as well: This Link points to google. Email addresses like this one: andi@splitbrain.org are recognized, too. DokuWiki supports multiple ways of creating links. External links are recognized automagically: http://www.google.com or simply www.google.com - You can set link text as well: This Link points to google. Email addresses like this one: <andi@splitbrain.org> are recognized, too. Internal Internal links are created by using square brackets. You can either just give a pagename or use an additional link text. Internal links are created by using square brackets. You can either just give a pagename or use an additional link text. Wiki pagenames are converted to lowercase automatically, special characters are not allowed. You can use namespaces by using a colon in the pagename. You can use some:namespaces by using a colon in the pagename. For details about namespaces see namespaces. Linking to a specific section is possible, too. Just add the section name behind a hash character as known from HTML. This links to this Section. This links to this Section. Notes: Links to existing pages are shown in a different style from nonexisting ones. DokuWiki does not use CamelCase to automatically create links by default, but this behavior can be enabled in the config file. Hint: If DokuWiki is a link, then it's enabled. When a section's heading is changed, its bookmark changes, too. So don't rely on section linking too much. Interwiki DokuWiki supports Interwiki links. These are quick links to other Wikis. For example this is a link to Wikipedia's page about Wikis: Wiki. DokuWiki supports [[doku>Interwiki]] links. These are quick links to other Wikis. For example this is a link to Wikipedia's page about Wikis: [[wp>Wiki]]. Windows Shares Windows shares like this are recognized, too. Please note that these only make sense in a homogeneous user group like a corporate Intranet. Windows Shares like this are recognized, too. Notes: For security reasons direct browsing of windows shares only works in Microsoft Internet Explorer per default (and only in the “local zone”). For Mozilla and Firefox it can be enabled through different workaround mentioned in the Mozilla Knowledge Base. However, there will still be a JavaScript warning about trying to open a Windows Share. To remove this warning (for all users), put the following line in conf/lang/en/lang.php (more details at localization): conf/lang/en/lang.php <?php /** * Customization of the english language file * Copy only the strings that needs to be modified */ $lang['js']['nosmblinks'] = ''; Image Links You can also use an image to link to another internal or external page by combining the syntax for links and images (see below) like this: {{wiki:dokuwiki-128.png}} Please note: The image formatting is the only formatting syntax accepted in link names. The whole image and link syntax is supported (including image resizing, internal and external images and URLs and interwiki links). Footnotes You can add footnotes 1) by using double parentheses. You can add footnotes ((This is a footnote)) by using double parentheses. Sectioning You can use up to five different levels of headlines to structure your content. If you have more than three headlines, a table of contents is generated automatically – this can be disabled by including the string ~~NOTOC~~ in the document. Headline Level 3 Headline Level 4 Headline Level 5 ==== Headline Level 3 ==== === Headline Level 4 === == Headline Level 5 == By using four or more dashes, you can make a horizontal line: Media Files You can include external and internal images, videos and audio files with curly brackets. Optionally you can specify the size of them. Real size: Resize to given width: Resize to given width and height2): Resized external image: Real size: {{wiki:dokuwiki-128.png}} Resize to given width: {{wiki:dokuwiki-128.png?50}} Resize to given width and height: {{wiki:dokuwiki-128.png?200x50}} Resized external image: {{https://secure.php.net/images/php.gif?200x50}} By using left or right whitespaces you can choose the alignment. {{ wiki:dokuwiki-128.png}} {{wiki:dokuwiki-128.png }} {{ wiki:dokuwiki-128.png }} Of course, you can add a title (displayed as a tooltip by most browsers), too. For linking an image to another page see Image Links above. Supported Media Formats DokuWiki can embed the following media formats directly. Image gif, jpg, png Video webm, ogv, mp4 Audio ogg, mp3, wav Flash swf If you specify a filename that is not a supported media format, then it will be displayed as a link instead. By adding ?linkonly you provide a link to the media without displaying it inline {{wiki:dokuwiki-128.png?linkonly}} dokuwiki-128.png This is just a link to the image. Fallback Formats Unfortunately not all browsers understand all video and audio formats. To mitigate the problem, you can upload your file in different formats for maximum browser compatibility. For example consider this embedded mp4 video: When you upload a video.webm and video.ogv next to the referenced video.mp4, DokuWiki will automatically add them as alternatives so that one of the three files is understood by your browser. Additionally DokuWiki supports a “poster” image which will be shown before the video has started. That image needs to have the same filename as the video and be either a jpg or png file. In the example above a video.jpg file would work. Lists Dokuwiki supports ordered and unordered lists. To create a list item, indent your text by two spaces and use a * for unordered lists or a - for ordered ones. This is a list The second item You may have different levels Another item The same list but ordered Another item Just use indention for deeper levels That's it * This is a list * The second item * You may have different levels * Another item - The same list but ordered - Another item - Just use indention for deeper levels - That's it Also take a look at the FAQ on list items. Text Conversions DokuWiki can convert certain pre-defined characters or strings into images or other text or HTML. The text to image conversion is mainly done for smileys. And the text to HTML conversion is used for typography replacements, but can be configured to use other HTML as well. Text to Image Conversions DokuWiki converts commonly used emoticons to their graphical equivalents. Those Smileys and other images can be configured and extended. Here is an overview of Smileys included in DokuWiki: 8-) 8-O :-( :-) =) :-/ :-\ :-? :-D :-P :-O :-X :-| ;-) ^_^ m( :?: :!: LOL FIXME DELETEME Text to HTML Conversions Typography: DokuWiki can convert simple text characters to their typographically correct entities. Here is an example of recognized characters. → ← ↔ ⇒ ⇐ ⇔ » « – — 640×480 © ™ ® “He thought 'It's a man's world'…” -> <- <-> => <= <=> >> << -- --- 640x480 (c) (tm) (r) "He thought 'It's a man's world'..." The same can be done to produce any kind of HTML, it just needs to be added to the pattern file. There are three exceptions which do not come from that pattern file: multiplication entity (640×480), 'single' and “double quotes”. They can be turned off through a config option. Quoting Some times you want to mark some text to show it's a reply or comment. You can use the following syntax: I think we should do it > No we shouldn't >> Well, I say we should > Really? >> Yes! >>> Then lets do it! I think we should do it No we shouldn't Well, I say we should Really? Yes! Then lets do it! Tables DokuWiki supports a simple syntax to create tables. Heading 1 Heading 2 Heading 3 Row 1 Col 1 Row 1 Col 2 Row 1 Col 3 Row 2 Col 1 some colspan (note the double pipe) Row 3 Col 1 Row 3 Col 2 Row 3 Col 3 Table rows have to start and end with a | for normal rows or a ^ for headers. ^ Heading 1 ^ Heading 2 ^ Heading 3 ^ | Row 1 Col 1 | Row 1 Col 2 | Row 1 Col 3 | | Row 2 Col 1 | some colspan (note the double pipe) || | Row 3 Col 1 | Row 3 Col 2 | Row 3 Col 3 | To connect cells horizontally, just make the next cell completely empty as shown above. Be sure to have always the same amount of cell separators! Vertical tableheaders are possible, too. Heading 1 Heading 2 Heading 3 Row 1 Col 2 Row 1 Col 3 Heading 4 no colspan this time Heading 5 Row 2 Col 2 Row 2 Col 3 As you can see, it's the cell separator before a cell which decides about the formatting: | ^ Heading 1 ^ Heading 2 ^ ^ Heading 3 | Row 1 Col 2 | Row 1 Col 3 | ^ Heading 4 | no colspan this time | | ^ Heading 5 | Row 2 Col 2 | Row 2 Col 3 | You can have rowspans (vertically connected cells) by adding ::: into the cells below the one to which they should connect. Heading 1 Heading 2 Heading 3 Row 1 Col 1 this cell spans vertically Row 1 Col 3 Row 2 Col 1 Row 2 Col 3 Row 3 Col 1 Row 2 Col 3 Apart from the rowspan syntax those cells should not contain anything else. ^ Heading 1 ^ Heading 2 ^ Heading 3 ^ | Row 1 Col 1 | this cell spans vertically | Row 1 Col 3 | | Row 2 Col 1 | ::: | Row 2 Col 3 | | Row 3 Col 1 | ::: | Row 2 Col 3 | You can align the table contents, too. Just add at least two whitespaces at the opposite end of your text: Add two spaces on the left to align right, two spaces on the right to align left and two spaces at least at both ends for centered text. Table with alignment right center left left right center xxxxxxxxxxxx xxxxxxxxxxxx xxxxxxxxxxxx This is how it looks in the source: ^ Table with alignment ^^^ | right| center |left | |left | right| center | | xxxxxxxxxxxx | xxxxxxxxxxxx | xxxxxxxxxxxx | Note: Vertical alignment is not supported. No Formatting If you need to display text exactly like it is typed (without any formatting), enclose the area either with <nowiki> tags or even simpler, with double percent signs %%. This is some text which contains addresses like this: http://www.splitbrain.org and **formatting**, but nothing is done with it. The same is true for //__this__ text// with a smiley ;-). <nowiki> This is some text which contains addresses like this: http://www.splitbrain.org and **formatting**, but nothing is done with it. </nowiki> The same is true for %%//__this__ text// with a smiley ;-)%%. Code Blocks You can include code blocks into your documents by either indenting them by at least two spaces (like used for the previous examples) or by using the tags or <file>. This is text is indented by two spaces. This is preformatted code all spaces are preserved: like <-this This is pretty much the same, but you could use it to show that you quoted a file. Those blocks were created by this source: This is text is indented by two spaces. This is preformatted code all spaces are preserved: like <-this <file> This is pretty much the same, but you could use it to show that you quoted a file. </file> Syntax Highlighting DokuWiki can highlight sourcecode, which makes it easier to read. It uses the GeSHi Generic Syntax Highlighter – so any language supported by GeSHi is supported. The syntax uses the same code and file blocks described in the previous section, but this time the name of the language syntax to be highlighted is included inside the tag, e.g. or <file java>. /** * The HelloWorldApp class implements an application that * simply displays "Hello World!" to the standard output. */ class HelloWorldApp { public static void main(String[] args) { System.out.println("Hello World!"); //Display the string. } } The following language strings are currently recognized: 4cs 6502acme 6502kickass 6502tasm 68000devpac abap actionscript3 actionscript ada aimms algol68 apache applescript apt_sources arm asm asp asymptote autoconf autohotkey autoit avisynth awk bascomavr bash basic4gl batch bf biblatex bibtex blitzbasic bnf boo caddcl cadlisp ceylon cfdg cfm chaiscript chapel cil c_loadrunner clojure c_mac cmake cobol coffeescript c cpp cpp-qt cpp-winapi csharp css cuesheet c_winapi dart dcl dcpu16 dcs delphi diff div dos dot d ecmascript eiffel email epc e erlang euphoria ezt f1 falcon fo fortran freebasic freeswitch fsharp gambas gdb genero genie gettext glsl gml gnuplot go groovy gwbasic haskell haxe hicest hq9plus html html4strict html5 icon idl ini inno intercal io ispfpanel java5 java javascript jcl j jquery julia kixtart klonec klonecpp kotlin latex lb ldif lisp llvm locobasic logtalk lolcode lotusformulas lotusscript lscript lsl2 lua m68k magiksf make mapbasic mathematica matlab mercury metapost mirc mk-61 mmix modula2 modula3 mpasm mxml mysql nagios netrexx newlisp nginx nimrod nsis oberon2 objc objeck ocaml-brief ocaml octave oobas oorexx oracle11 oracle8 oxygene oz parasail parigp pascal pcre perl6 perl per pf phix php-brief php pic16 pike pixelbender pli plsql postgresql postscript povray powerbuilder powershell proftpd progress prolog properties providex purebasic pycon pys60 python qbasic qml q racket rails rbs rebol reg rexx robots roff rpmspec rsplus ruby rust sas sass scala scheme scilab scl sdlbasic smalltalk smarty spark sparql sql sshconfig standardml stonescript swift systemverilog tclegg tcl teraterm texgraph text thinbasic tsql twig typoscript unicon upc urbi uscript vala vbnet vb vbscript vedit verilog vhdl vim visualfoxpro visualprolog whitespace whois winbatch wolfram xbasic xml xojo xorg_conf xpp yaml z80 zxbasic There are additional advanced options available for syntax highlighting, such as highlighting lines or adding line numbers. Downloadable Code Blocks When you use the or <file> syntax as above, you might want to make the shown code available for download as well. You can do this by specifying a file name after language code like this: <file php myexample.php> <?php echo "hello world!"; ?> </file> myexample.php <?php echo "hello world!"; ?> If you don't want any highlighting but want a downloadable file, specify a dash (-) as the language code: . RSS/ATOM Feed Aggregation DokuWiki can integrate data from external XML feeds. For parsing the XML feeds, SimplePie is used. All formats understood by SimplePie can be used in DokuWiki as well. You can influence the rendering by multiple additional space separated parameters: Parameter Description any number will be used as maximum number items to show, defaults to 8 reverse display the last items in the feed first author show item authors names date show item dates description show the item description. All HTML tags will be stripped nosort do not sort the items in the feed n[dhm] refresh period, where d=days, h=hours, m=minutes. (e.g. 12h = 12 hours). The refresh period defaults to 4 hours. Any value below 10 minutes will be treated as 10 minutes. DokuWiki will generally try to supply a cached version of a page, obviously this is inappropriate when the page contains dynamic external content. The parameter tells DokuWiki to re-render the page if it is more than refresh period since the page was last rendered. By default the feed will be sorted by date, newest items first. You can sort it by oldest first using the reverse parameter, or display the feed as is with nosort. Example: {{rss>http://slashdot.org/index.rss 5 author date 1h }} Fiber Optic Cables Can Eavesdrop On Nearby Conversations por BeauHD (2026/05/09 07:00) NASA Keeps Track As Mexico City Sinks Into the Ground por BeauHD (2026/05/09 03:30) <a href="https://news.slashdot.org/story/26/05/08/1928254/does-fidelitys-reorganization-signal-the-beginning-of-the-end-for-small-team-agile?utm_source=rss1.0mainlinkanon&utm_medium=feed" class="urlextern" title="https://news.slashdot.org/story/26/05/08/1928254/does-fidelitys-reorganization-signal-the-beginning-of-the-end-for-small-team-agile?utm_source=rss1.0mainlinkanon&utm_medium=feed" rel="ugc nofollow">Does Fidelity's Reorganization Signal the Beginning of the End for 'Small-Team Agile'? por BeauHD (2026/05/08 23:00) Micron Ships Gigantic 245TB SSD por BeauHD (2026/05/08 22:00) New Linux 'Dirty Frag' Zero-Day Gives Root On All Major Distros por BeauHD (2026/05/08 21:00) Control Macros Some syntax influences how DokuWiki renders a page without creating any output it self. The following control macros are availble: Macro Description ~~NOTOC~~ If this macro is found on the page, no table of contents will be created ~~NOCACHE~~ DokuWiki caches all output by default. Sometimes this might not be wanted (eg. when the <php> syntax above is used), adding this macro will force DokuWiki to rerender a page on every call Syntax Plugins DokuWiki's syntax can be extended by Plugins. How the installed plugins are used is described on their appropriate description pages. The following syntax plugins are available in this particular DokuWiki installation: Changes Plugin 2022-09-07 por Andreas Gohr List the most recent changes of the wiki Divalign2 Plugin 2020-06-11 por Luis Machuca Bezzaza Paragraph Alignment for DokuWiki Draw.io plugin 2021-02-21 por Milos Kozak Draw.io integration Dw2Pdf plugin 2023-11-25 por Andreas Gohr and Luigi Micco DokuWiki to PDF converter htmlmetatags plugin 2023-06-12 por Heiko Heinz Set html and open graph meta tags. Info Plugin 2020-06-04 por Andreas Gohr Displays information about various DokuWiki internals por Pagelist Plugin 2023-08-27 por Matthias Schulte, Michael Hamann, Michael Klier, Gina Haeussge Lists pages in a nice formatted way Semantic Plugin 2023-02-02 por Giuseppe Di Terlizzi Add Semantic Data in DokuWiki Wrap Plugin 2023-08-13 por Anika Henke Universal plugin which combines functionalities of many other plugins. Wrap wiki text inside containers (divs or spans) and give them a class (choose from a variety of preset classes), a width and/or a language with its associated text direction. Changes Plugin —- plugin —- description: List the most recently changed pages and media-files of the wiki author : Andreas Gohr email : dokuwiki@cosmocode.de type : syntax lastupdate : 2022-09-07 compatible : Elenor Of Tsort, Frusterick Manners, Greebo, Hogfather, Igor, Jack Jackrum depends : conflicts : similar : querychangelog, recent tags : changelog, listing downloadurl: https://github.com/cosmocode/changes/zipball/master bugtracker : https://github.com/cosmocode/changes/issues sourcerepo : https://github.com/cosmocode/changes This plugin allows you to embed the list of recent changes as a simple list into any page. Download and Installation Download and install the plugin using the Extension Manager. Refer to Plugins on how to install plugins manually. Syntax and Usage The list is created using the following syntax: {{changes>}} Optionally you can specify a number of parameters that control the scope of the shown changes and the way the list is rendered. The plugin always displays only the most recent change for every page / media file! Allowlist/blocklist by namespace By default plugin shows the changes in the entire wiki. To restrict the list of changes to a given namespace and its sub-namespaces you can specify its name either directly or using ns parameter: {{changes>foo}} {{changes>ns=foo}} The ns parameter supports both inclusion and exclusion of the namespaces. If a namespace name starts with a minus sign that namespace will be excluded. Also you can assign a number of namespaces as a comma separated list: {{changes>ns = -foo}} {{changes>ns = foo, bar, -bar:baz}} The first example will show the changes in all namespaces except of “foo”, the second one will include “foo” and “bar” namespaces except of “bar:baz” sub-namespace. You can also exclude specific pages: {{changes>foo&excludedpages=bar}} Number of changes displayed The number of changes that are presented in the list is controlled with count parameter (defaults to 10). The count can also be specified as just a number: {{changes>15}} {{changes>count=15}} Type(s) of changes displayed It is also possible to control the type of changes shown in the list. By default all types are shown but with type parameter you can restrict the shown changes to a given type. The supported types are create, edit, minor and delete. Multiple types can be specified separated by a comma: {{changes>type = create}} {{changes>type = edit, minor}} Allowlist/blocklist changes by user To show only changes by particular users, the user parameter takes a comma-separated list of usernames: {{changes>user = rauschen}} {{changes>user = rauschen, andi}} Exclusion of particular users is also possible using the excludedusers parameter, which also takes a comma-separated list of usernames: {{changes>excludedusers = FosseWay}} {{changes>excludedusers = FosseWay, andi}} Maximum age of change displayed Filtering by age is possible, too. Just specify the maximum age in seconds. However, please note that this plugin can not display changes older than recent_days. {{changes>maxage = 500}} Output renderer The changes can be rendered either as a simple list (default) or using Pagelist plugin. You have to install the Pagelist plugin separately, if it's not available the simple list is used instead. The renderer is selected with the “render” parameter: {{changes>render = list}} {{changes>render = pagelist}} The renderers can have extra parameters (a.k.a. flags), which can be passed within parenthesis as a comma-separated list: {{changes>render = list(signature)}} {{changes>render = pagelist(header, nouser)}} {{changes>ns = foo, bar, -bar:baz&render = pagelist}} {{changes>type = create&render = list(dayheaders, signature, nocomments, nouser)}} The built-in list renderer supports the following parameters: summary, nosummary — show/hide the change summary. signature, nosignature — show/hide user name and time of the change. dayheaders — Group changes by a heading (date of the change). nocomments — Disable comment count if Discussion is installed. nouser — do not show user column in the list. nodesc — nodescription (if you have Pagelist plugin) By default only the summary is shown. For the list of parameters supported by Pagelist plugin refer to its documentation. Multiple parameter syntax If you want to pass a number of parameters to the plugin they should be separated with an ampersand, for example: {{changes>foo&15&type=create&user=rauschen}} The above syntax would display the last 15 pages created by user rauschen inside the “foo” namespace. ACL compatability Note: The plugin respects ACL permissions but output is cached with the page it is in until a new change was made. If you're listing ACL dependent changes use the ~~NOCACHE~~ macro in the page you're using this plugin. Username fallback The plugin attempts to describe the user who made each change in the following order: If possible, the descriptive username is displayed, e.g. Joanna Schmidt If descriptive username is unavailable3), login ID is displayed, e.g. joanna.schmidt If no user information is provided to the Changes plugin by auth, the IP address the change was made from is displayed. This will likely be the case for an anonymous edit. Development A public git repository is available at https://github.com/cosmocode/changes Changelog Version upped (2023/12/14 22:50) fix cache handling. fix #71 (2023/12/14 09:41) replace deprecated function calls, adjust signatures (2023/12/14 09:31) automatic code style fixes (2023/12/14 09:17) added default files (2023/12/14 09:16) Merge pull request #70 from dokuwiki-translate/lang_update_606_168011… (2023/04/12 06:54) translation update (2023/03/29 18:35) Merge pull request #69 from dokuwiki-translate/lang_update_548_167458… (2023/01/24 18:28) Bugs and feature request Please report issues in the bug tracker at https://github.com/cosmocode/changes/issues 1) This is a footnote 2) when the aspect ratio of the given width and height doesn't match that of the image, it will be cropped to the new ratio before resizing 3) Under certain circumstances, some auth methods may be unable to provide descriptive username. For instance, authentication against a corporate AD server, where the AD server may return minimal details, and this is outside the control of the wiki administrator.