Install failure "Hawaii"

[Dr.CSS]

Tried to install in a folder that had a previous version, I deleted everything in it, empty folder, uploaded new CMSMS.

New config.php everything set with the correct permissions, etc.

Start setup, nice new interface, can't get past first page, error in screen shot below.

What this means I have know idea never saw this check before, now what.

Running on the same sever that all my others are on, haven't even gotten to the DB.

[attachment deleted by admin]

[alby]

Tried to install in a folder that had a previous version, I deleted everything in it, empty folder, uploaded new CMSMS.
....
Running on the same sever that all my others are on, haven't even gotten to the DB.

Code: Select all

Name			Default	Changeable		Changelog
max_input_time		"-1"	PHP_INI_PERDIR	Available since PHP 4.3.0

PHP_INI_PERDIR: Entry can be set in php.ini, .htaccess or httpd.conf

If you update php with old php.ini, max_input_time variable is missing and -1 is default.

If you have root/admin access insert in php.ini:
max_input_time=60
if not add/create .htaccess in CMSMS root directory the row:
php_value  max_input_time  60

Alby

[Dr.CSS]

can only FTP or go to amin panel thru host.

Does that help?

[alby]

can only FTP or go to amin panel thru host.

I don't know your host.
Have you admin panel for php configuration?
If yes add or change the value of max_input_time to 60
If no create a filename .htaccess, add: php_value  max_input_time  60 , save and put, via FTP, in CMSMS root directory

Alby

[Pierre M.]

Hello,
welcome to "Hawaii" !

I'd like to try it. But I have the same problem with "max input time". I could have posted the same screenshot : min 45s, recommend 60s, You have "-1". All other tests are green.

I just tried your fix (a one line .htaccess with php_value max_input_time 60), and now it is HTTP 500 error.

If my hoster's "-1" setting means "unlimited", I'm above the required value and even above the recommended value, so the test should pass and I think this is a bug. Unfortunately, the tracker, as the wiki, doesn't want to let me in with my forum account to file that new bug.

Please fix this test in install/install.php if I'm right. 0.13 runs very well, True 1.0 is so near

PM

[Elijah Lofgren]

This should be fixed in SVN: http://viewsvn.cmsmadesimple.org/viewsv ... 2&view=rev
CMSMS 1.0 Beta2 should have this fix included.

If you want to can download the fixed install.php
http://viewsvn.cmsmadesimple.org/viewsv ... iew=markup

[Pierre M.]

I downloaded the "fixed" install.php and I had the same problem

I'd rather wait for beta2 to test Hawaii.

Thanks for you answer.

[Dr.CSS]

That file worked!!! 

It's looking real good, better default content, nice explanations. Cool new layout/Design.

Just one question, isn't all the old stuff in DB gone when you do a fresh install into a folder that had older version in it, all folder/files were deleted, using the old DB, told it to write over create tables?

An old news item shows under the News on all pages.

YEAH

[Pierre M.]

Just tried to install 1.0b2 : OK
There is no more "-1" problem. Thanks for the fix, thanks for this nice simple product.

My first feedback about 1.0b2 :

-everything ran smoothly (as with 0.13), except "Installing modules...[done]" and "Index Search...[done]" at the end of step 5. They took some time. May be my host was just busy. It works, it was just slow.

-may be a inconvenience : with 0.13, the built-in good looking URLs were on by default ("/index.php/mypage", "/index.php/europe/france", and so on). With 1.0b2, the sample content has "?page=name" as in the pre-0.13 old days. I prefer the "/america/argentina" scheme, I think the good looking URLs should be on again.

PM

[Elijah Lofgren]

-may be a inconvenience : with 0.13, the built-in good looking URLs were on by default ("/index.php/mypage", "/index.php/europe/france", and so on). With 1.0b2, the sample content has "?page=name" as in the pre-0.13 old days. I prefer the "/america/argentina" scheme, I think the good looking URLs should be on again.

We had so many problems with people using CMSMS on IIS that we turned pretty URLs off by default. It's better to have CMSMS work with ugly URLs, than to have errors. We just need to let people know that there is an easy way to get nicer URLS (as long as host supports it). 

[Pierre M.]

@Elijah : thank you for your explaination.

Another suggestion : the install could be webserver dependent so pretty URLs are activated by default if supported.

Or better : desactivated only if not supported

//End of installer :
if not (webserver is "IIS" or webserver is "even worse")
{
//turn on pretty URLs
}

It would be really cool to have this. (but it is just my opinion)
PM

[Elijah Lofgren]

@Elijah : thank you for your explaination.

Another suggestion : the install could be webserver dependent so pretty URLs are activated by default if supported.

Or better : desactivated only if not supported

//End of installer :
if not (webserver is "IIS" or webserver is "even worse")
{
//turn on pretty URLs
}

It would be really cool to have this. (but it is just my opinion)
PM

I think we'd still have problems detecting things correctly. I think people on Apache hosts have even had this problem.
I think it's fine to ask people to change 1 line in config.php if they want pretty URLS.