4
paint... paint... uff... uff...
I adopted phprojekt and "adapted" it to work with xoops:
1) I put XOOPS and projekt tables in the same DB (with different prefix: xoops_ and projekt_)
2) I write a php script to replicate XOOPS user, groups, and user group association in phprojekt. The script copy/update XOOPS user in a predefined group (projekt users) to projekt.
3) I create a phprojekt "skin" with a menu similar to XOOPS menu (vertical with projekt entries and a link to the site home)
4) I patched phprojekt login (lib/auth.inc.php) to accept authentication from XOOPS user table:
if ($row[1] == $enc_pw) {
// store the found user_ID
$fetch_uservalues = $row[0];
} // end check for &pw
// BEGIN XOOPS AUTH
if ( ! $fetch_uservalues ) {
$xoopres = db_query("select pass from xoops_users where uname='$loginstring'");
$xooprow = db_fetch_row($xoopres);
if ( $xooprow && ($xooprow[0] == md5($user_pw)) ) {
$fetch_uservalues = $row[0];
}
}
// END XOOPS AUTH
} // end loop over all found users with the same loginstring
} // end case for non-ldap auth
} // end else bracket for authentication
All work quite fine (i am starting using it)... except (todo):
5) avoid requiring a new authentication entering in projekt page... now i have to auth entering in XOOPS and than again when selecting projekt
Ho can i do??? cookies??? Is there an active session table in xoops??? other ways???
6) write a XOOPS modules to show blocks from projekt tables. I am working on it but i think it will long :( :( Writing XOOPS modules doesn't seem too complex... but understand German field names in projekt isn't soo easy
Bye
PeterPan