londonismyname Posted June 8, 2016 Share Posted June 8, 2016 Hello, I have read similar problems in here but not this exact issue and none of the other “fixes” help. I just installed osc2.3.4 on a server that is running MYSQL 5.6.30 and PHP 5.5 and it has PHP extension mysqli. The install worked fine but when I go to the front end I get this error above what looks like a fine working site:“Deprecated: mysql_connect(): The mysql extension is deprecated and will be removed in the future: use mysqli or PDO instead in /home/dgirl465/public_html/catalog3/includes/functions/database.php on line 168Warning: mysql_connect(): Headers and client library minor version mismatch. Headers:50548 Library:50630 in /home/dgirl465/public_html/catalog3/includes/functions/database.php on line 168Warning: session_start(): Cannot send session cookie - headers already sent by (output started at /home/dgirl465/public_html/catalog3/includes/functions/database.php:168) in /home/dgirl465/public_html/catalog3/includes/functions/sessions.php on line 97Warning: session_start(): Cannot send session cache limiter - headers already sent (output started at /home/dgirl465/public_html/catalog3/includes/functions/database.php:168) in /home/dgirl465/public_html/catalog3/includes/functions/sessions.php on line 97” The page shows the “sample” products so it must be pulling from the database so I have no idea what's going on here. The admin section gives me similar errors but obviously different pages and line numbers. It also shows me nothing but the errors. PLEASE HELP:-) Link to comment Share on other sites More sharing options...
burt Posted June 8, 2016 Share Posted June 8, 2016 Your PHP was compiled with MySQL 5.5 Your PHP is trying to use MySQL 5.6 Get your host to recompile PHP with the correct MySQL version. Link to comment Share on other sites More sharing options...
MrPhil Posted June 8, 2016 Share Posted June 8, 2016 And if that doesn't fix it, check if you have any add-ons, etc. still using MySQL (rather than MySQLi). Those would need to be fixed if your PHP installation does not have the old (deprecated) MySQL extension any more. Link to comment Share on other sites More sharing options...
londonismyname Posted June 8, 2016 Author Share Posted June 8, 2016 Your PHP was compiled with MySQL 5.5 Your PHP is trying to use MySQL 5.6 Get your host to recompile PHP with the correct MySQL version. The server was MySQL 5.5 and had this same error so I upgraded it to 5.6 to see if it fixed it(but nope). I did not recompile apache and PHP as a 5.5. to 5.6 upgrade is not supposed to need it. Do you still think this is the issue even though it was doing it before? if so I will recompile. Thanks Link to comment Share on other sites More sharing options...
londonismyname Posted June 8, 2016 Author Share Posted June 8, 2016 i recompiled and it's fixed. THANK YOU SOOOO MUCH! Link to comment Share on other sites More sharing options...
rufusking Posted October 28, 2016 Share Posted October 28, 2016 For those folks who are running the newer PHP 7.0 Recompiling will not correct the issue. (Obviously) So the easiest fix is to make a quick adjustment in the code as follows: Find the file: /admin/includes/application_top.php Find the following code: error_reporting(E_ALL & ~E_NOTICE); and replace it with this: error_reporting(E_ALL & ~E_NOTICE & ~E_DEPRECATED); That takes care of the admin section next the production store. Find the file : /includes/application_top.php Find the following code: error_reporting(E_ALL & ~E_NOTICE); and replace it with this: error_reporting(E_ALL & ~E_NOTICE & ~E_DEPRECATED); Save your changes and the deprecated tag warning should go away. This will continue to be a problem and will plague this Store front until all deprecated tags are done away with. Link to comment Share on other sites More sharing options...
♥John W Posted October 28, 2016 Share Posted October 28, 2016 It's also a bad idea to output errors to the screen on a live site. Use an error log for instance ini_set('display_errors', FALSE); ini_set('error_log', 'inludes/catalog_errors.log'); I'm not really a dog. Link to comment Share on other sites More sharing options...
♥14steve14 Posted October 29, 2016 Share Posted October 29, 2016 For those folks who are running the newer PHP 7.0 Recompiling will not correct the issue. (Obviously) So the easiest fix is to make a quick adjustment in the code as follows: Find the file: /admin/includes/application_top.php Find the following code: error_reporting(E_ALL & ~E_NOTICE); and replace it with this: error_reporting(E_ALL & ~E_NOTICE & ~E_DEPRECATED); That takes care of the admin section next the production store. Find the file : /includes/application_top.php Find the following code: error_reporting(E_ALL & ~E_NOTICE); and replace it with this: error_reporting(E_ALL & ~E_NOTICE & ~E_DEPRECATED); Save your changes and the deprecated tag warning should go away. This will continue to be a problem and will plague this Store front until all deprecated tags are done away with. As far as I am aware this only hides the errors, they should really be fixed properly. REMEMBER BACKUP, BACKUP AND BACKUP Link to comment Share on other sites More sharing options...
♥John W Posted October 29, 2016 Share Posted October 29, 2016 Yes, that does only hide errors and I agree errors should be fixed. Notice level errors often indicate a problem that shows something is not working correctly. An unset variable, or a constant that is set twice (doesn't work) error should be corrected. Deprecated errors show you a problem that won't work in future versions. I'm not really a dog. Link to comment Share on other sites More sharing options...
rufusking Posted October 31, 2016 Share Posted October 31, 2016 As far as I am aware this only hides the errors, they should really be fixed properly. Yes, that does only hide errors and I agree errors should be fixed. Notice level errors often indicate a problem that shows something is not working correctly. An unset variable, or a constant that is set twice (doesn't work) error should be corrected. Deprecated errors show you a problem that won't work in future versions. You are correct but my job shouldn't be to rewrite the entire oscommerce platform. Ill leave that to Harald and his crew. This solution only covers it over like you said so that the site is useable as it is with newer PHP and MySQL setups. There is no doubt as these languages evolve the OSC crew will again have to make changes which are very taxing on their labor. Link to comment Share on other sites More sharing options...
Fredi Posted December 8, 2016 Share Posted December 8, 2016 Who can tell what corrections need to do to adjust? There is a short recommendation? Support forum for osCommerce in russian language - from Ashkelon. Support since 2002.Best regards, Fredi Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.