Please help - can't open store

[Kjolebutikken]

Hi,

I was testing to log into my store to see what would happen and how it works. I might have used a wrong password for the "testcostumer". This might be the reaseon.

When I pressed the continue button, the whole shop "dissapeard". I only get a totally white page when I try to open my site. I get no errors, only a white page. So I can't access the shop. However I can access admin.

 

Somebody know what I have to do and in what file. I have backup, but it would be nice if I could know how to fix this if it happens again, and I would prefer that before uploading the whole store again.

 

Please answer if somebody can give me a hint:-)

 

This is the url to my store:

http://www.kjolebutikken.com/oscdemo1/index.php

 

Best regards

Kjolebutikken

[masat]

Not much to go on but go look at your site error log. It will probably tell you exactly where the trouble is at. My guess is something in application_top.php or maybe header.php.

 

I can almost guarantee you will find a syntax error there somewhere.

[Kjolebutikken]

Not much to go on but go look at your site error log. It will probably tell you exactly where the trouble is at. My guess is something in application_top.php or maybe header.php.

 

I can almost guarantee you will find a syntax error there somewhere.

 

Hi, thanks for answering. Still can't opne my site so I'm a bit stressed.

Where can I find this error log? Is it on my controlpanel on my webhotel? I found something called php error messages. This is in "off" position.

 

Thanks

Kjolebutikken

[MaBiSmAd]

This may or may not help, but it is something you can try -

 

The page that is output contains the 1st few lines of HTML that is sent by index.php (specifically up through the title.) There is a line that switches to SSL (preusumably when you logged in as a customer your configuration says to use SSL, but this is not configured properly or is not working.) You can try the following and it might be a good idea to search the forum for problems about blank page and SSL, but try this -

 

In index.php find the following line -

<base href="<?php echo (($request_type == 'SSL') ? HTTPS_SERVER : HTTP_SERVER) . DIR_WS_CATALOG; ?>">

and temporarily change it to -

<base href="<?php echo HTTP_SERVER . DIR_WS_CATALOG; ?>">

[Kjolebutikken]

This may or may not help, but it is something you can try -

 

The page that is output contains the 1st few lines of HTML that is sent by index.php (specifically up through the title.) There is a line that switches to SSL (preusumably when you logged in as a customer your configuration says to use SSL, but this is not configured properly or is not working.) You can try the following and it might be a good idea to search the forum for problems about blank page and SSL, but try this -

 

In index.php find the following line -

<base href="<?php echo (($request_type == 'SSL') ? HTTPS_SERVER : HTTP_SERVER) . DIR_WS_CATALOG; ?>">

and temporarily change it to -

<base href="<?php echo HTTP_SERVER . DIR_WS_CATALOG; ?>">

 

Thank you so much for aswering. I tried your suggestion, but I'm afraid it did not fix the problem.

Have tried to replace all files with my backup also, but the page is still white. I have got message that other peole can open my page and can create account, but they say the login page is white. I have white all over, cannot even open the site.

 

This problem seems to be only the folder/directory which contains my shop. I have another testshop, all compeletly clean standard oscommerce on the same server. This I can open. All oter files in my toor I can open, but not my shop. Id anobody would like to try, here is the url to my shop:

 

http://www.kjolebutikken.com/oscdemo1/index.php

 

I find it strange that uploading backup of the whole shop (oscdemo1) did not fix this. This makes my wonder if there is something wrong with the databaseconnecion. That the failed login I did caused some error in the database??? I don't know much about this, so I'm only thinking loud here.

 

Also it's strange that others can enter the shop, and not me.

 

I also suddenly got some error messages when logging into admin, something about safe mode restrictions and sessions.php. This I fixed. Found an answer to this problem in the forum. This was about the application_top.php files and changing E_ALL & ~E_NOTICE to E_ALL & ~E_NOTICE & ~E_WARNING, and then empty the sessions table in my database. Did this, the errormessages dissapeared, but the page is still only white.

 

Please anser to this if you have any more suggestions.

Would be very happy if I could be able to work with my site during my christmas holiday.

Merry Christmas to all of you:-)))

Thanks a lot guys:-)

Kjolebutikken

[Jan Zonjee]

In Safari the index page is white, it complains about an incorrect reply from the server. No clue what you can do about it.

 

However, if I connect to that page with curl I can retrieve the html of the page and it contains a warning of osC and a fatal error of PHP:

Warning: I am able to write to the configuration file: /customers/kjolebutikken.com/kjolebutikken.com/httpd.www/oscdemo1/includes/configure.php. This is a potential security risk - please set the right user permissions on this file.

<b>Fatal error</b>:  Cannot redeclare tep_update_whos_online() (previously declared in /customers/kjolebutikken.com/kjolebutikken.com/httpd.www/oscdemo1/includes/functions/whos_online.php:14) in <b>/customers/kjolebutikken.com/kjolebutikken.com/httpd.www/oscdemo1/includes/functions/whos_online.php</b> on line <b>13</b>

[MaBiSmAd]

In Safari the index page is white, it complains about an incorrect reply from the server. No clue what you can do about it.

 

However, if I connect to that page with curl I can retrieve the html of the page and it contains a warning of osC and a fatal error of PHP:

Warning: I am able to write to the configuration file: /customers/kjolebutikken.com/kjolebutikken.com/httpd.www/oscdemo1/includes/configure.php. This is a potential security risk - please set the right user permissions on this file.

<b>Fatal error</b>:  Cannot redeclare tep_update_whos_online() (previously declared in /customers/kjolebutikken.com/kjolebutikken.com/httpd.www/oscdemo1/includes/functions/whos_online.php:14) in <b>/customers/kjolebutikken.com/kjolebutikken.com/httpd.www/oscdemo1/includes/functions/whos_online.php</b> on line <b>13</b>

 

My only next best guess is that the session cache is messed up (possibly shared between multiple oscommerce installations.) Perhaps delete the files in the cache.

[Kjolebutikken]

My only next best guess is that the session cache is messed up (possibly shared between multiple oscommerce installations.) Perhaps delete the files in the cache.

 

Thanks for your answers. I would like to try that, but where do I find the files in the cache? I went into admin and found two lines under cache:

 

Use Cache (is set to false)

Cache directory /tmp/

 

Do you mean to empty the cache directory /tmp/ ?

I can't find the /tmp/ directory. Do you know where it is supposed to be?

 

Thank you:-))

Kjolebutikken

[Jan Zonjee]

Apart from the obvious fatal error because tep_update_whos_online is found twice in the code that is loaded for index.php the NSURLErrorDomain:-1011 that Safari displays has to do with gzip compression. I found a good explanation on the bug in this page (blog by Jason Clark).

 

Basically, the browser problem is the fact that the server tells the browser that the content it is sending is gzipped, while in fact it sends text.

 

Using this command in curl

curl -i -H "Accept-Encoding: gzip" http://www.kjolebutikken.com/oscdemo1/index.php

(see the link above) gives the following output (as you can see, text instead of binary gibberish):

HTTP/1.1 200 OK
Date: Sat, 24 Dec 2005 22:28:01 GMT
Server: Apache
X-Powered-By: PHP/4.4.1
Set-Cookie: osCsid=faec6cd5b8f4442cdb55b89c7c343af3; path=/oscdemo1/; domain=www.kjolebutikken.com
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Content-Encoding: gzip
Vary: Accept-Encoding
Connection: close
Transfer-Encoding: chunked
Content-Type: text/html

<!-- Page layout by Simple Template System (STS) v2.01 on osCommerce 2.2-MS2 - http://www.diamondsea.com/sts/ -->
<!-- Using Template File [includes/sts_template.html) -->
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<title>Kjolebutikken</title><base href="http://www.kjolebutikken.com/oscdemo1/">
.
.
.
etcetera

This is something for the ISP. Probably they can't be reached till Tuesday.

[Kjolebutikken]

Apart from the obvious fatal error because tep_update_whos_online is found twice in the code that is loaded for index.php the NSURLErrorDomain:-1011 that Safari displays has to do with gzip compression. I found a good explanation on the bug in this page (blog by Jason Clark).

 

Basically, the browser problem is the fact that the server tells the browser that the content it is sending is gzipped, while in fact it sends text.

 

Using this command in curl

curl -i -H "Accept-Encoding: gzip" http://www.kjolebutikken.com/oscdemo1/index.php

(see the link above) gives the following output (as you can see, text instead of binary gibberish):

HTTP/1.1 200 OK
Date: Sat, 24 Dec 2005 22:28:01 GMT
Server: Apache
X-Powered-By: PHP/4.4.1
Set-Cookie: osCsid=faec6cd5b8f4442cdb55b89c7c343af3; path=/oscdemo1/; domain=www.kjolebutikken.com
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Content-Encoding: gzip
Vary: Accept-Encoding
Connection: close
Transfer-Encoding: chunked
Content-Type: text/html

<!-- Page layout by Simple Template System (STS) v2.01 on osCommerce 2.2-MS2 - http://www.diamondsea.com/sts/ -->
<!-- Using Template File [includes/sts_template.html) -->
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<title>Kjolebutikken</title><base href="http://www.kjolebutikken.com/oscdemo1/">
.
.
.
etcetera

This is something for the ISP. Probably they can't be reached till Tuesday.

 

Thanks, yes It's just my luck if I can't fix this until tuesday:-(

I wonder if the two tep_update_whos_online's is found because I have installed osc twize on the same server? I did this so that I could test everything out one one first, and if it worked, I did the same with the other, if it failed, I copied the "good" files from the one working to the one just failing. This way I have been able to "stay out of trouble" most of the time:-) But maybe I shold have deleted one of them before testing the login function. Maybe The system could not handle that?

 

What you said about gzip, I'm sorry, but I'm a bit new to this so I did not understand much, but I can tell you that I asked my host if they supported gzip cpmpression, and they answered that they did, so in admin I did enable gzip compression when I installed oscommerce.

 

Does this information say anything to you?

Is there anything else I can try in the meantime if I cannot get in contact with my host until tuesday?

 

Thanks

Kjolebutikken

[Jan Zonjee]

I wonder if the two tep_update_whos_online's is found because I have installed osc twize on the same server? I did this so that I could test everything out one one first, and if it worked, I did the same with the other, if it failed, I copied the "good" files from the one working to the one just failing. This way I have been able to "stay out of trouble" most of the time:-) But maybe I shold have deleted one of them before testing the login function. Maybe The system could not handle that?

No it means the function is found twice in the files that are loaded. You can only "declare" a function once.

 

What you said about gzip, I'm sorry, but I'm a bit new to this so I did not understand much, but I can tell you that I asked my host if they supported gzip cpmpression, and they answered that they did, so in admin I did enable gzip compression when I installed oscommerce.

So you changed it to gzip compression is false and it didn't help? Or are you waiting for the problem to go away by itself?

[Kjolebutikken]

No it means the function is found twice in the files that are loaded. You can only "declare" a function once.

 

So you changed it to gzip compression is false and it didn't help? Or are you waiting for the problem to go away by itself?

 

Hi JanZ, Thank you for helping me:-) I can see my site again:-)))

Yes, you was absolutely right. It was the gzip that was the problem. I did'nt see it and I know now that I should have, but I did not suspect that this could be a problem, because I was told this would be a "good" thing:-) My site would work faster and it would be alright if my host supported it. So when my host answered that they supported it, I turned it on, but I did this under installation, so I don't understand why the problem came just now when I tried the login function. But anyway, thank you so much for enlighten me. I'm just so releived that I can see my site again:-))) Do you know an alternative to gzip compression that will make the site go faster, since I've now disabled it?

 

Thank you - thank you all guys for the help I received about this:-)

And Merry Christmas to all!!!

 

 

Best regards

Kjolebutikken

[MaBiSmAd]

So when my host answered that they supported it, I turned it on, but I did this under installation, so I don't understand why the problem came just now when I tried the login function. But anyway, thank you so much for enlighten me. I'm just so releived that I can see my site again:-))) Do you know an alternative to gzip compression that will make the site go faster, since I've now disabled it?

 

Thank you - thank you all guys for the help I received about this:-)

And Merry Christmas to all!!!

Best regards

Kjolebutikken

 

Glad you found and fixed your problem.

 

A lot of people at hosting companies don't know and don't think they need to check out information they give to you. Gzip is a function available to PHP, but it must be enabled. Someone else may know, but since this is part of the PHP core functions, there is probably not an alternative.

 

You can check if this is enabled by creating a simple .php file with a phpinfo(); statement. Create a file with the following code and put this file onto your web site and browser to it -

<?PHP
phpinfo();
?>

 

If gzip is present and enabled, there will be a listing for it. If it is not enabled, request your hosting company to enable it (in the php.ini file.)

[MaBiSmAd]

Glad you found and fixed your problem.

 

A lot of people at hosting companies don't know and don't think they need to check out information they give to you. Gzip is a function available to PHP, but it must be enabled. Someone else may know, but since this is part of the PHP core functions, there is probably not an alternative.

 

You can check if this is enabled by creating a simple .php file with a phpinfo(); statement. Create a file with the following code and put this file onto your web site and browser to it -

<?PHP
phpinfo();
?>

 

If gzip is present and enabled, there will be a listing for it. If it is not enabled, request your hosting company to enable it (in the php.ini file.)

 

I mis-wrote in the last post. Gzip is part of PHP but it cannot be enabled/disabled (except perhaps by compiling PHP without it.) Therefore, the problem you experienced is probably due to a bug in the ocscommerce code that uses gzip or due to an incompatible change or contribution that you might have added.

[Kjolebutikken]

Glad you found and fixed your problem.

 

A lot of people at hosting companies don't know and don't think they need to check out information they give to you. Gzip is a function available to PHP, but it must be enabled. Someone else may know, but since this is part of the PHP core functions, there is probably not an alternative.

 

You can check if this is enabled by creating a simple .php file with a phpinfo(); statement. Create a file with the following code and put this file onto your web site and browser to it -

<?PHP
phpinfo();
?>

 

If gzip is present and enabled, there will be a listing for it. If it is not enabled, request your hosting company to enable it (in the php.ini file.)

 

Hi MaBiSmAd,

Thank you so much for enlighten me:-)

I did as you said and created a testfile and ran it through my browser and I got a error 403 and message that I was not allowed to read this file.

I will contact my host and ask them to enable gzip in my php.ini and then try to enable gzip in my admin again:-)

Thank you very much for your help:-)

Best regards

Kjolebutikken