Specky, one of the founders of DiddlySquat, has given his personal account of the demise of DiddlySquat.

According to the Irish Gaming and Roleplaying Wiki:

Diddlysquat is an RPG publishing company founded by Geoff Moore in 2004 with the intention of producing a horror/sci-fi tabletop RPG called Spectres. The Spectres game was intended to be released as three prequels followed by the main game system.

But sadly DiddlySquat is no more and I guess we won’t be seeing Spectres as a full game (though the work will probably be made available via GCG).

When you read this kind of things it really makes you cynical about the communities involved (both online and offline). Sure I’ve argued and caused near-flame wars in the online half of the Irish gaming community, but I would hope that people don’t bare grudges and that they should realise that, sometimes, antagonistic nature of online discussion is actually healthy. But I don’t think that’s true. People do hold grudges for the slightest things.

So, here is a farewell to another doomed project of the Irish Gaming Community. I roll my dice to you (*sounds of all dice scattering across the table and getting lost on the floor* doh!)

As an aside, I can’t help but draw some parrallels to this earlier history of other projects in the community too and the recent flop of the an Game Chef concept (see this comment). I guess I’m too old for this shit.

Related Posts:

• Frustrating!
• GCG… it’s alive!
• Some of my thoughts on the Irish Scenario-Con question
• New: The Adventuring Party podcast
• Some fun with Planet Irish Gaming

Found this neat little feature in Pligg that allows you to easily add a link to Pligg. The simple code can be expanded so you can add a button to your webpage that allows it to be easily submitted to Pligg. It’s not world-shattering, nor is it an unusual feature to find.

However, if your a Redbrick Member you could add this piece of code to any of your webpages that would all you or another Redbrick user to submit it to Pligg.

Submit this to Redbrick Pligg!

If you want, you can replace “document.location.href” with an explicit URL. I guess what we really need is a icon for Redbrick Pligg!

I’m considering adding it to Planet Redbrick and Redbrick Wiki. Is it a good idea? I could package it up in a WordPress plugin but I don’t know how many Redbrick Bloggers use WordPress.

The same also applies for Game Crafter’s Guild’s Pligg, however this Pligg is specifically for Gaming and Roleplaying related content, and we don’t have an icon either!

Submit to Game Crafter’s Guild’s Pligg!

Related Posts:

• A thought-exercise: Redbrick “Web 2.0″
• Frustrating!
• Integrating Pligg beta 8.1.0 with WordPress 2.0.4 (v1.1)
• Integrating Pligg beta 8.1.0 with PubCookie
• A new look for thedeadone.net

… and just a little soul draining. My last few entries on my blog have all been about the Game Crafters Guild website and mostly technical in nature. Here, here and here.

I thought the idea behind the GCG site was/is a good one. It would be something I would contribute to and participate in. So I made a new feature-rich version of it and it went live a little while ago. I didn’t just plug together some pieces of software, I wrote code to join them, tested it, created new themes and templates for and brought it all together. It works. It is alive.

However, it is barely shambling forward.

I only know a little about getting communities started. I believe I succeeded with the Redbrick Wiki, failed with Project Freebrick and Occult Wiki. The IrishGamingWiki.com is ticking over, at least more so than GCG. I’m only involved in running Redbrick Planet but that seems to be trickling along.

The Formula: People must want it, then you fulfil that need and off you go. Once you have three or four people who believe the idea other than you and start using it earnestly, things start to happen.

With GCG, I was under the impression that there were quite a few people who would be interested in it. But I guess I did the site upgrade in a sort of vacuum. No-one was calling for it. No-one was arguing about it. Just me, thinking it was a good idea. Still do. Still working on the site. But there was no “buzz” anywhere about it. It just happened. Perhaps I should start some flame war on igaming or irishgaming.com/forums… that would generate interest, polarise people for and against the idea…

It’s just frustrating that barely anyone has logged on. I can imagine more than few had a look at the site and went “hmm, that looks good, when people start using it” and then buggered off… not realising that we need to turn you lurkers into users. I feel like a cafe manager sitting in a brand new cafe, that’s totally empty with the staff constantly cleaning tables to look busy. People look in and see it’s not busy, so they’ll come back later!

Maybe I’m just coming down off my “creative” run with it. I did do a lot in a short space of time. Maybe I’m not patient enough, that it’ll happen in good time. Perhaps with the impending Gaelcon, people are too busy but after Gaelcon will start using it. Maybe. The worst thing is when your friends say, they like it and would use it and they’ll log on… and then don’t. They have good excuses and all that, I can’t fault them per say, but they all have excuses and reasons.

What do people who read my blog think about it? Is GCG a good idea? Would use it and if so, why aren’t you, what’s the thing its missing?

One of the more frustrating elements about it is that I put some other personal projects on hold to try and finish the site. In a sense, I got buried in code so I can’t contribute to the site as a user would, as I would if someone else had created the site. I have a project (mentioned here and here as “COG”) that I had planned to use the site to do something with for example but that’s paused right now. I had a few blog entries I wanted to write about too, which are now just empty drafts waiting patiently to be filled in.

Related Posts:

• GCG… it’s alive!
• Some fun with Planet Irish Gaming
• Maybe not the end of an era, but the end of something!
• A personal perspective of the demise of DiddlySquat
• Getting DokuWiki to use WordPress Authentication (v1.2)

I’ve managed to get Pliggto use WordPress authentication and user database. You can see it running on the Game Crafter’s Guild website.

I recently got Pligg using Pubcookie and that formed the basis of this work, however they are very different.

I’ve only tested this with Pligg Beta 8.1.0. I believe future versions may have a better approach for external authentication so I can’t guarantee this will work with future versions.

This approach is very “hacky”. I’ve also been slightly lazy. It assumes that you will use WordPress’ login, logout and register pages. This will break the existing login, logout and register forms in Pligg. The ultimate solution would allow the Pligg forms to login and logout also on WordPress and the register form to create new users in WordPress.

It also does not attempt to merge the user databases from WordPress and Pligg together. Instead they are left seperate. This means that administrators have two places to manage users. If you want to delete a user, you’ve got to delete them from WordPress and Pligg seperately.

I’ve done previous external application integrations with WordPress, most notable with DokuWiki. In these previous case, I was able to allow the use of WordPress template tags in DokuWiki. However, in the case of Pligg, it is not possible as there are several function name clashes. Pligg and WordPress are considered CMSs (Content Management Systems) and it is inevitable that function names and variables clash.

Version History

1.1 (19/10/2006)

Stray header redirection in login.php removed.

1.0 (17/09/2006)

First Release

Installation locations

The first thing to do is decide on where you will install Pligg and WordPress. Pligg must be installed in either a directory on the same level as WordPress or a subdirectory of WordPress. In my code examples, I’ve installed WordPress and Pligg on the same level. I will refer to the WordPress directory as “wp” and Pligg as “p”. So, for reference, I have Pligg and WordPress installed like this:

/public_html/wp
/public_html/p

Equally valid would be:

/public_html/wp
/public_html/wp/p

Pligg and WordPress should be part of the same domain. Otherwise the WordPress cookies won’t be picked up by Pligg.

Installing the software

Install WordPress normally and configured it how you will. Make sure it’s all working. Make a not eof your database prefix and site url. You can get your database prefix from ‘wp-config.php’. It is the ‘$table_prefix’ variable. Your site url (or URI if you want to be pedantic), is where you access WordPress from. You can get the exact value from your “Options”, “General” panel when you log in to WordPress as admin. Your site url should have no trailing slash. It is important you get this right as you won’t be able to log in to Pligg later otherwise. For example, if you install into a different directory, then your webpage’s url will be different from your WordPress url.

Now install Pligg, but use the same database. Make sure everything is working, in particular that you can log in using the “god” account.

Modifying Pligg

All the work to modify Pligg takes place in ‘libs/login.php’. What we want to do is get Pligg to login using WordPress cookies/authentication. If the user doesn’t yet exist in Pligg, create it. Also, copy over all the existing user data to the Pligg database. We won’t be using Pligg’s login, authentication or logout any more.

However, we can’t just include wordpress and call wordpress functions. Instead, we’re going to have to do it manually. What I’ve done is added a function called is_user_logged_onto_wp(), which does all the extra work.

Here is the modified ‘libs/login.php’. Make sure to correctly set the $wp_db_prefix to your database prefix (including the underscore) and $wp_siteurl to your WordPress url.

< ?php
// The source code packaged with this file is Free Software, Copyright (C) 2005 by
// Ricardo Galli .
// It’s licensed under the AFFERO GENERAL PUBLIC LICENSE unless stated otherwise.
// You can get copies of the licenses here:
// http://www.affero.org/oagpl.html
// AFFERO GENERAL PUBLIC LICENSE is also included in the file called “COPYING”.
// Modified by Mark Cunningham
// (http://thedeadone.net). Log in using WordPress
// WordPress path (you don’t really need this)
//if(!defined(‘WP_ROOT’)) define(‘WP_ROOT’, mnmpath.’/../wp/’);
//
// Can’t do this, sadly as “get_permalink” collides in both code bases.
// Must do everything manually!
//require_once WP_ROOT.’wp-config.php’;
$wp_db_prefix = “wp_”;
$wp_siteurl = “http://www.myblog.com/wp”;
// Generate cookie keys!
if( !defined(‘WP_COOKIEHASH’) ) {
// this value should be the same as siteurl
$cookiehash = md5($wp_siteurl);
define(‘WP_COOKIEHASH’, $cookiehash);
}
if ( !defined(‘WP_USER_COOKIE’) )
define(‘WP_USER_COOKIE’, ‘wordpressuser_’. WP_COOKIEHASH);
if ( !defined(‘WP_PASS_COOKIE’) )
define(‘WP_PASS_COOKIE’, ‘wordpresspass_’. WP_COOKIEHASH);
// TODO: storing copy of password in pligg?
class UserAuth {
var $user_id = 0;
var $user_login = “”;
var $md5_pass = “”;
var $authenticated = FALSE;
function is_user_logged_onto_wp(){
global $db, $wp_db_prefix;
// Most of this stuff I’ve taken (and modified) from WordPress codebase
// Do we have a username and password?
if ( !empty($_COOKIE[WP_USER_COOKIE]) && !empty($_COOKIE[WP_PASS_COOKIE]) ){
$wp_username = $_COOKIE[WP_USER_COOKIE];
$wp_password = $_COOKIE[WP_PASS_COOKIE];
// Does the user exist in wordpress?
if(!$wp_user = $db->get_row(“SELECT * FROM “.$wp_db_prefix.”users WHERE user_login = ‘$wp_username’”)){
// User doesn’t exist in wordpress… so…
// … should I delete this user in Pligg?
echo “This user $wp_username does not exist in WordPress!
“;
return false;
}
// Grab data for user
$wp_userdata = $db->get_results(“SELECT meta_key, meta_value FROM “.$wp_db_prefix.”usermeta WHERE user_id = ‘$wp_user->ID’”);
if ($wp_userdata) {
foreach ( $wp_userdata as $meta ) {
@ $value = unserialize($meta->meta_value);
if ($value === FALSE)
$value = $meta->meta_value;
$wp_user->{$meta->meta_key} = $value;
// We need to set user_level from meta, not row
if ( $wp_db_prefix.”user_level” == $meta->meta_key )
$wp_user->user_level = $meta->meta_value;
}
}
// Check if username and password are valid!
if ( md5($wp_user->user_pass) != $wp_password) {
// bad password!
echo “Bad password in cookie for $wp_username!
“;
return false;
}
// Okay, user exists and _is_ logged into wordpress!
// check if user exists in pligg!
$ok = 1;
// if a user doesn’t exit… create the user
if(!user_exists($wp_username)){
$userip = $_SERVER['REMOTE_ADDR'];
$ok = $db->query(“INSERT INTO users (user_login, user_email, user_pass, user_date, user_ip) VALUES (‘$wp_username’, ‘$wp_user->user_email’, ‘password’, now(), ‘$userip’)”);
}
// if user creation was okay or user was already created, sync and log in
if($ok) {
// grab pligg user data
$user=$db->get_row(“SELECT user_id, user_pass, user_login FROM users WHERE user_login = ‘$wp_username’”);
// Copy user data from wordpress!
$sql = “UPDATE users set “;
// admins should be set as “god” in pligg. What other levels should be mapped?
if($wp_user->user_level >= ’10′){
$sql .= “user_level=’god’, “;
} else {
$sql .= “user_level=’normal’, “;
}
$sql .= “user_date=’$wp_user->user_registered’, “;
$sql .= “user_url=’$wp_user->user_url’, “;
$sql .= “user_aim=’$wp_user->user_aim’, “;
$sql .= “user_yahoo=’$wp_user->user_yim’, “;
$sql .= “user_gtalk=’$wp_user->jabber’, “;
$sql .= “user_email=’$wp_user->user_email’ “;
$sql .= “WHERE user_id=$user->user_id”;
// there are other fields in pligg that don’t exist in wordpress.
// Just ignoring them for the time being.
$db->query($sql);
// These are required for login to Pligg
$this->user_login = $user->user_login;
$this->user_id = $user->user_id;
$this->authenticated = TRUE;
$this->md5_pass = md5($user->user_pass);
$this->SetIDCookie(1, false);
// Oh, don’t forget to log the ip!
$lastip=$_SERVER['REMOTE_ADDR'];
mysql_query(“UPDATE users SET user_lastip = ‘$lastip’ WHERE user_id = {$user->user_id} LIMIT 1″);
mysql_query(“UPDATE users SET user_lastlogin = now() WHERE user_id = {$user->user_id} LIMIT 1″);
// All good!
return true;
}
else
{
echo “Problem creating user in Pligg!
“;
}
}
else
{
//debug
//echo “No wordpress user found!
“;
}
return false;
}
function UserAuth() {
global $db;
// Are we logged into wordpress?
// Don’t do anything unless we are!
if($this->is_user_logged_onto_wp()){
if(isset($_COOKIE['mnm_user']) && isset($_COOKIE['mnm_key']) && $_COOKIE['mnm_user'] !== ”) {
// Si ya está autentificado de antes, rellenamos la estructura.
$userInfo=explode(“:”, base64_decode($_REQUEST['mnm_key']));
if(crypt($userInfo[0], 22)===$userInfo[1]
&& $_COOKIE['mnm_user'] === $userInfo[0]) {
$dbusername = $db->escape($_COOKIE['mnm_user']);
$dbuser=$db->get_row(“SELECT user_id, user_pass, user_level FROM users WHERE user_login = ‘$dbusername’”);
if($dbuser->user_id > 0 && md5($dbuser->user_pass)==$userInfo[2]) {
$this->user_id = $dbuser->user_id;
$this->user_level = $dbuser->user_level;
$this->user_login = $userInfo[0];
$this->md5_pass = $userInfo[2];
$this->authenticated = TRUE;
}
}
}
// Logout of Pligg if not logged in to wordpress
} else {
$this->user_login = “”;
$this->authenticated = FALSE;
$this->SetIDCookie (0,false);
header(“Cache-Control: no-cache, must-revalidate”);
header(“Expires: ” . gmdate(“r”, time()-3600));
}
}
function SetIDCookie($what, $remember) {
switch ($what) {
case 0: // Borra cookie, logout
setcookie (“mnm_user”, “”, time()-3600, “/”); // Expiramos el cookie
setcookie (“mnm_key”, “”, time()-3600, “/”); // Expiramos el cookie
break;
case 1: //Usuario logeado, actualiza el cookie
// Atencion, cambiar aqu?cuando se cambie el password de base de datos a MD5
$strCookie=base64_encode(join(‘:’,
array(
$this->user_login,
crypt($this->user_login, 22),
$this->md5_pass)
)
);
if($remember) $time = time() + 3600000; // Lo dejamos v?idos por 1000 horas
else $time = 0;
setcookie(“mnm_user”, $this->user_login, $time, “/”);
setcookie(“mnm_key”, $strCookie, $time, “/”);
break;
}
}
function Authenticate($username, $pass, $remember=false) {
global $db;
$dbusername=$db->escape($username);
$user=$db->get_row(“SELECT user_id, user_pass, user_login FROM users WHERE user_login = ‘$dbusername’”);
$saltedpass=generateHash($pass, substr($user->user_pass, 0, SALT_LENGTH));
if ($user->user_id > 0 && $user->user_pass === $saltedpass) {
$this->user_login = $user->user_login;
$this->user_id = $user->user_id;
$this->authenticated = TRUE;
$this->md5_pass = md5($user->user_pass);
$this->SetIDCookie(1, $remember);
$lastip=$_SERVER['REMOTE_ADDR'];
mysql_query(“UPDATE users SET user_lastip = ‘$lastip’ WHERE user_id = {$user->user_id} LIMIT 1″);
mysql_query(“UPDATE users SET user_lastlogin = now() WHERE user_id = {$user->user_id} LIMIT 1″);
return true;
}
return false;
}
function Logout($url=’./’) {
$this->user_login = “”;
$this->authenticated = FALSE;
$this->SetIDCookie (0);
//header(“Pragma: no-cache”);
header(“Cache-Control: no-cache, must-revalidate”);
header(“Location: $url”);
header(“Expires: ” . gmdate(“r”, time()-3600));
header(“ETag: \”logingout” . time(). “\”");
die;
}
}
$current_user = new UserAuth();
?>
[/soure]

Now login to wordpress and go to your Pligg frontpage. You may have to reload, but you should be automatically logged into Pligg! Remember, don’t use Pligg’s login or logout any more. I’ll deal with what you need to change in the templates to handle that soon. If you use your wordpress admin account, you’ll have full ‘god’ mode in Pligg.

Final modifications

Your site isn’t fully secure yet. Delete ‘register.php’ so that no-one can create accounts using Pligg. We can also simply remove ‘login.php’ but lets not be so drastic. Lets modify ‘login.php. Look for these lines:

1
if($_POST["processlogin"] == 1) {
$username = trim($_POST['username']);
$password = trim($_POST['password']);
$persistent = $_POST['persistent'];
if($current_user->Authenticate($username, $password, $persisten$
$errorMsg=PLIGG_Visual_Login_Error;} else {
if(strlen($_REQUEST['return']) > 1) {
header(‘Location: ‘.$_REQUEST['return']);
} else {
header(‘Location: ‘.my_pligg_base.’/');
}
die;
}
}

We want to prevent hackers from using direct URLs to log in. So comment out the normal authentication test, as below.

if($_POST["processlogin"] == 1) {
$username = trim($_POST['username']);
$password = trim($_POST['password']);
$persistent = $_POST['persistent'];
if($current_user->Authenticate($username, $password, $persisten$
$errorMsg=PLIGG_Visual_Login_Error;} else {
if(strlen($_REQUEST['return']) > 1) {
header(‘Location: ‘.$_REQUEST['return']);
} else {
header(‘Location: ‘.my_pligg_base.’/');
}
die;
}
}

Pligg also comes preconfigured with one special user account, the “god” account. You can’t delete this account via the admin interface. You can create the “god” account in WordPress to prevent some user creating it and gaining “god” rights on Pligg. Or if you know sql or have access some sort of web access to your database, you can rename the “god” account to match the username of an existing admin user or delete the user outright.

Required Template Changes

So, now your WordPress users can log in on WordPress and then be automatically logged in to Pligg. But you’ve got to point the login, logout and register links to your WordPress equivelents. If your happy enough modifying the template then your ready to go. However, heres a run down of the minimal changes required to make sure it’s okay.

Lets create a copy of the existing template, mollio-beat. To do this, just make a copy of ‘templates/mollio-beat’ in ‘templates/’ (including all subdirectories). Make sure the permissions are correct, etc. I renamed this copy “gcg1″ (for Game Crafters Guild version1), so I now had a ‘template/gcg1′. I went into the admin interface in Pligg and under the Template configuration, changed ‘mollio-beat’ to ‘gcg1′ and disabled the option that lets users change the template. We don’t want users being able to go back to the old way of authentication.

We can’t use WordPress template tags. You can always write PHP and SQL code that access the data manually in your database if your that way inclined. This means we have to use direct links.

template/gcg1/header.tpl

Open up ‘template/gcg1/header.tpl’. Look for these lines:

{else}

Change them to:

Note: In my installation of Pligg, I’ve updated “my_base_url” (via the admin interface) correctly. I also have WordPress as a subdirectory of that same base url, so it became a handy shortcut to use ‘{$my_base_url}/wp’ to reference any WordPress links directly.

header.tpl controls the header of all the Pligg pages so these changes will make sure those login, logout and register links are fixed across the entire Pligg site.

template/gcg1/profile_center.tpl

‘template/gcg1/profile_center.tpl’ controls what users can modify in their profile. We’ll want to disable as much as possible of this as their profiles are overwritten from WordPress everytime they login.

Some where in the file, add this so users know where to modify their profile:

Please use this form to modify your profile.

Delete these lines. Users won’t be able to modify their passwords here, so remove the option:

{#PLIGG_Visual_Profile_ChangePass#}

Now we need to disable the fields that are copied over by wordpress. These are aim, email, yahoo, url and gtalk.

template/gcg1/story_center.tpl

‘template/gcg1/story_center.tpl’ controls the display of individual stories. If a non-logged in user, views a story, they will see a login and logout link!

Replace:

{#PLIGG_Visual_Story_LoginToComment#} {#PLIGG_Visual_Story_Register#} {#PLIGG_Visual_Story_RegisterHere#}.

With:

Login
Register

template/gcg1/sidebar/login.tpl

‘template/gcg1/sidebar/login.tpl’ is the sidebar login form you see. Replace it with this:

{#PLIGG_Visual_Login_Title#}

Register

Login

template/gcg1/sidebar/logged_in.tpl

‘template/gcg1/sidebar/logged_in.tpl’ is the sidebar panel you see when logged in. Replace the logout link:

{#PLIGG_Visual_Logout#}

With something like this:

{#PLIGG_Visual_Logout#}

I also add a link to the WordPress Admin panel for convience here.

Ready to go!

After all these changes, you should be able to login using WordPress only and be logged in on your Pligg page too! If you have any comments, feedback or find any bugs, just leave a comment here. Thanks.

Related Posts:

• Add a “pligg it” button to your webpage!
• Frustrating!
• Getting DokuWiki to use WordPress Authentication (v1.2)
• GCG… it’s alive!
• Where has TDO Mini Forms plugin gone?

This extension does not transform your WordPress (WP) posts into DokuWiki (DW) entires. If your looking for that functionality, I’d recommend doing a google search for dwBliki plugin.

What this extension does is to get DokuWiki to use WordPress’ authentication, i.e. DokuWiki to use WordPress’ user database, using an authentication plugin for DokuWiki.

Download the DokuWiki Authentication Extension (v1.2)

Previous downloads:Download the DokuWiki Authentication Extension (v1.1) and Download the DokuWiki Authentication Extension

Before you begin, you’ll need to be able to run MySQL commands on your WP database and shouldn’t be afraid of modifying some code.

Much of this work was based on the DW splitbrain.org wiki documentation. I used the phpbb integration as a template. See:

http://wiki.splitbrain.org/wiki:auth:mysql
http://wiki.splitbrain.org/wiki:tips:integrate_with_phpbb

I’ve tested this with versions:

DokuWiki: 2006-03-09d
Wordpress: 2.0.4

I can’t speak for other versions.

Version History

1.2 (10/10/2006)

• The extension turns back on “magic quotes” which causes additional slashes in DW articles after editing.

1.1 (03/10/2006)

• Small fix for using WordPress tags while logged in.
• Documentation/Instructions updates

1.0 (27/09/2006)

• First Release

Notes on using this authentication plugin

I’d recommend that you get your users to use the WP’s Register, Login and Logout interface rather than DW’s. However, DW’s Login and Logout should work fine and they should log in and out of WP at the same time.

BUT you should use WP to add new users. If you use DW, they won’t be configured correctly to use WP as you need to modify two SQL tables and DW will only modify one.

By default all users are a member of the “defaultgroup”. WP does not have any concept of user groups. It does have a concept of roles which I have ignored because I wanted the flexibility of DW’s user groups. You can’t really remove users from this group unless you modify “wordpress.class.php”.

You can use DW’s “User Manager” to add and remove your WP users from DW’s user groups but avoid the “Configuration Settings” as this overwrites your local.php and seems to cause problems for the WP authenication.

This plugin also introduces a useful feature. Because it pulls in your WordPress files, you can then, anywhere else in DW, access WordPress functions. This means, for example, you can use template functions like “get_header();” or “get_sidebar();” if your skinning your DW.

First up: Installing WordPress and/or DokuWiki

For installing WP or DW, refer to the included installation documentation.

Install WP first and make sure everything is up and running before installing DW. Make sure that DW is installed in a directory at the same level as WP or as a subdirectory of WP. This is to make sure that the cookie domains are the same.

In my test environment I had wordpress installed @ ~/public_html/test/wp and DW installed @ ~/public_html/test/dw.

Now, configuring DokuWiki…

First, copy “wordpress.class.php” to /inc/auth. Open it in your favorite text editor and make sure that WP_ROOT is correct:

if(!defined(‘WP_ROOT’)) define(‘WP_ROOT’, DOKU_INC.’../wp/’);

I have it configured by default to assume that dokuwiki is installed at the same level as WP and that WP is installed in a directory called “wp”.

acl.auth.php

You probably created a “conf/acl.auth.php” when you installed DW initially. If you didn’t, make a copy of conf/acl.auth.php.dist and name it “acl.auth.php”.

local.php

You probably created a “conf/local.php” when you installed DW initially. If you didn’t, make a copy of conf/local.php.dist and name it “local.php”. Open it in your favorite text editor and add (or modify) these settings:

// Disable the ability to register: users should register via the WordPress interface
$conf['openregister']= 0;
// Disable password autogen: not important if users can’t register
$conf['autopasswd'] = 1;
// Disable password resend: let wordpress do this
$conf['resendpasswd']= 0;
// Enable access control
$conf['useacl'] = 1;
// Use wordpress authentication
$conf['authtype'] = ‘wordpress’;
// Not sure what passcrypt needs to be set to, but this works
$conf['passcrypt'] = ‘smd5′;
// Recommend you set defaultgroup to “user” and “superuser” admin group.
// as we’ll be creating them during our integration.
$conf['defaultgroup']= ‘user’;
$conf['superuser'] = ‘@admin’;
// Updating profile requires password
$conf['profileconfirm'] = ’1′;

Finally, modifying your SQL Database

First, backup your database. You can do this quite easily via WP’s Database plugin.

You need to create two new tables to support DW. In the code below I’ve called these tables “wp_dw_groups” and “wp_dw_usergroups”. If you did not use “wp_” as your database prefix for WordPress, you will need to modify these commands before you use them and replace “wp_” with the prefix you used. “wordpress.class.php” uses the database prefix to reference these tables.

Connect to your database and run these two commands:

CREATE TABLE `wp_dw_groups` (
`gid` int(10) UNSIGNED NOT NULL AUTO_INCREMENT,
`name` varchar(50) NOT NULL DEFAULT ”,
PRIMARY KEY (`gid`),
UNIQUE KEY `name` (`name`)
) TYPE = MYISAM;
CREATE TABLE `wp_dw_usergroup` (
`uid` int(10) UNSIGNED NOT NULL DEFAULT ’0′,
`gid` int(10) UNSIGNED NOT NULL DEFAULT ’0′,
PRIMARY KEY (`uid`,`gid`)
) TYPE = MYISAM;

These will create the two tables you need. However, you need to setup some groups too. So these two commands will create a user and an admin group.

INSERT INTO `wp_dw_groups` VALUES (1,”admin”);
INSERT INTO `wp_dw_groups` VALUES (2,”user”);

Now you need to give yourself admin rights. Normally the first user created in WP is the admin account. This normally has the ID of 1. So now we will add admin user to admin and user groups.

INSERT INTO `wp_dw_usergroup` VALUES (1,1);
INSERT INTO `wp_dw_usergroup` VALUES (1,2);

Finished

Now you should be able to login and logout using your WP’s users on DW!

Related Posts:

• Frustrating!
• GCG… it’s alive!
• Some fun with Planet Irish Gaming
• Integrating Pligg beta 8.1.0 with WordPress 2.0.4 (v1.1)
• WordPress 2.0!

So I’ve been quiet. Hidden away in a bunker, miles underground. All I had was a laptop and broadband. The data packets crackled with the potential of lightning. My eyes were bleary and red as I fumbled trying to stitched the limbs on… in my final moments of exhaustion, I was transfixed with horror as it opened it’s eyes…

“It’s alive…” I shuddered before I lost my mind.

Well the truth is, I probably lost my mind long before then.

I’ve kinda been consumed on a web project these last few days. All my spare “creative” cycles have gone into it. What started as a little demo, became a prototype, became a full working site! And I just couldn’t stop.

I wanted to show specky_ie what could be done, fairly easily, with existing open-source software for the Game Crafter’s Guild of Ireland website. As I discovered, a lot can be done. I’ll reserve the details of how and what I did for another post as I think it’d be useful for a lot of wordpress fans.

Anyway, the site is currently live, but we haven’t officially announced it yet. The Guild is place for people who want to be creative using roleplaying games. It’s not specifically for the online Irish gaming community at all. It is distinct, different and hopefully open to everyone who has or might have an interest, either as contributor, self-promotion or just wants to get the latest news.

Anyway, it’s online, it’s up. Go see it and tell me what you think (either here or there, I don’t mind). In fact, start contributing by joining the forums. It’s a shell waiting to be filled right now.
Now, my next big problem is, I think I may have to redesign my own website!

Related Posts:

• Frustrating!
• Some fun with Planet Irish Gaming
• A personal perspective of the demise of DiddlySquat
• Getting DokuWiki to use WordPress Authentication (v1.2)
• My newest experiement: The Irish Gaming Wiki