Nothing to see here.<\/p>"},"ratings":{"1":0,"2":0,"3":0,"4":0,"5":"1"},"assets_icons":[],"assets_banners":{"banner-772x250.png":{"filename":"banner-772x250.png","revision":"648552","resolution":"772x250","location":"assets"}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["0.6.1","0.6.2","0.6.3","0.7","0.8","0.8.1","0.9","0.9.1","0.9.2"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":"648548","resolution":"1","location":"assets"},"screenshot-2.png":{"filename":"screenshot-2.png","revision":"648548","resolution":"2","location":"assets"},"screenshot-3.png":{"filename":"screenshot-3.png","revision":"648548","resolution":"3","location":"assets"}},"screenshots":{"1":"WordPress Wiki That Doesn't Suck articles page","2":"Edit\/Add New article page","3":"Custom HTML editor in WordPress 3.3"}},"plugin_section":[],"plugin_tags":[1487,1104,9545],"plugin_category":[47],"plugin_contributors":[80736],"plugin_business_model":[],"class_list":["post-11121","plugin","type-plugin","status-closed","hentry","plugin_tags-custom-post-types","plugin_tags-support","plugin_tags-wiki","plugin_category-education-and-support","plugin_contributors-jazzs3quence","plugin_committers-jazzs3quence","plugin_committers-nerrad"],"banners":[],"icons":{"svg":false,"icon":"https:\/\/s.w.org\/plugins\/geopattern-icon\/wordpress-wiki-that-doesnt-suck_c2adac.svg","icon_2x":false,"generated":true},"screenshots":[{"src":"https:\/\/ps.w.org\/wordpress-wiki-that-doesnt-suck\/assets\/screenshot-1.png?rev=648548","caption":"WordPress Wiki That Doesn't Suck articles page"},{"src":"https:\/\/ps.w.org\/wordpress-wiki-that-doesnt-suck\/assets\/screenshot-2.png?rev=648548","caption":"Edit\/Add New article page"},{"src":"https:\/\/ps.w.org\/wordpress-wiki-that-doesnt-suck\/assets\/screenshot-3.png?rev=648548","caption":"Custom HTML editor in WordPress 3.3"}],"raw_content":"\n
The main purpose of this plugin is to provide a page to display documentation. Not a Wiki per se<\/em>, as it's not intented to be collaborative (although it can be), rather, it just uses Custom Post Types to separate documentation articles from the rest of your content. This plugin came as a result of my undying hatred of MediaWiki. I know BBCode and HTML and PHP and CSS and still the wiki markup just baffles me. I can never remember how to do the simplest<\/em> things, like create a freaking link. Really? All I want to do is throw a WordPress Wiki That Doesn't Suck<\/em> uses custom post types. And that's pretty much it. It creates a new custom post type ( To display your wiki articles on a page, you can either use the included template files (in the You can see WPWTDS in action at http:\/\/museumthemes.com\/wiki\/ and http:\/\/eventespresso.com\/support\/documentation\/<\/p>\n\n\n Not yet.<\/p><\/dd>\n Basically, I had a specific need, custom post types seemed like the best answer. Plus, once it was done, I couldn't think of anything else it really needed.<\/p><\/dd>\n This wasn't a concern for me, since I just wanted someplace I could post support docs that was public. That said, generic WordPress user roles will still work, so if you're an Author<\/em> you'll be able to post new wiki articles, same as anything else.<\/p><\/dd>\n After you install the plugin, wiki articles will use your theme's default A default template that you can use is provided if you want to customize the layout. More than likely you'll need to modify it slightly to fit your specific theme.<\/p>\n\n The best reference I can give you for working with custom post types (if you wanted to make your own wiki main page, for instance) is the Custom Post Types<\/a> article in the Codex<\/a>. The only thing you need to know is that the post types are identified as Version 0.9.2<\/strong><\/p>\n\n Version 0.9.1<\/strong><\/p>\n\n Version 0.9<\/strong><\/p>\n\n Version 0.8.1<\/strong><\/p>\n\n Version 0.8<\/strong><\/p>\n\n Version 0.7<\/strong><\/p>\n\n Version 0.6.3<\/strong><\/p>\n\n Version 0.6.2<\/strong><\/p>\n\n Version 0.6.1<\/strong><\/p>\n\n Version 0.6<\/strong><\/p>\n\n Version 0.5<\/strong><\/p>\n\n<a href=\"...\"><\/code> in there. If you're looking at this plugin, you know what I'm talking about. When this plugin was written the WordPress plugins available for what I want to do either aren't<\/em> what I want to do, or don't work with the latest version of WordPress. Hence this plugin.<\/p>\n\nwpwtds_article<\/code>) that can be accessed from the Wiki != suck<\/em> menu it adds to your sidebar (!= is \"not equal to\" in coder jargon). Wiki articles are posted with the wiki<\/code> slug, so your URLs will look like http:\/\/mydomain.com\/wiki\/my-cool-article<\/code>.<\/p>\n\n\/templates<\/code> directory), or you can use the [wpwtds]<\/code> shortcode that's been added in 0.9.<\/p>\n\n\n
\/wp-content\/plugins\/<\/code> directory or use the Add New Plugin option in WordPress to install.<\/li>\n[wpwtds]<\/code> shortcode or the included template file examples to display a list of wiki articles on your page.<\/li>\n<\/ol>\n\n\n\n
single.php<\/code> template file. You may want to actually use<\/em> your wiki, as in have an actual wiki page, and for that, you'll either need to add a custom template to your theme or use the [wpwtds]<\/code> shortcode. To use the shortcode, all you need to do is add [wpwtds]<\/code> on a post or a page and it will display a list of all your wiki articles.<\/p>\n\nwpwtds_article<\/code>s.<\/p><\/dd>\n\n<\/dl>\n\n\n\n
\n
\n
\/templates\/<\/code> directory, but now you can use [wpwtds]<\/code> to display all your docs in a generic format.<\/li>\n<\/ul>\n\n\n
\n
\n
single-wpwtds_article.php<\/code><\/li>\n<\/ul>\n\n\n
\n
\n
readme.txt<\/code><\/li>\n<\/ul>\n\n\n
with_front<\/code> qualifier to the rewrite<\/code> option to use it's own permalink structure.<\/li>\n<\/ul>\n\n\n