UPDATE
WordPress Wiki 1.0 is now available through the WordPress plugin repository, or through the built-in plugin installer in WordPress!
Get it here:
***
It’s finally here!
Some of you may be scratching your heads, since we’ve been calling this release 0.9 all along. We decided to call this one 1.0 because of the significant changes made by converting the plugin to Object Oriented/MVC design and putting all the widgets back in.
Plus, 1.0 just feels better 
.
Download from GitHub for now- the plugin will be available in the WordPress plugin repository shortly.
Wicked!
If possible I think you should ask the Plugin Directory staff to reset the ranking of this plugin, considering the vast changes.
I gave it a test on a fresh install on kodingen.com. Ran into these issues thus far:
- Even if I opt not to add a TOC, it’s added anyhow and the box is always checked upon refresh after an ‘Update’ or ‘Publish’.
- ‘Wiki Options’ is a blank page. It also brakes the drop-down of the compressed admin menu.
- Several custom themes (P2 & LightWord) did not display wiki pages very well. WooThemes’ “Listings” (which deploys its own CPT) even kept the post type from showing up in the admin menu. PageLines however seemed to handle it perfectly, from the little testing I did with it.
My first requests would be:
Update the pages, apply a more distinctive theme and maybe add a forum component like Vanilla.
- Enable ordinary tags and add a custom wiki taxonomy for categorization of wiki articles.
- Make this a proper website!
All in all fantastic work man, I’m very happy the 1.0 is upon us!
Lame. I’ll see if I can fix that. It’s supposed to be turned on by default, but it should stay off if you uncheck it.
The problem with the Wiki Options page was fixed right after it was pushed to the WordPress repository, re-download and try again.
Themes are going to be tricky with this plugin no matter what we do, which was part of the reason why the “Views” have been separated out. Any suggestions here?
Noted. We’re working on this site currently, expect changes soon.
Glad to hear the site upgrades are coming. Definitely feel good and ready to settle down with an account just about now.
About the themes, I’m not a developer myself so there’s nothing substantial I can suggest. I would however like to reiterate that the PageLines theme, while completely different from TwentyTen, by all appearances worked flawlessly with the plugin. So even though they don’t abide by common conventions (so it seems to me anyhow), they must be doing something very right in terms of compatibility with your plugin. Maybe if you dig into the source there are some ‘recommended practices’ and ‘useful code snippets’ to retract from it.
I don’t know what you mean by “Views” separated out.
Oh, and another thing, though I might have mentioned it earlier:
Please be sure to make this plugin work with WPML. Straightforward translation of wiki pages would be a huge feature. I’ll test what I can.
I agree about WPML. We should also setup a glotpress site for this.
I’ll ask Amir from WPML to test WPML compatibility
Check the plugin folder for the “views” folder. The one that controls the display of the front-end interface isn’t in there yet but will be soon.
Ah, that ‘view’, got it.
As for WPMU, I got around to doing some initial tests. I seem to have translated an ordinary wiki page successfully:
http://erlendsh.kodingen.com/wiki/wordpress/wiki/my-first-wikipage/
However I also translated my About page, and then I tried the “make this a wiki page” option, which made it disappear (leaving the Norwegian translation behind, because I checked the “this is a minor edit, don’t update the translation” option). And this link leads nowhere either:
http://erlendsh.kodingen.com/wiki/wordpress/wiki/about
So just saying, there are definitely a couple sinkholes to be aware of here, but it looks like with a little bit of care there shouldn’t be anything in the way of excellent multilanguage capabilities!
Followup: Wups, seems WPML ain’t too happy with your front-end editing. I tried editing the Norwegian version of ‘my-first-wikipage’ (i.e. ‘min-første-wikiside’) and it just disappeared, just like the About page ^^
This time it didn’t go that far though. It was still around, with the edit successfully applied (stilig! => kult!) at:
http://erlendsh.kodingen.com/wiki/wordpress/wiki/min-f%C3%B8rste-wikiside/
… just without the ‘?lang=nb’ to make it work as a translation.
Checking back with the admin panel, it was like the translation had never been there, and I could add a new one no problem, so I did (notice the ‘-2′ on the translation).
You’re crazier than a coconut for supporting WordPress < 3.0.. It's just not worth the headache!
Fantastic news. Thanks for your hard work
If I want to open the settings, i get this error: Fatal error: Call to a member function has_cap() on a non-object in /var/www/wp-content/plugins/wordpress-wiki/controllers/wiki_admin.php on line 41
What version of WordPress are you using?
I keep getting “You don’t have permission to do that.” when I try to edit a wiki page from the frontend. I’m logged in with the administrator.
Any reason why it’s doing that? Or can only wiki-editors edit wiki pages?
No, everybody should be able to edit pages. There’s no permission check on the front end editor (or it isn’t supposed to be).
What version of WordPress and WordPress Wiki are you running?
WordPress 3.0.4 and Wp Wiki version 1.0.
Found out that it was a Theming error, my custom theme didn’t have certain tags.
Thanks anyway!
I know it’s my theme, but I can’t seem to figure out what tags it’s missing. It uses wp_head(), does wp-wiki need any more?
Hi there!
It was working correctly before the update, but I’m having weird problems afterwards. The wiki entries no longer inherit #single_content into postcontent / post_content. So, the entries are displaying at front page width, or 395px fixed. I can’t find anything that will let me change that. Additionally, to get the TOC to populate, I have to use H2 or H3 tags within the text field? This means that I’m duplicating my table of contents in headline sized font on the entry itself. Any way around that? I really want this plugin to work, but I’m utterly flummoxed right now.
Oh yeah, I’m also having the issue with TOC rechecking itself on update. Unable to turn it off.