Localization as an afterthought?

Question

So, I signed a contract with a web development company as a subcontractor. They combine a large, complex user / product management system for a company that must support several levels of hierarchical localization. I signed a contract for 3 months and, looking at their code, I would like me not to.

They decided to write their own MVC infrastructure (I think the client company did not want to use the pre-written one), and it is very poorly written. There, SQL is scattered across almost every model representation and controller (and there are no parameter-based search methods, that's all SQL), and they still don’t even think about localization - something that will affect almost every query.

The payment term is 4 months, and I honestly believe that we will make good progress by breaking all this and we will do CakePHP. Have any of you been in a similar situation, and what have you done?

PS: This is written in PHP / MySQL.

Answer 1

Rewriting from scratch is almost always the wrong idea (read Joel's article Things You Shouldn't Do - Part 1 ). But you should start implementing small changes (big ones in your case). The sooner you clear the code, the better it will develop ... Get a reliable level of data access and try to parse the advertising MVC first.

, , , , , , . ... , , .

, ( ) . , , ?

Answer 2

-, . Expression Engine. , , , , , , ?

CakePHP, , . , 3 .