Topics

Build 273 - Update to Model::save() method

Release Note 3

The save() method of a model will change in the next build (273+). This is an undocumented feature and it should be rarely used, however, some areas of the core files used it and just in case this pattern was copied, we want to announce this change.

The change is actually a fix since the method was not compatible with Eloquent. In October, the first argument was used to pass in the save data. In Eloquent, the first argument is used to pass in saving options. This was a mistake that was not picked up since the early days, so we are correcting it to ensure compatibility with Laravel and its packages.

Please check your code for instances of ->save() and ensure the first argument is not being used for save data, otherwise this data will be ignored in the upcoming build. Below is how to patch your code if you do discover it. You can patch the code immediately and do not need to wait for the latest build.

Latest from the blog

In this post we want to reveal some details about October Pond, which we are building at the moment. If you haven't yet heard about Pond, it is an installation manager and deployment tool for Windows and Mac.