Learn about DokuWiki
Learn about DokuWiki
Compatible with DokuWiki
(Early releases (before 1.0.3) had different download links; so if you have problems with their updating in Extension Manager, just uninstall the plugin and install it afresh.)
After you installed the plugin, the links to pages in your wiki will receive “Edit” button (appears on hover). So you would not need to click first the link to go to that page, and then to click “Edit page” there. With this new popover button you go to the editor window of that other page in one click.
See the popover button in action: Demo.
Hover the links and notice how the button size is adjusting to different font sizes.
Since version 1.1 (2018-11-17) there is correct support for:
The plugin should work out of the box. If you would like to adjust its looks for your template, then read on please.
2. The sizes of the popover buttons get adjusted with the links font sizes (
=1em). If you want to change the appearance (the size of the popover button, its color etc.), you can apply your styles, for example, in
<your dokuwiki>/conf/userstyle.css or in CSS files of your template. (For the original CSS see
<your dokuwiki>/lib/plugins/editonlink/script.js, and you can overwrite it in
<your dokuwiki>/conf/userscript.js or in JS files of your template).
3. Likewise, overwrite CSS if you like to change the animation of hovered links. (This animation is done via tiny inline SVG).
4. Buttons are automatically added to inner wiki links (CSS classes
wikilink2 – existing and non-existing pages) and to breadcrumbs (CSS class
breadcrumbs). It can be changed via CSS.
5. CSS conflicts are unlikely, but they can happen if you style the inner wiki links in your template with
:after pseudo-elements. That can conflict with the popover button. Then maybe you could change
:before, or something.
6. In order to add the popover button, the inner links get
position: relative. It might happen that you wish to give some of such links in your template
position: absolute or
position: fixed. (For example, if you use those links as dropdowns in navigation toolbars or something).
Then a conflict with this plugin can happen. To avoid it, you can, for example, remove classes
breadcrumbs from those specially positioned links; or wrap them in div's or span's and give special positioning to those instead of the links.
js (at least, in default DokuWiki template and similar). But it appears that links on the page get drawn before
<html> gets class
js set; so I just leave CSS as it is.
To discuss bugs or issues, please use the github tracker.
Due to some FF bug (?), in some templates, elements with “position: relative” (and manipulated visibility/opacity of pseudo-elements) can remain invisible when scrolled into the window. In that case, try to set “z-index: 1” or something.
Maybe I should add z-index to wikilink style, but I'm not sure what exactly is that bug and wouldn't that be excessive for usual templates.
Q. Would buttons added to all those links slow down the page?
A. Not at all. In general, there are several reasons why pages can get slower with plugins and other bells and whistles:
Conclusion: this plugin just couldn't have any noticeable effect on the performance.
If the link contains a parameter – like “this:page?do=something”, then the button click replaces that parameter with “?do=edit” (for the moment of clicking; then the link gets restored to its original URL). The point is, by this button you go to edit an address with any additional parameters stripped. I believe it's how the editing works anyway.
An interesting development could be to show a little popup menu when clicking that button. (It would be painted by JS, only by the click, thus having no influence on the speed of the page).