CMS Made Simple Forums

Hi,

I'm still getting trouble with my hosting provider. This time it's the php memory again that's bothering me.

After installation of ver 1.5.1 most seemed to work fine. Just the admin pages were not shown in a proper way.
At the top, it showed all possible links after each other in text-format with links (normally in the pull down menu's) and nothing below that.
I guessed it was the shortage of php memory so I inserted "ini_set('memory_limit', '16M');" in config.php as suggested by RonnyK.

This seemd to solve the problem however after a few minutes pages at the frontend started being blank.
Since my provider (XS4ALL in The Netherlands) rejected to increase the php memory size for me there is only one thing left: look for an other provider. This was not the first issue with them.

Since this will take a while, I'm looking for ways to downsize the needed php memory for the time being.
Are there any ways to do so?

Thanks in advance,

Arthur

CMS Install Information:
CMS Version 1.5.1
Installed Modules
CMSMailer 1.73.14
FileManager 0.4.3
MenuManager 1.5.3
ModuleManager 1.2.1
News 2.9.1
nuSOAP 1.0.1
Printing 0.2.6
Search 1.5.2
ThemeManager 1.0.8
TinyMCE 2.4.10
FrontEndUsers 1.5.3
CustomContent 1.5
Config Information
php_memory_limit:
process_whole_template: true
max_upload_size: 16000000
default_upload_permission: 664
assume_mod_rewrite: false
page_extension:
internal_pretty_urls: false
use_hierarchy: false
debug: false
output_compression: false
...
use_smarty_php_tags: false
locale:
default_encoding: utf-8
admin_encoding: utf-8
PHP Information:
Current PHP Version (phpversion): 4.4.9 Caution
md5 function (md5_function):  On (True) Success
GD version (gd_version): 2 Success
tempnam function (tempnam_function): On (True) Success
Magic quotes in runtime (magic_quotes_runtime): Off (False) Success
PHP Effective Memory Limit (memory_limit): 24M Success
Maximum Execution Time (max_execution_time): 30 Caution ?
PHP Safe Mode (safe_mode): Off (False) Success
Session Save Path (session_save_path): /tmp (1777) Success
Checking if the httpd process can create a file inside of a directory it created (create_dir_and_file): Success
PHP register_globals (register_globals): On (True) Caution ?
PHP output_buffering (output_buffering): 4096 Success
disable_functions in PHP (disable_functions): Success
PHP Open Basedir (open_basedir): Success
Test for remote URL (test_remote_url): Success
fsockopen: Connection ok! Success
fopen: Connection ok! Success
File uploads (file_uploads): On (True) Success
Maximum Post Size (post_max_size): 8M Caution ?
Maximum Upload Size (upload_max_filesize): 16M Success
Basic XML (expat) support (xml_function): On (True) Success
Test file_get_contents (file_get_contents): On (True) Success
Test ini_set (check_ini_set): On (True) Success
Server Information:
Server API (server_api): cgi-fcgi
Server Database (server_db_type): MySQL (mysql)
Server Database Version (server_db_version): 5.0.32 Success
Server Software (server_software): Apache/1.3.37 (Unix) mod_ssl/2.8.28 OpenSSL/0.9.7d
Server Operating System (server_os): FreeBSD 4.10-RELEASE-p2 On i386
Permission Information
tmp: (0777) Success
templates_c: (0777) Success
modules: (0777) Success
File Creation Mask (umask): (0777) Success
config_file: 0444 Success

You could probably lower the php memory needed by uninstalling and removing unneeded modules. Depending upon what your needs are, you could probably do away with the following at least on a temporary basis:

  ModuleManager 1.2.1
  nuSOAP 1.0.1
  ThemeManager 1.0.8
  TinyMCE 2.4.10

Just De-activate the modules you don't need on a regular basis.... then any data associated with them is not lost.

Thanks guys,

I uninstalled the 4 modules and removed the memory limit line from the config.php. The front end is still blank and the admin part is not showing properly again.
Introducing the "memory_limit" line in config.php at least makes the admin part look OK. Frontend is still blank.

I'm about to re-install from scratch. Would this help or makes this no sense?

PS    I also cleared the cache and verified the system md5 check. This seems OK