SQL/cPanel issue

I have faced this issue a few days ago and still do not know any possible solution, hope someone can help me or at least explain this to me.

I had a freelancer hired for adding some extra features on my website. He had been working on 'Like' and 'Share' function for the timeline post. And as you can understand- like function is simular to the facebook like, and share function simply brings another users post on your timeline. The job was done and everything was working fine.

After I have changed the cPanel password. When I did so- those functions stopped functioning. I could not figure out what was the problem in the beginning, but that I got the issue: when I change the password- it stops working. BUT when changing password via cPanel and do not click option 'Allow MySQL password change'- everything works fine. So I have to have an old password for MySQL in order for the proper functioning of the functions I have for the timeline post.

So I will repet my question: what is the reason and what can be the fix for this? 

Sorry for the long text, thank you for your attention :)

Hello

May be your programmer hardcoded the access to Database somewhere in his code. It's a bad parctice because Dolphin has unique configuration settings for Database connection. The easiest way is to contact with him and ask about the problem. Otherwise you need to find someone who will investigate the modification, find and fix the issue.

 Thank you again Anton :) I think I will find a way to fix this.

 OK, this wasn't a freelancer on Freelancer.com by name of LROC was it ?!

off topic I know but I have to ask!

 Hello

 You are welcome! :) 

If it is as Anton stated, you could search in the custom code for the mySQL password and manually change it to your new password.

 You should share this "programmers" name so other members here can be aware and make sure it is addressed; especially if they are working with or looking for a programmer.

 Hello

 I don't know whom yyvskiy worked with. :) Moreover it was my supposition that DB access was hardcoded.

 No, wasn`t him, I used oDesk.

I have found the line which he wrote and which caused the problem, it looks like this:

$con = mysql_connect("localhost","**User name here**","**Password here**"

Maybe I can change the line manually to avoid custom access changes in future?

 It was Amit Verma in oDesk. My first feedback on his job was good because I did not see and was not aware of this kind of issues.