Re: [psa-users] Drive Include Path Problem on new pages

[Justin K. <ju...@ko...>]

Peter Hiltz wrote:

>It doesn't make any difference.
>I've moved the metabase files down one directory below the phpsecurityadmin 
>directory, and modified include/config.php so that it shows:
>
>    'IncludePath' =>    dirname(__FILE__).'../../metabase' // where to find 
>the metabase files
>  
>
This won't work quite as you're expecting.... You need to have the slash 
added after dirname() like:

dirname(__FILE__).'/../../metabase'

>But that doesn't make a difference either. If I change that directive, I get a 
>complaint about being unable to find the metabase_interface.php file.
>  
>
Above is likely why you get this error.

>I feel like I'm missing something obvious. Somewhere there is a config file 
>staring me in the face and laughing.
>
Did you try checking out the latest CVS source? Maybe there is something 
that we had fixed there without realizing it. Basically, I always use 
dirname(__FILE__)  when looking for files so I know exactly where I am.  
I haven't had the no DBMS Driver error in so long I don't remember 
exactly what caused it.

Another option is to go to the metabase board in Yahoo groups and search 
the archives there. It definately sounds like metabase isn't playing 
nice with you.

>On Monday 19 May 2003 03:32 pm, Justin Koivisto wrote:
>  
>
>>Just out of curiosity, what happens when you change your require
>>statement to something like:
>>require_once dirname(__FILE__).'/phpsecurityadmin/_restrict.php';
>>
>>I did have a similar problem when I was first starting to use Metabase,
>>and it all came down to the include path for Metabase wasn't set, and
>>that is when I realized that the 'IncludePath' had to be set for
>>metabase to work even if I had already included the files successfully.
>>    
>>
>
>
>  
>