trying to install 1.7 - fails on checksum

[Peciura]

Try install on local host and than move site to server.

[replytomk3]

I'm getting help on the IRC. You need to

1) Install CMSMS on XAMPP to see how it works. And also to see that it DOES WORK.

2) And call your hosting company for tech support. Now's the time to find out how good your hosting company is.

You might hear more on the forum and I on the IRC. But this looks nothing like a CMSMS fault. Get your tech support on this issue. Ask them if they have any PHP limitations like open sessions, etc.


Forward this page to tech support: http://wiki.cmsmadesimple.org/index.php/User_Handbook/Installation/Requirements

Especially:
Linux/Unix
Apache 2
Working PHP sessions
php.ini settings


In addition, you will have to post here PHP.ini settings, and .htaccess contents. Some stupid things like DENY ALL in htaccess can lead to bewildering problems.

[davout]

I have another php CMS product 'OCPortal' working fine on the same host, so I doubt whether it's a hosting issue.

I have previously successfully deployed CMS-MS on my local Windows Vista laptop under XAMPP. But that's Vista and my Java host is Linux.

This is my second attempt at trying to get CMS-MS working on a java host.  The lack of debug on the install process is woeful.  Sorry, but I can't afford to waste anymore time on a product which has such poor logging/diagnostics.

[Dr.CSS]

Is this failing each time when you try to checksum the files?...

I've set up many sites and have never used the checksum function it says I can but I just skip it and continue on my way installing...

[replytomk3]

There IS debug

http://forum.cmsmadesimple.org/index.php/topic,34215.msg161429.html#msg161429

Getting help requires patience and answering questions. For example, I still don't know what you refer to by "java host".

And I have seen dozens of CMSMS installs on a dozen different hosting companies. So I as easily say that it is your hosting problem, and CMSMS's fault.

PHP.ini?? .htaccess?? contents

There are also server logs which give information even if CMSMS did not.

If you think that this is a waste of time (a second attempt ON THE SAME HOSTING) then wait until you run into big problems with a website.

[davout]

Please refer to the earlier trail of posts....

If I click on the 'continue' button the install app immediately returns to the initial 'select a language' page.

[davout]

Running...

http://www.essays-in-software.com/skap/ ... hp?debug=1

... has no effect. There is no debug output

[Dr.CSS]

If your server fits all the requirements for this and all the permissions are correct and all else looks good but when you try cmsms/install/ and it doesn't automatically run the index.php file in that folder well if I ran into a server that didn't run index.php from that link I would find another host...

[rab]

Interesting! I just experienced same (similar) problems while both installing new (v1.7) and upgrading from 1.6.6 to 1.7 on different sites. The initial install or upgrade file started out fine, but as soon as I got to the 2nd page (checksum verification) and clicked on Continue, my browser tried to download an index.php file instead of continuing. This happened:

• * in each of 3 browsers (FF3.6, IE8 and Chrome)
• * when I was installing new 1.7 or upgrading from 1.6.6 to 1.7
• * whether I uploaded the cmsms.base.tar file via cPanel and extracted it there, or started over and uploaded all extracted files via FileZilla
• * on both production server and desktop
• * even though 1st install page said all tests had passed

Production server is using Linux 2.6.18, Apache 2.2.15 and PHP 5.3.2.
Desktop uses Windows XP, Apache 2.2.15 and PHP 5.3.2.

Very weird, and I'm still working on it.

[davout]

I really don't understand this response.

Another correspondent to this message thread has replicated the problem I've reported, in essence showing the issue to be a problem with the CMs-MS install,  and yet you still insist this a problem with the hosting service??!!?

I'm struggling to understand such an arrogant approach to product support.

[davout]

I received a message from Peciura suggesting that I run a phpinfo() command to find out all the php settings. The output is attached as a file. The file is in HTML but I've had to revise the file name to use a txt extension because the attachment facility on this forum site doesn't accept html files.

Then he suggested that I append the following commands at the very start of the 'install/index.php' file...

Code: Select all

<?php
ini_set('session.use_cookies', 1); 
ini_set('session.gc_maxlifetime',123456);

...  but this had no affect. The problem remains the same.

[alby]

Have you ask to your provider for server error logs?
You have PHP with FastCGI method, certainly you have more informatons in logs.

Alby

[owr_bgld]

I'm struggling to understand such an arrogant approach to product support.

so what? read the topics - your problem IS NOT CMSms - your Problem is at the provider - talk to him in this way.

..... but when you try cmsms/install/ and it doesn't automatically run the index.php file in that folder well if I ran into a server that didn't run index.php from that link I would find another host...

didn't you understand this answer? a normal host runs index.php automatically, your HOST DOES NOT, so it's a problem with your provider.


PS: No I'm not mod or admin here - I'm normal user who also sometimes wants to get help

[rab]

Just completed a lot of playing around and testing and found the solution - at least for me.

I added a .htaccess file to the public_html folder with the following contents:

Code: Select all

# Install CMSMS 1.7 fix
php_value error_reporting 22527

Installation of CMSMS 1.7 then ran without problems.

In defense of the CMSMS Support Team, this fix is listed in Calguy's post announcing v1.7's release, so it is/was not a CMSMS problem. Not sure that necessarily warranted some of the unhelpful and unfriendly responses in this thread, but if this fix works for you, I'd suggest you just forget about it and move on to developing your site.

[alby]

but if this fix works for you, I'd suggest you just forget about it and move on to developing your site.

No, the case of davout is a issue in host configuration.
Sufficient read the relative error log (I sent a PM).

Alby