JavaScript Object Notation (JSON) is a text-based way of representing JavaScript object literals, arrays, and scalar data. It is language independent, self-describing, and plain text. It is a good solution for transferring data between systems because it is easy to read, write, and utilize.
CakePHP has built-in functions to serve data as JSON, making it trivial to allow access to data within an application or across the internet.
There are file upload plugins for CakePHP (See https://github.com/friendsofcake/awesome-cakephp#file-manipulation ) and they have lots of features. But all I want to do is to simply attach documents to my model and ensure they don't clobber one another so I created my own basic functionality that meets my needs without any added overhead.
Sometimes you need to disable a users account, without deleting the account and the information related to that account. That's why previously in Controller and Views there was a user role named "Disabled." You can set the role to Disabled currently, but it doesn't do anything. Now we're going to change that.
In the previous tutorial, Table Relationships, we set up associated tables and displaying associated data, but there's no point to displaying associated data if you can't add it first.
There are multiple ways to save associated data. We'll start with the easiest way, discretely.
When working with CakePHP it is important to remember "Convention over Configuration." If you start from the bottom, or back end, the database, and work your way forward correctly, CakePHP will do much of legwork for you, saving you tons of redundant and repetitive work.
If you don't, there are almost always ways to make things work the hard way. An example of this is the relationships between tables. If you name your database tables and fields following CakePHP convention, it becomes trivial to set up relationships between them.
You may have noticed references to password() and resetPassword() functions in the Authentication tutorial. These are used to allow users to reset their password when they forget it.
Authentication verifies the identity of a user or service, and Authorization determines their access rights. First we need to identify a user, so we need the user to log in.