Install Stuck On Step Two

[sykesa]

Hello,

 

Im trying to install a fresh copy of OS Commerce on my site. I had to use the Register GLobals patch all seems good but when you get to step two of the install select "Sample Data/Auto Configure" when you hit continue it doesn't go to step three it just reloads step 2 any ideas?

 

Andrew

[♥Vger]

Install gets stuck on page 2

---------------------------

The most common cause for installation getting stuck in step 2

is that most recent PHP installations have register_long_arrays = OFF

This needs to be turned to ON in the php.ini file (you will need to

stop and restart your server to get this change to take effect.)

 

Vger

[mikeque]

I have followed all the suggestions.

 

in php.ini, I have set the following:

register_globals = On

register_long_arrays = On

 

in .htaccess I have set these up:

php_value register_globals 1

php_flag register_globals on

php_flag register_long_arrays on

 

I have restarted my machine (Mac OSX 10.4).

 

And still cannot get to Step to to begin the set up. I get no errors, just can't get past he New Setup page.

Any other ideas???

 

Thanks

 

 

Install gets stuck on page 2

---------------------------

The most common cause for installation getting stuck in step 2

is that most recent PHP installations have register_long_arrays = OFF

This needs to be turned to ON in the php.ini file (you will need to

stop and restart your server to get this change to take effect.)

 

Vger

[mikeque]

I have followed all the suggestions.

 

in php.ini, I have set the following:

register_globals = On

register_long_arrays = On

 

in .htaccess I have set these up:

php_value register_globals 1

php_flag register_globals on

php_flag register_long_arrays on

 

I have restarted my machine (Mac OSX 10.4).

 

And still cannot get to Step to to begin the set up. I get no errors, just can't get past he New Setup page.

Any other ideas???

 

Thanks

 

Not sure why, but after restarting the computer a couple more times, it finally works. Maybe it was a browser cache thing. Who knows.

 

So doing all of the above does fix this problem (at least in my case)