Latest News: (loading..)
Search the Community
Showing results for tags 'ms2'.
Found 3 results
eeto posted a topic in Installation and ConfigurationHi. I've got a problem with an ancient osCommerce installation which I believe is MS2. It's old and creaky, but it's been at least functional for a very long time. Now I ran into big problems when I tried to get our new SSL certificate working with this installation. I can get it to work alright, different browsers tell me that the site is secure. The problem is that when SSL works, customers can't log in. An attempt to login only directs the user back to the login page with no error message. Trying to use a wrong password does result in a password / user mismatch error, though. I know this version of osCommerce is very old, but updating is a pain and we're currently planning on building a new shop from the ground up. We'd just need to get SSL working for however long it takes for us to get a brand new site up and running. Here's what I have in my catalog's configure.php right now. This works, customers can log in ok, but SSL is off. define('HTTP_SERVER', 'http://www.mydomainhere.com'); // eg, http://localhost - should not be empty for productive servers define('HTTPS_SERVER', 'https://www.mydomainhere.com'); // eg, https://localhost - should not be empty for productive servers define('ENABLE_SSL', false); // secure webserver for checkout procedure? define('HTTP_COOKIE_DOMAIN', '.mydomainhere.com'); define('HTTPS_COOKIE_DOMAIN', '.mydomainhere.com'); define('HTTP_COOKIE_PATH', '/shop/'); define('HTTPS_COOKIE_PATH', '/shop/'); define('DIR_WS_HTTP_CATALOG', '/shop/'); define('DIR_WS_HTTPS_CATALOG', '/shop/'); This is how I tried to get it to work. Site appears secure, login breaks. define('HTTP_SERVER', 'https://www.mydomainhere.com'); // eg, http://localhost - should not be empty for productive servers define('HTTPS_SERVER', 'https://www.mydomainhere.com'); // eg, https://localhost - should not be empty for productive servers define('ENABLE_SSL', true); // secure webserver for checkout procedure? define('HTTP_COOKIE_DOMAIN', '.mydomainhere.com'); define('HTTPS_COOKIE_DOMAIN', '.mydomainhere.com'); define('HTTP_COOKIE_PATH', '/shop/'); define('HTTPS_COOKIE_PATH', '/shop/'); define('DIR_WS_HTTP_CATALOG', '/shop/'); define('DIR_WS_HTTPS_CATALOG', '/shop/'); With the SSL configuration above osCsid also seems to stay in the URLs. Refreshing the page doesn't do anything to it. If I manually delete the automatically appearing osCsid from the page url and load up login.php by itself, login works. I also noticed that if I login as a customer using the non-SSL configuration and then log out and switch to the configuration that enables SSL, I can log in again as long as the old cookies are present. If I erase the cookies, osCsid appears in the address bar and login breaks. I'm not really familiar with SSL certificates. All I know is that this is from GeoTrust and the domain matches (www. included) with this site. But I guess the certificate itself is not the problem, since it does appear to work. Here are my settings from the admin side: Force cookies = false (setting this to true only gives the osC error page about enabling cookies) Check SSL session ID = true (false when SSL is off) Check user agent = false Check IP address = false Prevent spider sessions = true Recreate session = true In the error log I'm getting a lot of stuff like this. Could this be a part of the problem? The PHP version on the server is 5.3.29, I thought it's 5.4 that is incompatible? PHP Deprecated: Function session_is_registered() is deprecated PHP Deprecated: Function session_register() is deprecated PHP Deprecated: Function session_is_registered() is deprecated PHP Deprecated: Function eregi() is deprecated Any ideas? Any help would be appreciated, I've googled for hours without finding a solution. Thanks.
I am new to the board, so please let me know if I posted in the wrong area. My friend has the following- running the following- PHP 5.2,oscom version 2.2 ms2 He had been told that if he does not upgrade his code or PHP by this week they are going to shutdown his site. Is there a simple process to upgrade? Do we just upgrade PHP to 5.6 or 7? Do we just update our oscom version? Is there a lot of issues with upgrading? Should I just toss the site and move all the products over to something new?
It seems like every other question posted nowadays is about how to upgrade an older version of oscommerce and the op usually references the official version. This post is meant to provide a quick reference for how to convert an older shop to the current, recommended, one. First, the version that should be used is commonly called the Bootstrap, BS or Responsive version. It can be located here. One should not use the official version. The official version can be installed via the hosts control panel so it is easy to think that is the one to use - it is not. Since the BS version is not directly compatible with other versions, the following steps will be needed: Install the BS version into a new location Convert the database. See this thread for help with that. Install whatever addons the site needs. You need to be sure the addon will work with the BS version. This thread mentions specific ones but there are many others that will work. If in doubt, ask in the support thread for the addon in question. If you intend to use paypal, then install the Paypal App. At this point you should have a working shop. Test it thoroughly, especially the payment and shipping modules, before going live with it. When you are ready to go live, Mark your current shop as down for maintenance ( a simple index.html file is fine for this purpose ). Make a backup of the current shops database and files. Convert the database to the BS version. Replace all of the files with the new shops files. Edit the configure files so they work as the live shop. Remove the blocking page. If everything has gone correctly, the conversion should be complete.