So I generally only replace the cake folder with the one from the new release? And what about the app and vendor folders?
On 31 Aug., 15:29, Martin Westin <martin.westin...@gmail.com> wrote: > Generally you can just replace your cake folder with the new one or do > a pull if you use Git. > > Unless you were having problems with some specific feature you are > unlikely to notice the changes as they are just to correct for less > common bugs that were not caught in beta. A number of changes to the > core has to do with improving the comments (and therefore the api- > docs) or formatting the core visually. So diff between two versions > might look massive since many files will have been altered without > affecting the functionality. > > But as I said before, you should run tests or manually check your app > prior to putting the new version into production. > > As an example, the only change that actually affected my main > application was this one: > "Ensuring that 'ext' param added by RequestHandler does not end up as > a queryString parameter in Auth.redirect." > But then I was one of the few that actually noticed this small bug in > the previous version. 99.9% of Cake users did not have the combination > of settings required to show that particular bug and they neither > noticed the bug nor the patch. > > On Aug 31, 3:01 pm, Bs <sommerf...@hs-heilbronn.de> wrote: > > > I'm talking about theupgradefrom the 2nd latest stable release > > (1.2.3) to the latest stable (1.2.4). > > > There seem to be a lot of differences between the files, at least > > that's what I get when using WinMerge to compare the files. > > > On 31 Aug., 13:13, Martin Westin <martin.westin...@gmail.com> wrote: > > > > I am not sure you mean version 1.1 to 1.2 or every small update like > > > 1.2.3 to 1.2.4? > > > I will assume you are talking about possible incompatibilities between > > > versions and updated "cake files" in the app dir. > > > > Small updates to the stable 1.2 will probably not ever change any file > > > in the app directory. Usually you will not be affected by these > > > updates in your code either. It is good practice to have test cases in > > > place to quickly check important code and to have a quick read through > > > the changelog. I do this just looking for keywords for things that > > > might impact my application. I am not so goot at test cases so I > > > always make sure I have a look in the browser and try out features > > > that are related to changes. > > > > For making the bigger leap from 1.1 to 1.2 there are a number of > > > articles and tutorials and a chapter in the cookbook, I believe. You > > > can, for example, find one migration article I wrote in the bakery. I > > > just logged everything I did when migrating a real application. > > > > /Martin > > > > On Aug 31, 10:31 am, Bs <sommerf...@hs-heilbronn.de> wrote: > > > > > Hi, > > > > > is there any tutorial available how toupgradeto the latest Cake PHP > > > > build? Or is this a task everybody has to do "by hand" by checking > > > > every file manually what has changed? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
