Module Manager memory issue

[cyberman]

As documentation says FormBuilder is one of the biggest memory eaters.

And by the way - ModuleManager/nuSoap can be deactivated if you are using FTP, ThemeManager is only useful if page is in development and can be deactivated too, the same for FileManager ... TinyMCE has a builtin one.

Have tried to deactivate some modules step by step (only for testing)?

[oliver341]

Ah ok, I thought it might be an issue with Heart Internet. Still, both our hosts use a generous memory limit of 128MB which I would have thought was enough.

[cyberman]

Its possible too to kill this limit with CMSms .

[oliver341]

Here's my module list:

Cms Version: 1.8.2

Installed Modules:

•CMSMailer: 2.0
•FileManager: 1.0.2
•MenuManager: 1.6.5
•ModuleManager: 1.4
•News: 2.10.6
•nuSOAP: 1.0.2
•Search: 1.6.5
•ThemeManager: 1.1.1
•TinyMCE: 2.7.3
•FormBuilder: 0.6.4

Php Information:

•memory_limit: 128M

[cyberman]

Have tried to deactivate some modules step by step (only for testing)?

[oliver341]

Have tried to deactivate some modules step by step (only for testing)?

Two problems with that:

1) The site is production/live so deactivating modules will break things
2) The modules are currently fully updated so I can't test if the update procedure works or not.

[cyberman]

Create a development area (second database, subfolder for core), clone the current install with no access to your live install - and for the following test you can use the backups before the modules was updated.

[oliver341]

I think I'll just update the modules by FTP...

[cyberman]

Do what you want - you've asked for a solution, I've tried to provide someone .

By the way - I've suggested this some postings before  .