https://www.machform.com/forums/ MachForm Community Forums Topic: Feature Request: Modify MySQL Server display on Errors en Sun, 15 Nov 2026 23:26:04 +0000 https://www.machform.com/forums/topic/feature-request-modify-mysql-server-display-on-errors#post-11299 Thu, 27 Jan 2011 14:18:35 +0000 yuniar 11299@https://www.machform.com/forums/ <p>Thanks for the feedback on this. We should get this cleaned within the next update. </p> https://www.machform.com/forums/topic/feature-request-modify-mysql-server-display-on-errors#post-11298 Thu, 27 Jan 2011 05:52:11 +0000 kwbrayton 11298@https://www.machform.com/forums/ <p>Just happened to call up a form today against the MySQL Server that had been taken down for maintenance. When the MachForms attempted to connect to the server, it throw the following error message: </p> <p>Could not connect: Can't connect to MySQL server on 'XXX.XXX.XXX.XXX' (10060)PHP Warning: mysql_connect() [function.mysql-connect]: Can't connect to MySQL server on 'XXX.XXX.XXX.XXX' (10060) in D:\Inetpub\Public\mf\includes\db-core.php on line 11</p> <p>My concern about this message is that this message displays both the DB_HOST value and the location of the db-core-php file. These seem like useful bits for hackers. It might be nice to be able to suppress revealing all this detail by turning off error reporting and/or crafting less revealing messages. </p> <p>As an example, I've replace the function connect_db() in db-core.php with this code:</p> <pre><code>function connect_db(){ $link = @mysql_connect(DB_HOST, DB_USER, DB_PASSWORD); /* or die(&#39;Could not connect: &#39; . mysql_error()); */ if(!$link) { echo &quot;ERROR: Cannot connect to database. Please try again later!&quot;; exit; } mysql_select_db(DB_NAME) or die(&#39;Could not select database&#39;); mysql_query(&quot;SET NAMES utf8&quot;); return $link; }</code></pre>