[solved] problem upgrading from 1.4 to 1.5.4

[quartney]

Okay, I uploaded the tar.gz via CPanel.  Thanks, I didn't know I could do that and it was sooooo much easier!

My checksum errors were few, but here they are:

Code: Select all

/home/content/w/r/k/wrk/html/tmp/cache/SITEDOWN
This resource is not exist!
/home/content/w/r/k/wrk/html/tmp/cache/index.html
This resource is not exist!
/home/content/w/r/k/wrk/html/tmp/templates_c/index.html
This resource is not exist!

My installation was completed "successfully" but the site is not working correctly.  For example, there is no stylesheet and the modules aren't working.  My modules menu still looks like the above screen shot with a lot of --Add Me before each choice.

[alby]

My installation was completed "successfully" but the site is not working correctly.  For example, there is no stylesheet and the modules aren't working.  My modules menu still looks like the above screen shot with a lot of --Add Me before each choice.

And System Information?

Alby

[quartney]

And System Information?

the same as before:
System information says:
> string(55) "Smarty error: unable to read resource: "systeminfo.tpl""

System verification says:
> string(53) "Smarty error: unable to read resource: "checksum.tpl""

[Dr.CSS]

You are obviously missing some files, maybe your system isn't letting you create them...

[alby]

the same as before:
System information says:
> string(55) "Smarty error: unable to read resource: "systeminfo.tpl""

System verification says:
> string(53) "Smarty error: unable to read resource: "checksum.tpl""

This is very strange, script must read your files for check md5sum!
Have you check with System Verification or with cmschecksum.php? Try with first (you are into CMSMS)
And in install step 2 all green check?
After clean cache and templates_c and re-enter in admin part

Alby

[quartney]

via cmschecksum.php:

Code: Select all

Checksum test
All checksums match!

And in install step 2 all green check?

Yes, although there were some warnings about file size, I think. 

I still have the same system information error and system verification error.

Look what the cms home page looks like:

[quartney]

my problem is the same as this guy's except I don't know if he got it solved or not:
http://forum.cmsmadesimple.org/index.ph ... 527.0.html

[quartney]

also, at the bottom of the extensions>modules page there is this error:

Code: Select all

 The modules folder is not writable, if you would like to install modules by uploading an XML file you need to make the modules folder have full read/write/execute permissions (chmod 777). Safe mode may also be in effect. (Troubleshooting)

even if the modules folder is 777.  and I've tried it at 755 as a previous post of mark's suggested.

[alby]

Yes, although there were some warnings about file size, I think. 

File size? If you have install folder you can re-run in step 2
However (for modules) are permissions issue of modules/MODULE/lang folder
(For Admin) are permission of admin/templates folder (I think that not work Group permissions also)

Alby

[quartney]

warnings:

Code: Select all

Checking PHP time limit in second
(minimum 30, recommend 60 or greater)
Number of seconds a script is allowed to run. If this is reached, the script returns a fatal error.

Code: Select all

Checking max post size
(minimum 2M, recommend 10M or greater)
You will probably not be able to submit (larger) data. Please be aware of this restriction.

Code: Select all

Checking max upload file size
(minimum 2M, recommend 10M or greater)
You will probably not be able to upload (larger) files using the included file management functions. Please be aware of this restriction.

[Ted]

Are the paths in config.php correct?  Maybe the host moved the path of the site without telling you?

[quartney]

Ted, you have the right idea.  The reason all the problems came up was because the DNS for the hosting service changed.  I have been told that the root of my hosting account is "/" now.  Please let me know if you see something I didn't modify correctly.

config.php:

Code: Select all

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

#Document root as seen from the webserver.  No slash at the end
#If page is requested with https use https as root url
#e.g. http://blah.com
$config['root_url'] = 'http://www.winyahrivers.org';
if(isset($_SERVER['HTTPS']) && $_SERVER['HTTPS']=='on')
{
$config['root_url'] = str_replace('http','https',$config['root_url']);
}

#Path to document root. This should be the directory this file is in.
#e.g. /var/www/localhost
$config['root_path'] = '';

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

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

#Where are uploaded files put?  This defaults to uploads.
$config['uploads_path'] = 'uploads';

#Where is the url to this uploads directory?
$config['uploads_url'] = $config['root_url'] . '/uploads';

Note:  I just tried changing the path of document root to:

Code: Select all

#Path to document root. This should be the directory this file is in.
#e.g. /var/www/localhost
$config['root_path'] = '/';

and I get all sorts of smarty errors showing at the top of the site's index page.

[alby]

Ted, you have the right idea.  The reason all the problems came up was because the DNS for the hosting service changed.  I have been told that the root of my hosting account is "/" now.  Please let me know if you see something I didn't modify correctly.

run install/index.php and in step 5 unchecked create tables and samples.
This re-create correct url/path config.php

Alby

[quartney]

YAY!!!

I ran the install without creating tables, cleared the cache, and everything is working now.

Thank you so much, Alby, for your patience!!!  And thanks Ted & Mark for your help, too.

Here are the correct settings:

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

#Document root as seen from the webserver.  No slash at the end
#If page is requested with https use https as root url
#e.g. http://blah.com
$config['root_url'] = 'http://www.winyahrivers.org';
if(isset($_SERVER['HTTPS']) && $_SERVER['HTTPS']=='on')
{
$config['root_url'] = str_replace('http','https',$config['root_url']);
}

#Path to document root. This should be the directory this file is in.
#e.g. /var/www/localhost
$config['root_path'] = '/home/content/w/r/k/wrk/html';

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

#Where do previews get stored temporarily?  It defaults to tmp/cache.
$config['previews_path'] = '/home/content/w/r/k/wrk/html/tmp/cache';

#Where are uploaded files put?  This defaults to uploads.
$config['uploads_path'] = '/home/content/w/r/k/wrk/html/uploads';

#Where is the url to this uploads directory?
$config['uploads_url'] = $config['root_url'] . '/uploads';

[oliverseddon]

I was having similar problems with my CMSMS after migrating from the test server to the live one, and through trial and error I discovered the Module Manager and Modules threw up errors saying the modules directory needed it's permissions changing to 777. Having checked the permissions 15 times I realised they were definately set to the correct 777 and tried uploading each module one at a time and still no change. I was going to run a fresh install and copy over the DB when I realised the install was showing my Uploads and Uploads/Images folder's needed CHMODing to 777, which I did and discovered that stopped Module Manager and Modules from displaying the permissions error. So the permissions check for the Modules must be connected to the uploads directory permissions check, strange but true.

Hope this helps others out there.