Cannot get x7chat module to work with RN

New Member Joined: Dec 06, 2008 Posts: 10

I hope I didn't post this in the wrong forum.

Quote:

Notice: Use of undefined constant INCLUDE_PATH - assumed 'INCLUDE_PATH' in /public_html/deadrabbitsclan/config.php on line 94

Warning: require_once(INCLUDE_PATHrnconfig.php) [function.require-once]: failed to open stream: No such file or directory in /public_html/deadrabbitsclan/config.php on line 94

Fatal error: require_once() [function.require]: Failed opening required 'INCLUDE_PATHrnconfig.php' (include_path='.:/usr/lib/php:/usr/local/lib/php:/home/werais5/php') in /public_html/deadrabbitsclan/config.php on line 94

Is anyone familiar with the x7chat? I love it, but unfortunately it doesn't seem compatible with RavenNuke, that's the error I get when trying to install it. Anyone know what I can edit/tweak to get it to work? Or a chat alternative that would work?

Running the latest version RN.

deadrabbitsclan.net

Posted: Tue Dec 09, 2008 3:30 am

Edit the config.php file in your nuke root.
Near the bottom there is a line includeing or requiring rnconfig.php
Just above that line add;
if(!defined('INCLUDE_PATH')) define('INCLUDE_PATH', './');

Posted: Tue Dec 09, 2008 3:41 am

Guardian2003 wrote:

Edit the config.php file in your nuke root.
Near the bottom there is a line includeing or requiring rnconfig.php
Just above that line add;
if(!defined('INCLUDE_PATH')) define('INCLUDE_PATH', './');

Warning: require_once(./rnconfig.php) [function.require-once]: failed to open stream: No such file or directory in /home/werais5/public_html/deadrabbitsclan/config.php on line 95

Fatal error: require_once() [function.require]: Failed opening required './rnconfig.php' (include_path='.:/usr/lib/php:/usr/local/lib/php:/home/werais5/php') in /home/werais5/public_html/deadrabbitsclan/config.php on line 95

It's what I get after placing that code into the config.php

Posted: Tue Dec 09, 2008 4:06 am

Do you have the file rnconfig.php in your nuke root?

Posted: Tue Dec 09, 2008 4:08 am

Yes, I double checked after I got the message the first time.

Posted: Tue Dec 09, 2008 4:30 am

You could try

if(!defined('INCLUDE_PATH')) define('INCLUDE_PATH', '');

But the error doesn't make any sense.
INCLUDE_PATH is set in mainfile.php which then 'includes' config.php which in turn 'includes' rnconfig.php
The only way you would get an error of this sort is;
if you have a mainfile.php from an old phpNuke installation
rnconfig.php is missing or corrupt
You are using a module or other add-on code which is calling the root config.php file directly instead of calling mainfile.php

Posted: Tue Dec 09, 2008 4:42 am

Guardian2003 wrote:

You could try

if(!defined('INCLUDE_PATH')) define('INCLUDE_PATH', '');

But the error doesn't make any sense.
INCLUDE_PATH is set in mainfile.php which then 'includes' config.php which in turn 'includes' rnconfig.php
The only way you would get an error of this sort is;
if you have a mainfile.php from an old phpNuke installation
rnconfig.php is missing or corrupt
You are using a module or other add-on code which is calling the root config.php file directly instead of calling mainfile.php

ha! That new string worked fine, I appreciate your help. I'm really glad I switched to RavenNuke the support community here is far more active, and it's given me far less headaches than plain Nuke did.

Thanks very much.

Posted: Tue Dec 09, 2008 6:25 am

No problem. Glad your module is working now Smile

Posted: Tue Dec 09, 2008 8:59 am

Guardian are you guys planning on adding something like the above to the config file with the next update? It is pain with any old installation script that is in the root that just includes the config file or any script that just includes the config file for that matter.

Posted: Tue Dec 09, 2008 10:44 am

We could do but where do you draw the line in the sand between maintaining backward compatibility?
It would not actually hurt anything to add that line (my personal opinion) but it does give us the opportunity when people have this specific problem to remind them that what they are using is quite old code so it could be perceived that leaving it out is better for their security.

Any installer that calls config.php directly instead of mainfile.php could not (as an example) use any admin authentication at the scripts runtime which means if they leave it on their server, it could be accessed by anyone with impunity.
Sometimes these swings and roundabouts give me a migrain Sad