If you're still having errors then your project is not finished yet.
One way would be to do a site-wide find/replace on your files and replace the OR die(mysql_error()) with an @ in front of mysql_error() like so: OR die(@mysql_error()).
Placing an @ in front of a function call suppresses error messages. But use it carefully, this is not always a good solution.
Read this post which links to this article to know if it's a good solution for you.
I would change all OR die() occourrences to a custom error-handling function, then if you get an error you will still know about it without displaying them to users.
Yes, it would take a lot of time, but a good project takes a lot of time.
Check this article to create your own error-handling function and this other one to Enable PHP error logging via .htaccess, they really helped me.
mysql_erroritself is not "showing errors". Does that mean you have a ton ofecho mysql_error()everywhere throughout your code and you want to silence that?mysql_errordoesn't show errors. It returns a string.echoing orprinting that error will display it. You need to fix the root cause (which is, frankly going to be a hell of a lot of work with that much code to dig through) — you will regret any shortcuts you take there. While you are at it, you should stop using themysql_extension (which is deprecated and will be removed from PHP in the future) and upgrade to PDO or themysqli_extension.echo mysql_error();tomysql_error()or remove it. Voila it works.mysql_query() OR die(mysql_erro()), I accidentally removed it editing the question