inspired by http://moinmo.in/MoinBounties
This Bounty Programme is designed to encourage development of DokuWiki software by its core developer(s) and the many plugin developers. Funders of bounties help DokuWiki developers to enhance DokuWiki in particular areas of interest for its users.
Bounties are open for any private individuals and companies - you just have to ensure (by finding other interested funders or by raising an interested topic) that the bounties' (monetary) value is not too low. Of course small changes are carried out for less money than changes which require more effort.
A bounty is valid as long as there is at least one non-timed-out funding offer for it. If a bounty gets invalid, it will be either removed or changed into a FeatureRequest by DokuWiki development core team.
As long as the bounty is not taken, you can take back or change your funding offer at any time.
At some time, one or multiple people will like to take a bounty
git clone git://el-tramo.be/wigit, index.php only 10 kB, contains git API.
| Number | Data |
|---|---|
| 1 | But numbers shall be |
| 2 | created automatically |
The author submitted a fix for this XSS-issue. http://www.dokuwiki.org/plugin:exttab2?rev=1273755792&do=diff
I have a site that uses ELGG, Vanilla Forums and DokuWiki - often embedded in the same page. The main login for the site is under ELGG and I have managed to get Vanilla Forums to use the ELGG login okay. The problem and the job is to get DokuWiki to use the ELGG login. The only requirement is that DokuWiki checks that the visitor has already logged in via ELGG.
Offer: £150 via Paypal
Offer open till Jan 1 2009
Contact: jededitor@gmail.com
ACL rules apply to media files as well - if you read protect a namespace foo:bar then all media files inside media/foo/bar are protected too. Maybe you have some errors in your ACLs? — chi 2010/01/19 11:58
Well, You are right. Thank you “chi” for your quick answer. Rol . (rol2010 at rolsys dot com)
SOLUTION by Andreas Gohr. The gallery plugin was enhanced to optionally use lightbox style image viewing including the set feature. Everyone using this feature is welcome to donate
{{edits_by>username or IP}}
{{editor>*?username}}, displaying the pages and last date/time of edit by username, or display each and every revision by a username. Now if we can only can only hyperlink every displayed usernames and IP, when clicked will show all the user's edits…dreaming :)Thanks Ryan! I suggest you donate the mentioned $15 USD to Andi. — Esther Brunner 2006-03-09 16:02done, donated 11 EUR ~ $15 USD to andi - — Ryan 2006-06-06 19:12
this is very good things
Hi Werner. I am currently on holiday so wont be able to test this till next week. But of course I am very happy to see this new plugin. Email me privately on how I can send the bounty to you. It would be my way of saying Happy Halloween :)
— Shiva Shankar 2006-10-18 13:31
Hi,
I've recently set up a wiki (http://www.songtranslator.net/lyrics) which offers translations into English of song lyrics in Spanish. Although DokuWiki syntax can hardly get any simpler, I think that, seeing as though practically all my pages have exactly the same layout, it would be great to set up a form which would create a new page and wrap up the contents of the form in DokuWiki syntax.
The format of each lyrics page is:
====== Song Title ======
Artist: //[[Artist]]//\\
{{youtube>small:youtube_video_code}}
<exttab1>
{| cell width="100%"
|First line of lyrics in Spanish
|
|-
|Next line of lyrics in Spanish
|
|-
|Next line of lyrics in Spanish
|
|-
|Next line of lyrics in Spanish
|
|-
(... etc)
|}
</exttab1>
(the empty lines on the right hand side of the table are for the translators to insert their translations)
A form which could gather the song title (which would also be the pagename), the artist, YouTube link (optional) and the lyrics line per line, create the page and then publish the form contents all wrapped up in the syntax above using a template would be much cleaner and easier to use than using the addnewpage and pagetemplate plugins or any of the blog plugins.
There are already various form plugins which output to e-mail (conform, contact, form and bureaucracy) and other wikis have similar plugins (http://twiki.org/cgi-bin/view/TWiki/TWikiForms or http://www.mediawiki.org/wiki/Extension:Semantic_Forms)
It would be convenient to be able to configure the hidden fields of DokuWiki syntax which the form contents are wrapped up in so as to adapt it to any kind of page layout, and if someone attempts to create a page which already exists there would have to be some mechanism to avoid overwriting.
Offer: 100€ via PayPal
Offer open until end of November 2008
Contact: smith [dash] robertson [at] adslmail [dot] es
Thanks!
Implemented by modifying the bureaucracy plugin and money received. I try to get the changes into the upstream distribution of the plugin. If the plugin author refuses to integrate the changes I'll post the plugin on the plugin pages. — Michael Klier 2008/11/22 15:43
The Roundbox template has not been updated since the 2005-11-12 DokuWiki release, and as a result the mediamanager no longer works well with it. The author has indicated he is no longer active in DokuWiki or PHP development and doesn't plan to maintain the roundbox template any longer.
This bounty therefore is to anyone prepared to update the Roundbox template - as a minimum to make the mediamanager functional, but ideally to update any other appropriate areas to make it compliant with the current DokuWiki release.
Offer: 40€ via PayPal
Offer open until end of 2008
Contact: geoff [at] sokoll [dot] net
This was implemented and included in the 2009-01-26 version of roundbox — Don Bowman 2009/10/18 13:23
We use DokuWiki for online documentation of our Opsview product: http://docs.opsview.org
We split out the documentation based on the release number of our product, so this allows us to make sure documentation is valid for a specific release. Our workflow is that for an upcoming release, we copy the entire subdirectory/namespace and rename to the new release number and we update documentation based on the changes for that new release as we develop.
However, we find we need branching. For instance, we could fix a problem in an earlier release, but only the specific release document would be updated - it is a manual task to update later releases. This manual task is sometimes forgotten. This in turn means that we could “lose” changes because we only cut new releases based on the latest release.
For our code procedures, if we update an older release, we can just use subversion to merge changes between branches. I'd like some automatic merging to take place behind the scenes by DokuWiki, though it would obviously have to flag if there are conflicts.
So this bounty specifically requires that I can:
Just for ideas: git in the backend?
We are offering 300 Euros.
This offer will stay open until 17th December 2007.
I created a simple word counter script which will show the number of words while editing. Feel free to donate if this fulfills your needs. — Andreas Gohr 2006-12-15 21:50
* How much?: $25 USD payable via PayPal. contact me: info a@t eziner d0t 0rg I will extend till it done!
this works: http://wiki.flux-cms.org/display/FCKW/Home we use it on our (internal) site - hoberion
Esther's blog plugin takes care of this, right? Yeah, this is solved by Esther's plugin. It works great to create page categories. I guess all that's missing is a tag index and a way to search by tags, but if you keep your wiki tidy, it's more than adequate.
maybe something like del.icio.us
Hello, I'm missing tagging, too. Tags are very cool for search in a messy wiki
The blog plugin is to big for me. Only a tag option and some functions that show the taglist like del.icon.us for embedded in some place, I like.
I too am missing tagging. I'll add $25 USD to this bounty, payable via PayPal. Nick Huntington
The blog and tag plugins have been split into different plugins. Can we/you donate to Esther and consider this closed now? — Viktor Söderqvist 2006-11-16 03:22
No, it's not enough. Esther's plugins are fabulous, but the list of tagged articles are not generated automatically. I hope DokuWiki has a built-in mechanism to handle tagging or categorizing, at least as MediaWiki do. — Roberto Ciang 2007-04-02 14:31
Is the tag plugin working as expected now ? — Christophe Gragnic 2008-01-05 16:31
A way of doing this without re-writing the user manager plugin would be to set config for defaultgroup to something like “none” and set up the ACL in the root namespace for that groupname to have the same access as group “ALL” which is unregistered users or users without a group. Then to see a list of users awaiting approval, an admin navigate to the usermanager page and search for users in group “none”. Edit the user to be part of group “user” or whatever group has some rights according to your ACL.
I know this is not the best solution, as it requires a little more than just clicking a link to approve users, nor does it tell the user that he needs to wait for an admin to approve him. But I think it comes pretty close to what you want with minimal effort :) — David Lorentsen 2007-02-22 16:11
A small note: To inform the user that he/she needs to wait for an approval from “Admin”, the notification mail content can be modified and be sent to the user. — C Ravi 2007-08-13