I just did a fresh install of the Maui edition on a linux box. Everything went fine except that when I go to the module manager under extensions, nothing shows up. NuSoap is installed and seems to be working but it doesn't seem to be reading anything. I go the Site Admin >> Global Settings to set the path per the help instructions but there's no option for it.
Any ideas?
Problems with Module Manager
-
carterbeech
- Forum Members

- Posts: 48
- Joined: Tue Nov 14, 2006 9:06 pm
-
jpknetweb
Re: Problems with Module Manager
I have this exact same problem, cms v1.0.2 on a linux box, nothing showing up on the ModuleManager at all. I add a piace of information, for a microsecond 2 lines of php errors show up. I managed to copy them (after a lot of tries):
Warning: load(classes/nusoap.php): failed to open stream: No such file or directory in /home/www/jpknet/web/modules/nuSOAP/nuSOAP.module.php on line 180
Fatal error: load(): Failed opening required 'classes/nusoap.php' (include_path='') in /home/www/jpknet/web/modules/nuSOAP/nuSOAP.module.php on line 180
I looked up in those directories and those files are at their place, they are there but apparently for php they are not.
Warning: load(classes/nusoap.php): failed to open stream: No such file or directory in /home/www/jpknet/web/modules/nuSOAP/nuSOAP.module.php on line 180
Fatal error: load(): Failed opening required 'classes/nusoap.php' (include_path='') in /home/www/jpknet/web/modules/nuSOAP/nuSOAP.module.php on line 180
I looked up in those directories and those files are at their place, they are there but apparently for php they are not.
-
carterbeech
- Forum Members

- Posts: 48
- Joined: Tue Nov 14, 2006 9:06 pm
Re: Problems with Module Manager
In my case, I think it has to do with my hosting provider (godaddy) not allowing me to get around an open_basedir restriction. Check your error logs and see if you have something similar.
-
carterbeech
- Forum Members

- Posts: 48
- Joined: Tue Nov 14, 2006 9:06 pm
Re: Problems with Module Manager
check in your error logs.
-
jpknetweb
Re: Problems with Module Manager
Of what? Apache? PHP? CMS?
Apache doesn't report anything unusual.
PHP has the two lines already posted.
CMS Log doesn't show anything.
I've tried replacing the line removing the relative path and placing in an absolute path and now it works... almost. It happens that all require_once calls fail so the only solution seems to be replacing all realtives with absolute paths. My open_basedir is not set so I have no restrictions in place, I'm pretty sure this can be solved without rewriting the whole CMS
.
I found out i have PHP 4.4.0. Any other insights?
Apache doesn't report anything unusual.
PHP has the two lines already posted.
CMS Log doesn't show anything.
I've tried replacing the line removing the relative path and placing in an absolute path and now it works... almost. It happens that all require_once calls fail so the only solution seems to be replacing all realtives with absolute paths. My open_basedir is not set so I have no restrictions in place, I'm pretty sure this can be solved without rewriting the whole CMS
I found out i have PHP 4.4.0. Any other insights?
-
carterbeech
- Forum Members

- Posts: 48
- Joined: Tue Nov 14, 2006 9:06 pm
Re: Problems with Module Manager
I found it in the apache error logs. That said, my host wouldn't allow me to remove the basedir restrictions so I couldn't actually get the thing to work.
If anyone has any ideas about how to make cms work on a godaddy dedicated box, please let me know.
If anyone has any ideas about how to make cms work on a godaddy dedicated box, please let me know.
-
jpknetweb
Re: Problems with Module Manager
PROBLEM SOLVED!
This problem arises when the include_path directive in php.ini is not properly set but left to default. My php.ini had a blank include_path directive, defaulting it to ".:/usr/local/Zend/lib". I modified the include_path directive to be explicitly ".:/usr/local/Zend/lib" and everything now works perfectly.
I run on Apache 1.x and PHP 4.4, this was probably fixed in later PHP versions.
This problem arises when the include_path directive in php.ini is not properly set but left to default. My php.ini had a blank include_path directive, defaulting it to ".:/usr/local/Zend/lib". I modified the include_path directive to be explicitly ".:/usr/local/Zend/lib" and everything now works perfectly.
I run on Apache 1.x and PHP 4.4, this was probably fixed in later PHP versions.
