First of all, if you are aware of a security issue, fix it first and deploy the fixes. That is before doing something new.
Related to this would be to switch to prepared SQL statements, which on it's own might already take you some time. You should write yourself some procedural helper functions for an easier transition.
Doing so will also help you to identify all the places where your current code-base needs maintenance and love.
You can then better decide with all you want to do, if that is possible.
And btw., why didn't you list SVN -> GIT or similar? Probably you're totally missing the uttermost important tooling here? What is your version control? Do you have got any?
procedural->oop
Apart from switching to PDO - which has got an object oriented interface - I would not suggest you to switch to OO too much. From the code example you give, you should first learn more procedural and improve your style with it, you will then pick OO when you actually need it.
Concepts like DRY work very well in many paradigms.
You might be also interested in a sort of checklist:
First of all, if you are aware of a security issue, fix it first and deploy the fixes. That is before doing something new.
Related to this would be to switch to prepared SQL statements, which on it's own might already take you some time. You should write yourself some procedural helper functions for an easier transition.
Doing so will also help you to identify all the places where your current code-base needs maintenance and love.
You can then better decide with all you want to do, if that is possible.
And btw., why didn't you list SVN -> GIT or similar? Probably you're totally missing the uttermost important tooling here? What is your version control? Do you have got any?
procedural->oop
Apart from switching to PDO - which has got an object oriented interface - I would not suggest you to switch to OO too much. From the code example you give, you should first learn more procedural and improve your style with it, you will then pick OO when you actually need it.
Concepts like DRY work very well in many paradigms.
You might be also interested in a sort of checklist:
First of all, if you are aware of a security issue, fix it first and deploy the fixes. That is before doing something new.
Related to this would be to switch to prepared SQL statements, which on it's own might already take you some time. You should write yourself some procedural helper functions for an easier transition.
Doing so will also help you to identify all the places where your current code-base needs maintenance and love.
You can then better decide with all you want to do, if that is possible.
And btw., why didn't you list SVN -> GIT or similar? Probably you're totally missing the uttermost important tooling here? What is your version control? Do you have got any?
procedural->oop
Apart from switching to PDO - which has got an object oriented interface - I would not suggest you to switch to OO too much. From the code example you give, you should first learn more procedural and improve your style with it, you will then pick OO when you actually need it.
Concepts like DRY work very well in many paradigms.
You might be also interested in a sort of checklist:
First of all, if you are aware of a security issue, fix it first and deploy the fixes. That is before doing something new.
Related to this would be to switch to prepared SQL statements, which on it's own might already take you some time. You should write yourself some procedural helper functions for an easier transition.
Doing so will also help you to identify all the places where your current code-base needs maintenance and love.
You can then better decide with all you want to do, if that is possible.
And btw., why didn't you list SVN -> GIT or similar? Probably you're totally missing the uttermost important tooling here? What is your version control? Do you have got any?
procedural->oop
Apart from switching to PDO - which has got an object oriented interface - I would not suggest you to switch to OO too much. From the code example you give, you should first learn more procedural and improve your style with it, you will then pick OO when you actually need it.
Concepts like DRY work very well in many paradigms.
You might be also interested in a sort of checklist: