Michael,
What you propose is totally possible. The idea would be that you would include all of the original website in the app/wwwroot folder. This would allow it to be accessed as though it was never modified. The only restriction is you must use cake-php’s index.php file. You can get around this by re-designating the links to index.php to point to index-flat.php and name your original index.php to index-flat.php… you might have some minor conflicts with cakePHP’s index.php being the default handler for http://my.domain.com/ but you should be able to over come this with some inventive manipulation. Possibly using an empty ‘home’ controller method and view to display the original index php, with a custom template just for that particular view so that the “no-grade” is transparent and your superiors think that you are not re-designing the whole site. :-) As far as the integration goes, it should be relatively simple from there once you have the whole site functioning inside the cake framework. As you say, you can simply link to various controller methods to enable the “approved” upgrades, while in the background, you can begin using cakePHP’s features to facilitate the transition of existing code transparently to your users/bosses. FYI, you will need to remember to disable cakePHP’s default CSS in your custom template so that the original site will render properly with little to no changes to existing code. Best of luck, and happy hacking!!! <http://www.connaxis.com/> <http://www.connaxis.com/> <http://www.connaxis.com/> <http://www.connaxis.com/> <http://www.connaxis.com/> <http://www.connaxis.com/> David Kenneth Coleman Sr.Software Engineer ………………………………………………………………………………………………………………… United States: + 1 6468108783 Dept: Development Argentina: + 54 11 52465987 E-mail: [email protected] The Netherlands: + 31 208080017 Skype: david.k.coleman ¡ <http://www.connaxis.com/> <http://www.connaxis.com/> <http://www.connaxis.com/> <http://www.connaxis.com/> <http://www.connaxis.com/> <http://www.connaxis.com/> NEW! Please check out our new <http://www.creative-outsourcing.com/> Portfolio Website: <http://www.creative-outsourcing.com/> Connaxis Creative Outsourcing Specialist <http://www.creative-outsourcing.com/> www.creative-outsourcing.com First page position Google.com: <http://www.google.com/search?hl=en&q=creative+outsourcing&btnG=Google+Searc h> Creative Outsourcing -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of schneimi Sent: 2009-07-06 15:56 To: CakePHP Subject: Re: Using CakePHP to refactor an existing website Hi, I can just give you a hint to a book concerning this topic, maybe it helps you. http://littlehart.net/book/ Regards, Michael Vincent schrieb: > Hi, > > I am considering refactoring a "messy" company intranet (written in > plain PHP) using a web framework, and as you guessed, CakePHP caught > my eye. > > My constraint is that I cannot rewrite it completely from scratch > (hard to convince a manager on that), so I am thinking to gradually > replace existing plain PHP pages with requests going through the MVC > workflow (routing, controller, rendering a view). > Of course, I can only replace independent/isolated parts of the > intranet with framework-based equivalents (wherever possible). > > So my question is: > Is it viable to mix plain PHP with CakePHP? The whole "convention over > configuration" thing might be a problem (dealing with legacy database, > URLs, > Any comment/recommendation on this project? > > Thanks in advance. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
<<inline: image001.jpg>>
