[solved] module manager not displaying modules

[handcoded]

Hi

I've moved a cms made simple install onto another server and the module manager displays page in admin displays fine but does no list any modules. I have re-uploaded the module manager files and checked that the modules directory is set to 777 but still nothing.

I am getting this error on page load
Allowed memory size of 8388608 bytes exhausted (tried to allocate 2103424 bytes) in /home/deco/public_html/modules/nuSOAP/nuSOAP.module.php on line 180

Is this the php memory limit ? If so what is a good amount to raise it to ?

Thanks

[handcoded]

I upped the memory for php from 8 to 16mb and now the module manager is working fine.

[Nullig]

16 is good, but if you have a lot of mods, 32 would be better.

Nullig

[goallblacks]

FYI use

ini_set('memory_limit','??M');

replacing ?? with the amount you need 16, 32, or whatever

[darconny]

FYI use

ini_set('memory_limit','??M');

replacing ?? with the amount you need 16, 32, or whatever

Can you please explain this more? I have a huge problem with cmsms running on a local provider with 8MB php memory limit. The modules are not working at all, neither the page manager etc. I just get blank white pages

I asked ISP administrator but I got negative answer, ie. "it's not possible to raise php memory". So, if this can be solved somehow from the user (my) side, please explain.

Thank you in advance
Darko

[goallblacks]

Probably best to refer to the PHP manual for things like this. A description of ini_set is in section "XCII. PHP Options&Information"

However, here goes.

1.    edit admin/moduleinterface.php using whatever editor you have. I use Kate under SUSE linux
2.    Insert one of the following between line 19 and 20
        - if you want 16M allocated then insert          ini_set('memory_limit','16M');
        - if you want 20M allocated then insert          ini_set('memory_limit','20M');
        - if you want 32M allocated then insert          ini_set('memory_limit','32M');
        - ... and so on.
3.    save the module.

[darconny]

Thank you very much goallblacks

This solved just a part of my problem, some modules are accessible now (set to 32M). But, how can I raise that limit for other components, I get white pages when I try to reach Content/pages, or Content/images, templates etc?

regards
Darko

[RonnyK]

Another good point where to insert that logic is just inside the config.php, right fter the <?php opening....

This is because the config.php doesnt get overwritten in an upgrade, core-files can be overwritten. In the new version (1.4 upcoming) there is a global setting, that will set the memory in the config.php from within the backend.

Ronny

[goallblacks]

That is true. I just change it where needed so as not to tie up resources uneccessarily. i reckon a hosting provider who sets it low does that for a reason and setting it high for every script will probably deregrade the server performance.

Grabbing resources the whol time may even cause the account to be suspended.

[darconny]

I still have problems with cmsms installation, despite the fact that local hosting provider raised php memory to 16M.
Now I try to force earlier version to work (mle 1.2.3), because it says that 16M is recommended for php memory limit. Something is wrong, part of menu disappeared and I get white page on Content/pages (listcontent.php). I used ftp for coping files to web server, is it possible this caused the problems?  I am not familiar with shell installation..

Also, I can't raise php limit manually, as goallblacks said, provider can suspend my account if that cause degrading server performance.

So, if you have some advice for me, let me know..

Thanks
Darko

[Dr.CSS]

Sorry, it sounds like you need to switch to a new service provider...

[darconny]

Thank you Mark, I think you are right. But, the problem is that's the clients decision to go with that provider.
Unfortunately, I think this project will fail.

[goallblacks]

before you give up check the file permissions. Some ftp programs set them incorrectly. Also the smarty templates_c and cache_c will need to be writable

[darconny]

Hmm, I've set the file/folders permissions following install docs through Total Commander. Seems to me that everything is ok, how can I see if the problem is with permissions?

[Dr.CSS]

?Total Commander? is this your FTP client/software?...

I use FileZilla and it shows the permissions on the folders/files next to type in the rwx format meaning ReadWriteeXecute also by right clicking and looking at file attributes...