BxDolModule line 64 to Config.php

Hi,

When Google tries to index the site (via the sitemap items no doubt), I see this in my logs:

 

mod_fcgid: stderr: PHP Fatal error:  require_once(): Failed opening required '/homeofdomain/modules/classes/Config.php' (include_path='.:/usr/share/pear:/usr/share/php') in /homeofdomain/inc/classes/BxDolModule.php on line 64

The ./modules/classes/Config.php actually doesn't exist, it's not on the filesystem, as a matter of fact, ./modules/classes doesn't exist.


Looking at BxDolModule.php around line 64:

        $sClassName = $sClassPrefix . 'Config';
        require_once($sClassPath . $sClassName . '.php');
        $this->_oConfig = new $sClassName($aModule);

(the middle line is line 64), it's trying to find Config.php which doesn't exist.


The Config.php files I find on the filesystem of the OS is:

 

/usr/share/pear/PEAR/Config.php
/usr/share/pear/PEAR/Command/Config.php

/homeofdomain/plugins/moxiemanager/classes/Util/Config.php

 

Obviously I want my site indexed for Google, so this is an urgent thing to try and resolve.

Any ideas?

 

Thanks.

Quote · 4 Jan 2016

This has been reported before here too:

 

https://www.boonex.com/forums/topic/Error-public-html-inc-classes-BxDolModule-php.htm

 

but no resolution.

Quote · 4 Jan 2016

If you notice in the other post, the problem is from a third party mod.

Do you have any modules other than Boonex installed?

ManOfTeal.COM a Proud UNA site, six years running strong!
Quote · 4 Jan 2016

Yes, I have about 8 mods installed (mostly from Modzzz). I'm waiting on one more from him to be updated for full compatibility with 7.2.1 so maybe that one is the problem.


Maybe this begs the question, how can one track down the mod responsible for this error? is there a debug or backtrace system available to point the finger at a mod?


In that other post, the person said they had 40 or so mods, so the above would assist others if there was a way to track down which mods are responsible for these errors.

 

If you notice in the other post, the problem is from a third party mod.

Do you have any modules other than Boonex installed?

 

Quote · 5 Jan 2016

I think the issue is related to class_prefix config key value. Below line of code is actually looking for $sClassPrefix and if it doesnt exist, it defaults to Config which leads to an fatal error.

  $sClassName = $sClassPrefix . 'Config';

All boonex modules will have one in their config.php files. Check if that key(class_prefix) have a value set in your third party modules.

Looking for Help? http://www.boonex.com/kevinmitnick
Quote · 7 Jan 2016

Hi Kevin. Thank you for your advice. I have checked all the third party modules and each one I use has the "class_prefix" defined in its config.php file.

 

What you're saying below is if they didn't have class_prefix defined then that would cause the fatal error yes?

 

I think the issue is related to class_prefix config key value. Below line of code is actually looking for $sClassPrefix and if it doesnt exist, it defaults to Config which leads to an fatal error.

  $sClassName = $sClassPrefix . 'Config';

All boonex modules will have one in their config.php files. Check if that key(class_prefix) have a value set in your third party modules.

 

Quote · 7 Jan 2016

I'm pretty sure that was the only reason for that error.

Looking for Help? http://www.boonex.com/kevinmitnick
Quote · 7 Jan 2016

Hi Kevin. Thanks for advising.


That is unfortunate as checking all the third party mods applied they all have the "class_prefix" assigned.

There is one module which isn't yet fully compatible with 7.2.1, maybe that's the module that's the problem?

 

There isn't any way I could get a debug log somehow to show which module is producing this error in my Apache logs?

 

I'm pretty sure that was the only reason for that error.

 

Quote · 7 Jan 2016
 
 
Below is the legacy version of the Boonex site, maintained for Dolphin.Pro 7.x support.
The new Dolphin solution is powered by UNA Community Management System.