CMS Made Simple Forums

I have two questions, if I may.

1)
I’m one of your newest members, having installed only yesterday.  I got through the installation fine (a bit scary getting the mySQL database set up).  Anyway, I installed CMSMS in the wrong place (I took the reference to ‘root’ as something the server owner might have, but certainly not me.  I thought the folder would be a temporary place for storage and thought the installation process would prompt me for where the files should go.)  The instructions said something like, copy the installation files to a folder.  So, I created a folder /public_html/RonsInstallation/  and then when I FTPed the installation folder to the server, they ended up as /public_html/RonsInstallation/cmsmadesimple/.  To get it into a more appropriate location (ie. www.domain.com rather than www.domain.com/RonsInstallation/cmsmadesimple) I guess I will have to uninstall and reinstall?  Is there anything I need to look out for when deleting the files?

2)
When installing I got a couple of warning messages (I was on the minimum for both of these warnings):
Checking PHP memory limit (min 8M, recommend 16M)

You may not have enough memory to run CMSMS correctly. If possible, you should try to get your system admin to raise this value to the minimum 8M or great. Proceed with caution.

Checking max upload file size (min 2M, recommend 10M)

You probably will not be able to upload any files using any of the included file management functions. Please be aware of this restriction.
I asked my host provider if they could adjust their system settings for me, but got the following response: “I believe those are hard settings that cannot be changed.  Why would anybody need to upload more than a 2mb file by php? You can upload by ftp any size you want.”  So, I’m wondering how much of a problem this might be.  What has your experience been with installations running this close to the lower limit?

Thanks, Ron

If it did install OK then copy all the file out of /RonsInstallation/cmsmadesimple, admin and the like, into the root, when they said "copy the installation files to a folder" it meant to put them in the root, unless you are setting up multiple installs.

Once they are all copied to the root open your config.php and change all the paths to show the correct links...
In this example I would delete all the /cmsms for yours this /RonsInstallation/cmsmadesimple ...

#-------------
#Path Settings
#-------------

#Document root as seen from the webserver.  No slash at the end
#e.g. http://blah.com
$config['root_url'] = 'http://multiintech.com/cmsms';  this will not be here...
$config['root_url'] = 'http://www.multiintech.com';    instead...

#Path to document root. This should be the directory this file is in.
#e.g. /var/www/localhost
$config['root_path'] = '/homepages/24/d151200904/htdocs/cmsms'; this will not be here...

#Name of the admin directory
$config['admin_dir'] = 'admin';

#Where do previews get stored temporarily?  It defaults to tmp/cache.
$config['previews_path'] = '/homepages/24/d151200904/htdocs/cmsms/tmp/cache';

#Where are uploaded files put?  This defaults to uploads.
$config['uploads_path'] = '/homepages/24/d151200904/htdocs/cmsms/uploads';

#Where is the url to this uploads directory?
$config['uploads_url'] = 'http://multiintech.com/cmsms/uploads';

#---------------
#Upload Settings
#---------------

#Maxium upload size (in bytes)?
$config['max_upload_size'] = 20000000;

#Permissions for uploaded files.  This only really needs changing if your
#host has a weird permissions scheme.
$config['default_upload_permission'] = '664';

#------------------
#Usability Settings
#------------------

etc.etc.

#------------
#URL Settings
#------------
etc.  etc.

#--------------
#Image Settings
#--------------

#Which program should be used for handling thumbnails in the image manager.
#See http://wiki.cmsmadesimple.org/index.php ... ge_Manager for more
#info on what this all means
$config['image_manipulation_prog'] = 'GD';
$config['image_transform_lib_path'] = '/usr/bin/ImageMagick/';

#Default path and URL for uploaded images in the image manager
$config['image_uploads_path'] = '/homepages/24/d151200904/htdocs/cmsms/uploads/images';
$config['image_uploads_url'] = 'http://multiintech.com/cmsms/uploads/images';

Thanks for that.  I was a bit of a goose.  At least I know it's easy to install a 'development site'.

Do you have any advice or thoughts on question 2 - my server just meeting the requirements?

As far as"Checking PHP memory limit (min 8M, recommend 16M)" your site may run slow and you should be able to get your host to bump it up... mine is 40mb...

As far as uploads size it can be set here... but like they said "are you going to upload more than 2mb at a time?"

#Maxium upload size (in bytes)?
$config['max_upload_size'] = 20000000;

Hello Mark,

I put your last comment to my host provider, and I asked them if they could tweak my memory up to 16M.  This is what they said:

You are hosted on a shared server. Those settings apply to everybody so that the entire server's memory can be shared in an optimal way. I doubt it's a simple matter of tweaking.

Without knowing your aplication, I'd say if it needs twice the normal amount of memory, it might be a memory hog.

Here are typical server specs:


Quote:
Memory: 8311500k/8912896k available (1877k kernel code, 75904k reserved, 759k data, 184k init, 7470976k highmem) 

What is being reported as "memory" of 8M is probably the PHP Info paramater post_max_size - and it refers to how big a buffer of data can be exchanged between a form and a processing script. 8M is a very big buffer. I cannot see when and why you would need to make use of more for a single posting.


Anyway, our servers do not allow using a user defined php.ini to override any of the php settings, nor an .htaccess for that purpose, and this is for security purposes and also to control resources.

They have quoted their server specs.  Do you think there will be sufficient memory for CMSMS to run okay without causing me or the rest of the world any problems?

Ron

I’m between a rock and a hard place.  May I have your comment of what my hosting provider said?

Have you tried to install and run a site, even just the default, to see what kind of performance you get...

In a rendered page right click to view source at the bottom of that you will see how long it took and how many queries...

sayitlikeitis wrote: I’m between a rock and a hard place.  May I have your comment of what my hosting provider said?

What is being reported as "memory" of 8M is probably the PHP Info paramater post_max_size - and it refers to how big a buffer of data can be exchanged between a form and a processing script.

It is not the post_max_size but the memory_limit that should be raised.

Anyway, our servers do not allow using a user defined php.ini to override any of the php settings, nor an .htaccess for that purpose, and this is for security purposes and also to control resources.

In that case your provider will have to change the setting in the servers php.ini

They have quoted their server specs.  Do you think there will be sufficient memory for CMSMS to run okay without causing me or the rest of the world any problems?

With the default memory limit of 8 MB you could very well get into problems on cmsmadesimple-1.x (it could result into error messages, blank pages, data corruption), although some PHP versions seem to use less memory then others.

Regards,
D

sayitlikeitis wrote: This is what they said:

Hopefully when you request to raise the memory_limit they'll give a response like this...

BTW: did you try putting at the top of include.php? That might also do the trick.

mark wrote: Have you tried to install and run a site, even just the default, to see what kind of performance you get...

That'is a nifty trick, and the times I got seemed reasonable to me.  Perhaps I can invite people to email me if it crashes on them (but then if it crashes, they may not email me).

I'm still learning how to use CMS, and at this stage I'm the only user.  I'm obliged to you for all the good comments.  I've noted everything and I'll just see how things go once I'm running.