The PHP’s popular Framework has some Naming conventions that need to be followed at the time of development.
Controller class names are plural, CamelCased, and end in Controller and the filename would be ‘ApplesController.php’.
e.g. PeopleController and LatestArticlesController
File and Class Name Conventions
In general, filenames match the class names, which are CamelCased. So if you have a class MyNiftyClass, then in CakePHP, the file should be named MyNiftyClass.php. Below are examples of how to name the file for each of the different types of classes you would typically use in a CakePHP application:
- The Controller class KissesAndHugsController would be found in a file namedKissesAndHugsController.php
- The Component class MyHandyComponent would be found in a file named MyHandyComponent.php
- The Model class OptionValue would be found in a file named OptionValue.php
- The Behavior class EspeciallyFunkableBehavior would be found in a file namedEspeciallyFunkableBehavior.php
- The View class SuperSimpleView would be found in a file named SuperSimpleView.php
- The Helper class BestEverHelper would be found in a file named BestEverHelper.php
Each file would be located in the appropriate folder in your app folder.
Model and Database Conventions
Model class names are singular and CamelCased.
e.g. Person, BigPerson, and ReallyBigPerson
Table names corresponding to CakePHP models are plural and underscored. The underlying tables for the above mentioned models would be people, big_people, and really_big_people, respectively.
Field names with two or more words are underscored: first_name.
Foreign keys in hasMany, belongsTo or hasOne relationships are recognized by default as the (singular) name of the related table followed by _id. So if a Baker hasMany Cake, the cakes table will refer to the bakers table via a baker_id foreign key. For a table like category_types whose name contains multiple words, the foreign key would be category_type_id.
Join tables, used in hasAndBelongsToMany (HABTM) relationships between models, should be named after the model tables they will join, arranged in alphabetical order (apples_zebras rather than zebras_apples).
View template files are named after the controller functions they display, in an underscored form. The getReady() function of the PeopleController class will look for a view template in /app/View/People/get_ready.ctp.
The basic pattern is /app/View/Controller/underscored_function_name.ctp.
By naming the pieces of your application using CakePHP conventions, you gain functionality without the hassle and maintenance tethers of configuration. Here’s a final example that ties the conventions together:
- Database table: “people”
- Model class: “Person”, found at /app/Model/Person.php
- Controller class: “PeopleController”, found at /app/Controller/PeopleController.php
- View template, found at /app/View/People/index.ctp
Using these conventions, CakePHP knows that a request to http://example.com/people/ maps to a call on the index() function of the PeopleController, where the Person model is automatically available (and automatically tied to the ‘people’ table in the database), and renders to a file. None of these relationships have been configured by any means other than by creating classes and files that you’d need to create anyway.
Source: CakePHP Bakery