mamook-devel Mailing List for Mamook

Hi Alvis,


Alvis Koon wrote:

> Dear all,
>
> I encountered some problem installing the mamook.
>
> 1) What is the SCRIPT_PATH in the release_constants.inc?
>
The SCRIPT_PATH is somewhat of a legacy constant that will change in
Mamook 2.0RC5. However, in Mamook 2.0RC4, SCRIPT_PATH was used to point
to an authentication script that you write. This authentication was used
only for student and staff logins. Mamook will execute your script with
two parameters. It's up to your script to return a colon delimited
string that says whether the login succeeded (0 or 1), the type of user
this is (S for student, E for staff), and an identifier (a student
number or contact_id).

This was done this way because a lot of users of Mamook already have
existing authentication databases. So, by being able to write a script,
you can bridge get Mamook to work with that existing database.

In Mamook 2.0RC5, you'll be able to choose how you want your
authentication done, ie by a third-party database as described above, by
LDAP authentication, or handled internally inside Mamook.

> 2) After I installed, the following error occurred.
>
> adoloadcode(/var/www/adodb/drivers/adodb-type.inc.php): failed to open 
> stream: No such file or directoryadoloadcode(): Failed opening 
> '/var/www/adodb/drivers/adodb-type.inc.php' for inclusion 
> (include_path='.:/usr/share/php:/usr/share/pear')Missing file: 
> /var/www/adodb/drivers/adodb-type.inc.php
>
> ADONewConnection: Unable to load database driver 
> 'type://user:pass@server/database?option=value'
>
>
> *Fatal error*: Call to a member function on a non-object in 
> */var/www/mamook/plugins/PluginCommander.class.php* on line *71
>
> *I did set the type to mysql, why is this error happening?

I looked at your release constants, and this error is occuring because
you have the DB_DSN constant defined. In the comments in the release
constants, it says to use [DB_TYPE, DB_USER, DB_PASS] or [DB_DSN]. So,
if you comment out the DB_DSN constant, it should work.

>
> Thanks

I strongly suggest that you change your passwords and values in your
secured constants since they were included in this e-mail. Your secured
constants should never be shared.

Hopefully that helps.

-Chris Chan
Mamook Core Developer