old PHP Project that needs organizing [closed]

Question

Closed. This question is opinion-based. It is not currently accepting answers.

---

Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.

Closed 8 years ago.

Improve this question

I am working in a company that owns a website which I find very difficult to coop with, not because of my lack of experience in PHP but due to the fact the code is written in a very old and low quality, written with no OOP.

What I can see in the APP:

• html page ,
• Php Page
• Template
• mysql structured like the Pablo Picasso paintings, no foreign keys, no constraints nothing

I only see code written and rewritten over and over I just myself can't understand how do people mingle in this ocean of codes vomit ? When I tried to contact one of my colleagues to understand more about it, he told me that its taking them more and more time to achieve tasks already emphasizing on the fact that complexity is gradually increasing and they can't do anything anymore because a massive amount of data has been initiated.

has anyone had any similar situation? any advice ? maybe there is a way to fix this chaos ?

Any post would be appreciated !

Answer 1

Picking a development framework and re-implementing the application using that will significantly improve the maintainability of an application.

If you want a way of justifying this from a cost perspective, do an audit with a SQL injection testing tool and you'll probably find a million things wrong. Some of these things will be so terrifying you'll be tempted to just burn the codebase to the ground and start over.

The best approach is to migrate, feature by feature, page by page, from the old application to the new one. Often you can do this by creating a content map, adding rewrite rules to map particular URLs to the legacy code, then start deleting these rules one by one as they're no longer required.

Remember to have a robust mapping table if you ever change URLs. Returning a 301 Permanent redirect is the best way to do this.

Answer 2

I take these projects a lot. Breathe. It's part of the industry.

Simply break the project up in to functions. Design a flow diagram. Program the flow diagram.

Software rebuilt.