mav1959uk Posted November 5, 2005 Posted November 5, 2005 My web shop has gone bit pear shaped www.mkwheatingcontrols.co.uk as can be seen none of my images and frames can be seen. Do you think I need to reinstall. Will 2.2 go on without a problem if I copy to my public html. Thanks in advance
Jack_mcs Posted November 5, 2005 Posted November 5, 2005 It looks like your configure file is not set up correctly. Try posting it here, minus the sensitive data, so someone can look at it. Jack Support Links: For Hire: Contact me for anything you need help with for your shop: upgrading, hosting, repairs, code written, etc. All of My Addons Get the latest versions of my addons Recommended SEO Addons
mav1959uk Posted November 5, 2005 Author Posted November 5, 2005 It looks like your configure file is not set up correctly. Try posting it here, minus the sensitive data, so someone can look at it. Jack Thanks Jack for your reply. Is that the configuration.php file in my administration section. How do I remove sensitive data. Thanks
AlanR Posted November 5, 2005 Posted November 5, 2005 Look at the source view: <!doctype html public "-//W3C//DTD HTML 4.01 Transitional//EN"> <html dir="LTR" lang="en"> <head> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> <title>Heating Controls</title> <base href="https://mkwheatingcontrols.co.uk/"> You don't seem to have any form of ssl installed so set the catalog/includes/configure.php file like so: (first few lines here) // Define the webserver and path parameters // * DIR_FS_* = Filesystem directories (local/physical) // * DIR_WS_* = Webserver directories (virtual/URL) define('HTTP_SERVER', 'http://mkwheatingcontrols.co.uk/'); // eg, http://localhost - should not be empty for productive servers define('HTTPS_SERVER', 'http://mkwheatingcontrols.co.uk/'); // eg, https://localhost - should not be empty for productive servers In other words, make the HTTPS_SERVER the same as the HTTP_SERVER. This is a pretty common problem, something's gone a little wonky on the server. They usually sort it out after a while. Local: Mac OS X 10.5.8 - Apache 2.2/php 5.3.0/MySQL 5.4.10 • Web Servers: Linux Tools: BBEdit, Coda, Versions (Subversion), Sequel Pro (db management)
mav1959uk Posted November 6, 2005 Author Posted November 6, 2005 Look at the source view: <!doctype html public "-//W3C//DTD HTML 4.01 Transitional//EN"> <html dir="LTR" lang="en"> <head> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> <title>Heating Controls</title> <base href="https://mkwheatingcontrols.co.uk/"> You don't seem to have any form of ssl installed so set the catalog/includes/configure.php file like so: (first few lines here) // Define the webserver and path parameters // * DIR_FS_* = Filesystem directories (local/physical) // * DIR_WS_* = Webserver directories (virtual/URL) define('HTTP_SERVER', 'http://mkwheatingcontrols.co.uk/'); // eg, http://localhost - should not be empty for productive servers define('HTTPS_SERVER', 'http://mkwheatingcontrols.co.uk/'); // eg, https://localhost - should not be empty for productive servers In other words, make the HTTPS_SERVER the same as the HTTP_SERVER. This is a pretty common problem, something's gone a little wonky on the server. They usually sort it out after a while. Alan Thanks for that, its up and running again. Do I need t o change my http back to https sometime in the future. Regards Malcolm :thumbsup:
AlanR Posted November 6, 2005 Posted November 6, 2005 AlanThanks for that, its up and running again. Do I need t o change my http back to https sometime in the future. Regards Malcolm :thumbsup: You will if you decide to use https for checkout and customer functions in the future. Until then you can just leave it, no problems are caused. It's caused by a server misconfiguration and the techies usually catch it sooner or later. Common problem. Local: Mac OS X 10.5.8 - Apache 2.2/php 5.3.0/MySQL 5.4.10 • Web Servers: Linux Tools: BBEdit, Coda, Versions (Subversion), Sequel Pro (db management)
mav1959uk Posted November 6, 2005 Author Posted November 6, 2005 You will if you decide to use https for checkout and customer functions in the future. Until then you can just leave it, no problems are caused. It's caused by a server misconfiguration and the techies usually catch it sooner or later. Common problem. Thanks Alan, I did email my server people and they restarted before I took your action. Ill keep an eye on things and try to push the server people to resolve the issue. Thanks again :thumbsup:
New 
Recommended Posts
Archived
This topic is now archived and is closed to further replies.