CakePHP 3.4 开发指南：快速入门与迁移指南

需积分: 9 58 浏览量更新于2024-07-20 收藏 2.36MB PDF 举报

"CakePHP 3.4 开发手册文档是官方提供的详尽指南，旨在帮助开发者理解和使用这个流行的PHP框架。本文档涵盖了从快速入门到深入迁移指南的各种主题，包括模型、视图、控制器三层架构，以及请求周期、命名约定、配置、ORM、调试、缓存、核心组件、网络、会话、测试等多个方面。此外，还有教程和示例，如书签应用教程和博客应用教程，以帮助开发者快速上手。" 在《CakePHP 3.4 开发手册》中，你将发现以下关键知识点： 1. **蛋糕PHP概述**： CakePHP 遵循“约定优于配置”的原则，使得开发过程更为高效。它包含三个主要层次——模型（Model）、视图（View）和控制器（Controller），构成MVC架构。 2. **模型层**：模型负责处理应用程序的业务逻辑和数据管理，通常与数据库交互。在CakePHP中，你可以通过ActiveRecord风格的对象来操作数据表。 3. **视图层**：视图负责展示数据，通常包含HTML、CSS和JavaScript，用于构建用户界面。视图可以与助手（Helper）一起工作，以创建复杂的布局和元素。 4. **控制器层**：控制器处理用户请求，协调模型和视图，确保数据流正确并生成响应。 5. **蛋糕PHP请求周期**：描述了从用户请求到服务器响应的整个流程，涉及路由、控制器动作、视图渲染等步骤。 6. **快速启动指南**：提供了一个快速上手的教程，通过书签应用实例介绍了如何创建基本的CakePHP项目。 7. **3.0迁移指南**：对于从旧版本升级到3.0的开发者，提供了必要的要求、升级工具和目录布局变更信息。还涉及了Composer的安装、命名空间、常量移除、配置更改等。 8. **ORM（对象关系映射）**：CakePHP 3.4引入的新ORM系统，简化了数据库操作，允许开发者以面向对象的方式处理数据库记录。 9. **核心组件**：包括调试、对象设置/配置、缓存、事件系统、日志、路由、网络（HTTP和电子邮件）、会话等，这些都是构建Web应用的基本元素。 10. **测试**：详细的测试套件部分指导如何进行单元测试、集成测试和功能测试，以确保代码的质量和稳定性。 11. **视图组件和助手**：视图助手可以帮助生成复杂数组、日期格式化、链接等，而组件则可以在多个控制器之间共享代码。 12. **I18n（国际化）和L10n（本地化）**：提供了一套完整的国际化和本地化解决方案，帮助开发者创建多语言应用。 13. **教程和示例**：如书签应用和博客应用教程，分步骤指导开发者如何实际操作，以加深对CakePHP的理解。这本手册是CakePHP 3.4开发者的宝贵资源，无论你是新手还是有经验的开发者，都能从中获取到大量实用的信息和技巧。

CakePHP Cookbook Documentation, Release 3.4

Danish

• Danish CakePHP Slack Channel

French

• French CakePHP Community

German

• German CakePHP Slack Channel

• German CakePHP Facebook Group

Iranian

• Iranian CakePHP Community

Dutch

• Dutch CakePHP Slack Channel

Japanese

• Japanese CakePHP Slack Channel

• Japanese CakePHP Facebook Group

Portuguese

• Portuguese CakePHP Google Group

Spanish

• Spanish CakePHP Slack Channel

• Spanish CakePHP IRC Channel

• Spanish CakePHP Google Group

https://cakesf.slack.com/messages/denmark/

http://cakephp-fr.org

https://cakesf.slack.com/messages/german/

https://www.facebook.com/groups/146324018754907/

http://cakephp.ir

https://cakesf.slack.com/messages/netherlands/

https://cakesf.slack.com/messages/japanese/

https://www.facebook.com/groups/304490963004377/

http://groups.google.com/group/cakephp-pt

https://cakesf.slack.com/messages/spanish/

http://groups.google.com/group/cakephp-esp

6 Chapter 1. CakePHP at a Glance

CakePHP Cookbook Documentation, Release 3.4

CakePHP Conventions

We are big fans of convention over conﬁguration. While it takes a bit of time to learn CakePHP’s conventions, you

save time in the long run. By following conventions, you get free functionality, and you liberate yourself from the

maintenance nightmare of tracking conﬁg ﬁles. Conventions also make for a very uniform development experience,

allowing other developers to jump in and help.

Controller Conventions

Controller class names are plural, CamelCased, and end in Controller. UsersController and

ArticleCategoriesController are both examples of conventional controller names.

Public methods on Controllers are often exposed as ‘actions’ accessible through a web browser. For example the

/users/view maps to the view() method of the UsersController out of the box. Protected or private

methods cannot be accessed with routing.

URL Considerations for Controller Names

As you’ve just seen, single word controllers map to a simple lower case URL path. For example, UsersController

(which would be deﬁned in the ﬁle name UsersController.php) is accessed from http://example.com/users.

While you can route multiple word controllers in any way you like, the convention is that your URLs are lowercase

and dashed using the DashedRoute class, therefore /article-categories/view-all is the correct form to

access the ArticleCategoriesController::viewAll() action.

When you create links using this->Html->link(), you can use the following conventions for the url array:

$this->Html->link('link-title', [

'prefix' => 'MyPrefix' // CamelCased

'plugin' => 'MyPlugin', // CamelCased

'controller' => 'ControllerName', // CamelCased

'action' => 'actionName' // camelBacked

]

For more information on CakePHP URLs and parameter handling, see Connecting Routes.

File and Class Name Conventions

In general, ﬁlenames match the class names, and follow the PSR-0 or PSR-4 standards for autoloading. The following

are some examples of class names and their ﬁlenames:

• The Controller class LatestArticlesController would be found in a ﬁle named LatestArticlesCon-

troller.php

• The Component class MyHandyComponent would be found in a ﬁle named MyHandyComponent.php

• The Table class OptionValuesTable would be found in a ﬁle named OptionValuesTable.php.

• The Entity class OptionValue would be found in a ﬁle named OptionValue.php.

• The Behavior class EspeciallyFunkableBehavior would be found in a ﬁle named EspeciallyFunk-

ableBehavior.php

• The View class SuperSimpleView would be found in a ﬁle named SuperSimpleView.php

• The Helper class BestEverHelper would be found in a ﬁle named BestEverHelper.php

Each ﬁle would be located in the appropriate folder/namespace in your app folder.

Additional Reading 7

CakePHP Cookbook Documentation, Release 3.4

Model and Database Conventions

Table class names are plural, CamelCased and end in Table. UsersTable, ArticleCategoriesTable, and

UserFavoritePagesTable are all examples of conventional model names.

Table names corresponding to CakePHP models are plural and underscored. The underlying tables for the above

mentioned models would be users, article_categories, and user_favorite_pages, respectively.

The convention is to use English words for table and column names. If you use words in another language, CakePHP

might not be able to process the right inﬂections (from singular to plural and vice-versa). If you need to add your own

language rules for some words, you can use the utility class Cake\Utility\Inflector. Besides deﬁning those

custom inﬂection rules, this class also allows you to check that CakePHP understands your custom syntax for plurals

and singulars words. See the documentation about Inﬂector for more information.

Field names with two or more words are underscored: first_name.

Foreign keys in hasMany, belongsTo/hasOne relationships are recognized by default as the (singular) name of the

related table followed by _id. So if Users hasMany Articles, the articles table will refer to the users table via

a user_id foreign key. For a table like article_categories whose name contains multiple words, the foreign

key would be article_category_id.

Join tables, used in BelongsToMany relationships between models, should be named after the model tables they will

join, arranged in alphabetical order (articles_tags rather than tags_articles).

In addition to use an auto-increment key as the primary key, you may also use UUID columns. CakePHP will cre-

ate a unique 36 character UUID (Cake\Utility\Text::uuid()) whenever you save a new record using the

Table::save() method.

View Conventions

View template ﬁles are named after the controller functions they display, in an underscored form. The viewAll()

function of the ArticlesController class will look for a view template in src/Template/Articles/view_all.ctp.

The basic pattern is src/Template/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 conﬁguration. Here’s a ﬁnal example that ties the conventions together:

• Database table: “articles”

• Table class: ArticlesTable, found at src/Model/Table/ArticlesTable.php

• Entity class: Article, found at src/Model/Entity/Article.php

• Controller class: ArticlesController, found at src/Controller/ArticlesController.php

• View template, found at src/Template/Articles/index.ctp

Using these conventions, CakePHP knows that a request to http://example.com/articles/ maps to a call on the

index() function of the ArticlesController, where the Articles model is automatically available (and automatically

tied to the ‘articles’ table in the database), and renders to a ﬁle. None of these relationships have been conﬁgured by

any means other than by creating classes and ﬁles that you’d need to create anyway.

Now that you’ve been introduced to CakePHP’s fundamentals, you might try a run through the Bookmarker Tutorial

to see how things ﬁt together.

CakePHP Folder Structure

After you’ve downloaded and extracted the CakePHP application, these are the ﬁles and folders you should see:

8 Chapter 1. CakePHP at a Glance

CakePHP Cookbook Documentation, Release 3.4

• bin

• conﬁg

• logs

• plugins

• src

• tests

• tmp

• vendor

• webroot

• .htaccess

• composer.json

• index.php

• README.md

You’ll notice a few top level folders:

• The bin folder holds the Cake console executables.

• The conﬁg folder holds the (few) Conﬁguration ﬁles CakePHP uses. Database connection details, bootstrapping,

core conﬁguration ﬁles and more should be stored here.

• The plugins folder is where the Plugins your application uses are stored.

• The logs folder normally contains your log ﬁles, depending on your log conﬁguration.

• The src folder will be where you work your magic: it’s where your application’s ﬁles will be placed.

• The tests folder will be where you put the test cases for your application.

• The tmp folder is where CakePHP stores temporary data. The actual data it stores depends on how you have

CakePHP conﬁgured, but this folder is usually used to store model descriptions and sometimes session informa-

tion.

• The vendor folder is where CakePHP and other application dependencies will be installed. Make a personal

commitment not to edit ﬁles in this folder. We can’t help you if you’ve modiﬁed the core.

• The webroot directory is the public document root of your application. It contains all the ﬁles you want to be

publically reachable.

Make sure that the tmp and logs folders exist and are writable, otherwise the performance of your application

will be severely impacted. In debug mode, CakePHP will warn you, if it is not the case.

The src Folder

CakePHP’s src folder is where you will do most of your application development. Let’s look a little closer at the

folders inside src.

Console Contains the console commands and console tasks for your application. For more information see Shells,

Tasks & Console Tools.

Controller Contains your application’s controllers and their components.

Locale Stores string ﬁles for internationalization.

Model Contains your application’s tables, entities and behaviors.

Additional Reading 9

剩余849页未读，继续阅读

zp_ice

粉丝: 2
资源: 8

CakePHP 3.4 开发指南：快速入门与迁移指南

cakephp中文手册PDF版

cakephp 3.0 使用总结

CakePHP框架最全中文文档

如何使用 cakephp /usr/bin/env

cakephp4 crond 取环境变量

cakephp crond 取环境变量

php 开发框架有哪些？从上手难度、互联网资源、运行效率、使用面 等角度做个分析

cakephp 读不到系统环境变量

cakephp4 读不到系统环境变量

cakephp 取apache的观景变量

最新资源

php 开发框架有哪些？从上手难度、互联网资源、运行效率、使用面等角度做个分析