> Hey Felix, really good suggestion... I'm going to try implementing > this. However, I would I manage changes to files inside app/webroot > (as you said) considering they're out of the vendor "package"? Nothing is out of the vendor package ; ). A complete copy of the latest version of CakePHP always rests in /vendors/cakephp/current. When a new CakePHP version is released, you checkout /vendors/cakephp/current and simply copy the new version over the old one. If files were removed you have to delete them manually (via SVN), but that doesn't happen very often. Then you commit the new version. After that you tag it in /vendors/cakephp (in our case as r4064). After that you simply merge the changes between the last CakePHP version (r3825) and the current one (r4064) into /trunk (your working copy of it). In case things inside /app have changed, *only* those changes will be applied, no custom mods will be overwritten. After merging the update in, you commit /trunk and voila, you updated CakePHP.
For a better understanding checkout a typical vendor branch folder layout: vendors |---cakephp |---|---r4064 |---|---|---app |---|---|---docs |---|---|---cake |---|---|---vendors |---|---|---index.php |---|---|---.htaccess |---|---current |---|---|---app |---|---|---docs |---|---|---cake |---|---|---vendors |---|---|---index.php |---|---|---.htaccess |---|---r3825 |---|---|---app |---|---|---cake |---|---|---vendors |---|---|---index.php |---|---|---.htaccess |---|---|---VERSION.txt I hope that helps. -- Felix -------------------------- http://www.thinkingphp.org http://www.fg-webdesign.de Marcelo de Moraes Serpa wrote: > > Well, most of the times replacing the /cake folder will be enough. > Sometimes however, files inside /app change, like > /app/webroot/index.php. In those cases you should replace them as > well to be on the safe side. > > In order to see what has changed in those files you can check the > SVN difference between your local version and the one you intent > to upgrade to. The best way to get this hassle out of your life is > to manage your project in SVN and to use a vendor branch > <http://svnbook.red-bean.com/en/1.1/ch07s05.html> for CakePHP. > This makes updating very easy and I highly recommend it. > > > > Hey Felix, really good suggestion... I'm going to try implementing > this. However, I would I manage changes to files inside app/webroot > (as you said) considering they're out of the vendor "package"? > > > On 12/4/06, *Claudio Poli * <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > > I'm having some problem.. > In an application I've loaded a bunch of model into app_controller.php > like > var $uses = array('Blah', 'Etc'); > to be available in every controller; after the upgrade into every > controller I go CakePHP tells me that he wants a model with the same > name as the controller. > for example I've a Welcome controller that do not have any model but > uses an Article model. > > what's going wrong here? > > thanks > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" 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 -~----------~----~----~----~------~----~------~--~---
