Free

No rewards are offered at the moment (apart from my thanks and gratitude). If you have any suggestions then please let me know.

DokuWiki is kinda okay

DokuWiki is good

DokuWiki is really awesome

DokuWiki saved my life

No Benefit

The Ponder Stibbons release in 2014 introduced the new extension manager to DokuWiki. It made searching, installing and updating DokuWiki plugins much much easier.<img src="https://i.imgur.com/K7Ytm3t.png">To work, it uses the "DokuWiki Plugin Repository" which is nothing more than a simple database that gets fed information about existing plugins from the pages in the wiki. Basically that little box at the top of each plugin page is what fills the repository info.That repository then can be queried over an <a href="https://github.com/splitbrain/dokuwiki-plugin-pluginrepo/blob/master/README-API" rel="nofollow noopener" target="_blank">API</a>  and provides all the data the extension manager needs to do its work.One of the features is to show a little hint when one of your plugins is out of date. To do so the extension manager reads the version info from the plugin.info.txt of the installed plugin and compares it to the version returned by the repository API. Simple enough.<img src="https://i.imgur.com/87BXysb.png">However for that to be useful, the information on both sides need to be correct:<ul> <li>the version needs to be correct on the plugin page</li> <li>the version in the plugin.info.txt in the download needs to be correct</li></ul>Otherwise you get what you probably have experienced before: the extension manager says there's an update, the update runs through but the version doesn't change and the extension manger still thinks there's an update.And then there's a third side that can go wrong: the author may simply forget to increase the version after implementing new features or fixing bugs. Users then simply don't know that there's an update.All three things are rather common to go wrong as this <a href="https://www.dokuwiki.org/devel:badextensions" rel="nofollow noopener" target="_blank">automated page </a>shows.Introducing the DokuWiki Plugin Version FixerTo fix this problem at least for me, I used a little script that updated versions automatically for me. All it needs is a github token and a DokuWiki account and it will do all the needed updates itself.During the last days I made it into a real project <a href="https://github.com/splitbrain/dokuwiki-versionfix" rel="nofollow noopener" target="_blank">available for all Plugin authors</a> .The script automatically detects the latest significant commit in a plugin's github repository and adjusts versions in the plugin.info.txt and on dokuwiki.org accordingly.<img src="https://i.imgur.com/tws2xoQ.png">It also can automatically check all plugins registered under your email address. With a little more than a 100 public DokuWiki plugins I maintain, a necessary feature.I also added a long wanted additional feature: git tagging. The tool will automatically figure out when versions of the plugin changed in the past (by inspecting changes to the plugin.info.txt) and create lightweight git tags for those commits. This makes it easily possible to checkout a plugin at a specific older version from github.<img src="https://i.imgur.com/COMuzXa.png">The version fixer is available at <a href="https://github.com/splitbrain/dokuwiki-versionfix" rel="nofollow noopener" target="_blank">Github</a> .

Managing Plugin Versions

Andreas Gohr

I was not aware of this... Very nice ! The only problem I see is that you're creating *lightweight* tags. I believe you really should be using *annotated* tags for this instead. They are far superior, allowing one to know who created the tag and when, and also they show up when using git describe whereas lightweight tags do not.

Nice: it's indeed not that trivial to keep all those dates in sync when we have to do it manually. Having this tool might help fixing invalid ones. Thanks! Also, to prevent such desync, this git hook proved quite handy: <a href="https://github.com/gturri/dotfiles/blob/master/hooks/pre-commit" rel="nofollow noopener" target="_blank">https://github.com/gturri/dotfiles/blob/master/hooks/pre-commit</a> (in particular when it's used with a git alias which installs it automatically when a repo is cloned. Eg: <a href="https://github.com/gturri/dotfiles/blob/master/bin/git-cl" rel="nofollow noopener" target="_blank">https://github.com/gturri/dotfiles/blob/master/bin/git-cl</a>)