Good day.
There is an old big site. Half the functionality of the site is implemented as before - the .php files with noodles from html , php and sql , are in the root of the site, the path is site.com/somefile.php .
The other half of the functionality is implemented in a new way - in the root of the site there is a subdirectory with the mvc-framework and there are controllers, models and displays, the path site.com/framework/somecontroller/somemethod .
The main page of the site works as before .
The task is to transfer the functionality of the main page to the framework so that the path does not change.
Options for solving the problem:
Expand the second copy of the framework in the root of the site, implement the functionality of the main page as
site.com/controller/method, slowly transfer the model controllers and views fromsite.com/framework/tosite.com/. At the same time, it will be necessary to somehow maintain the presence of/framework/in the links.Implement the functionality of the main page of the site in
site.com/framework/, and fromsite.com/index.phpgo tosite.com/framework/controller/method,site.com/framework/controller/methodand show content.Implement the functionality of the main page of the site in
site.com/framework/, then the contents of the directory/framework/make the site root. At the same time, it will be necessary to somehow maintain the presence of/framework/in the links.
Which solution is more adequate? How to keep the presence of /framework/ in the links in the case of option 1 and 3?