One method to do it - depending on how convoluted and hard coded the existing site is - is simply to try and migrate it over to the webroot folder of your CakePHP app. That way, you can reuse the CSS and JavaScript routines where necessary. Of course, you may still need to keep any database tables separate - naturally a lot of this depends on existing site design.
gaioshin On Oct 29, 8:23 am, "www.landed.at" <calvincr...@gmail.com> wrote: > I disagree , cake seems to be flexible enough to me to be able to do > this. Isn't this how routes could be used to ignore the old site > url's ? > Or a better way is that cake just ends up producing widgets that you > could insert into the static site. > I do agree with you miles that its not a good thing to do in general > and there would be some work but cake seems to be ABLE. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
