Module installation troubleshooting

[pandamonium54]

I spent gobs of time figuring this one out, so hopefully this will save one or two people a couple of hours of time.

I could install CMS-MS without any problem. Actually, CMS-MS, by itself, worked pretty well. But then I wanted to install FrontEndUsers (FEU), galleryS, and calendar.

I found that whenever I extracted FrontEndUsers/ to public_html/modules/FrontEndUsers, clicking Extensions>Modules stopped working. Firefox would load for about half a second, and then stop loading. Whatever page I was on would remain.

I found that whenever I extracted Uploads/ to public_html/modules/Uploads, I could install and activate it, but not uninstall it.

I found that galleryS would install and activate just fine, but that placing {cms_module module="galleryS" } on a page would cause that page to not load. It would not load in that all I saw was a blank page. Firefox's view source confirmed that there wasn't even html/head/body code there - just a blank page.

I found that calendar acted just the way that galleryS did.

If you're getting similar strange results, it might be due to php settings. I found this out by comparing phpinfo(); from two servers. If you can, try writing a .htaccess file to override the php settings on your webserver. The settings I found that made it work were:

.htaccess
php_value memory_limit 16M
php_flag allow_call_time_pass_reference on
php_flag display_errors on
php_flag magic_quotes_gpc on
php_value error_reporting 2039

[matcheux]

Hello,

I also have problems when uploading FrontEndUsers files to the module directory.
I have an "500 Internal Server Error" when accessing listmodules.php in the admin manager :

Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, php6-2@invalid and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.

This does not happen when installing other modules such as CMSMailer or CustomContent.

Hope Bruce Willis will help 

---
Matthieu (French user)

[CMSMS-Fan]

FrontEndUser is causing some sort of conflict on my system too:

Fatal error: Cannot redeclare implode_with_key() (previously declared in /home/fhlinux198/u/uvc-cog.org.uk/user/htdocs/modules/FrontEndUsers/FrontEndUsers.module.php:32) in /home/fhlinux198/u/uvc-cog.org.uk/user/htdocs/modules/FrontEndUsers/FrontEndUsers.module.php on line 32

If I delete the directory in the modules folder everything works fine.
I have already sorted the memory issue by upping the php.ini to 32MB
Any one suffered the same issues with this module.
Note: running CMS 0.12 fiji used both firefox and IE6 and tried FrontEndUser modules 1.0 and 1.1

[calguy1000]

this is a very weird error, if you look at the file, that function is only declared once.  For some reason it appears though that maybe your module file is getting loaded twice.

[CMSMS-Fan]

Spookey.
I have deleted the module and Cleared the cache and tried again but get exactly the same error.
I have done the above again and cleared cache on CMS and my browser and same error.
I have done all the above and uninstalled all other modules but same again.
I have done all the above and deleted the modules form the server leaving only the basic CMS install.  Same again.
I will re-install a clean instalation and see what happens and get back to you.

[sofajoe]

i have just tried to install the FrontEndUsers module and now get a blank page when i go to list modules in my admin area. 

I have already upped the memory issue in php.ini to 32MB

Any ideas on how I can install this module and not get a blank page?

[CMSMS-Fan]

Sorry I didn't update my problem.
I had to delete all CMSMS files in the end and completley re-install the lot.
I used the same database but instead of using cms_ I used CMS1_ and then went into the config.php and edited it to point to cms_ and then went back to the website again and all worked.  I then uploaded all the modules again and all worked.
I know this will never identify the problems I had but it was the only solution I could use to get the site back up and running again. 
The last thing I did before saving the config.php was to include one line at the top - ini_set('memory_limit','32M'); This cures the preset memory allocation for php use on a server where you have no access to the root to make changes to the php global settings. You can read more about the issue at http://tikiwiki.org/art82 .
After instalation all works fine.

[sofajoe]

thanks it was a memory issue. After reading about the issue at http://tikiwiki.org/art82, like an idiot, I realised i hadn't restarted Apache after upping the memory limit, i have now managed to inatll this module.

regards