That would depend very much on your old code and on how you see the integration between the two.
For example, using CakePHP for a sub-app in example.com/blog/ and keeping the rest of the (imagined) CMS in legacy code should be fairly simple... just as long as the .htaccess files don't cause each-other problems you should have that running by following some points in the manual. If you can use Cake for a separate section like that you can get some Cake-training done and porting your old code to Cake may start to look more plausible. My very first attempt at a Cake app (after the original blog tutorial) was to port an old CMS... But I wouldn't recommend doing that. Creating a fresh app makes it a lot easier to get comfortable with the conventions instead of trying to shoe-horn old code into controllers and models. /Martin On Mar 23, 5:06 pm, Aivaras <[email protected]> wrote: > Hello dear developers, > > I am wondering if it is possible to use CakePHP as a part of project. I mean > I'd love to have some old code, but would still love to use CakePHP. > I cannot convert everything to cakephp so that is why I need my old code to > work also. > > Any suggestions? > > Thanks in advance, > Faifas --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
