CakePHP框架入门与核心组件详解

需积分: 9 193 浏览量更新于2024-07-22 收藏 2.82MB PDF 举报

CakePHP框架指南提供了一个全面的介绍，涵盖了这个基于PHP的快速开发框架的核心概念和实践。该指南从2.x版本发布日期（2015年2月28日）开始，帮助开发者深入了解CakePHP的设计模式，如ActiveRecord、 Association Data Mapping、Front Controller 和 MVC（Model-View-Controller）架构。 **1. Getting Started** - **Blog Tutorial**: 这部分引导用户通过一个博客系统的创建，展示了如何在CakePHP中添加一层（例如，文章分类）来理解其工作原理。 **2. Installation** - **Requirements**: 提供了安装 CakePHP 所需的基础环境，包括 PHP 版本和数据库支持。 - **Download and Setup**: 包括下载 CakePHP 框架、设置权限以及开发和生产环境的配置步骤。 - **Advanced Installation & URL Rewriting**: 对于高级用户，讲解了更复杂的安装过程以及如何利用 URL 重写优化应用。 **3. CakePHP Overview** - **What is CakePHP**: 介绍了CakePHP 的核心价值和优点，如它的易用性、高效开发和社区支持。 - **MVC Architecture**: 详细解释了 MVC 设计模式在 CakePHP 中的应用，帮助开发者理解如何组织代码结构。 **4. Controllers** - **AppController**: 作为所有控制器的基类，阐述了其功能和作用。 - **Request Parameters**: 控制器如何处理来自用户的请求参数。 - **Actions and Callbacks**: 控制器中的行为和生命周期方法，如预处理和后处理函数。 - **Controller Methods and Attributes**: 方法和属性的使用，如模型绑定和视图缓存。 **5. Views** - **View Templates**: 描述了视图模板的使用和定制。 - **View Blocks**: 如何组织和复用视图内容。 - **Layouts, Elements, and Custom Views**: 展示了布局、元素和自定义视图类的重要性。 - **View API**: 视图的API提供了丰富的功能，如数据渲染和条件显示。 **6. Models** - **Understanding Models**: 解释模型在数据管理和业务逻辑中的角色。 - **More on Models**: 深入探讨模型关联、验证和行为（Behaviors）的应用。 **7. Core Libraries** - **General Purpose**: 包括通用库，如数据库操作、加密和会话管理。 - **Behaviors**: 描述模型行为如何增强模型功能。 - **Components and Helpers**: 分别是组件（用于封装可复用的功能）和助手（提供辅助视图功能）的介绍。 - **Utilities**: 一系列实用工具类，用于简化开发任务。 **8. Plugins** - **Installing, Using, and Creating Plugins**: 描述如何集成第三方插件、如何使用现有插件以及开发自定义插件的过程。 **9. Conclusion** - 最终总结了 CakePHP 框架的主要特性及其在项目开发中的应用，鼓励开发者充分利用这些资源进行学习和实践。通过阅读这篇指南，读者将能够掌握 CakePHP 的基本结构和关键概念，从而有效地在 PHP 开发中运用这一框架。无论是初学者还是经验丰富的开发者，都能从中找到适合自己的学习路径。

CakePHP Cookbook Documentation, Release 2.x

posts.php instead of Post.php), CakePHP will not recognize any of your settings and will use the defaults

instead.

For more on models, such as table preﬁxes, callbacks, and validation, check out the Models chapter of the

Manual.

Create a Posts Controller

Next, we’ll create a controller for our posts. The controller is where all the business logic for post interaction

will happen. In a nutshell, it’s the place where you play with the models and get post-related work done.

We’ll place this new controller in a ﬁle called PostsController.php inside the /app/Controller

directory. Here’s what the basic controller should look like:

class PostsController extends AppController {

public $helpers = array(’Html’, ’Form’);

}

Now, let’s add an action to our controller. Actions often represent a single function or interface in

an application. For example, when users request www.example.com/posts/index (which is the same as

www.example.com/posts/), they might expect to see a listing of posts. The code for that action would look

something like this:

class PostsController extends AppController {

public $helpers = array(’Html’, ’Form’);

public function index() {

$this->set(’posts’, $this->Post->find(’all’));

}

By deﬁning function index() in our PostsController, users can access the logic there by requesting

www.example.com/posts/index. Similarly, if we were to deﬁne a function called foobar(), users would

be able to access that at www.example.com/posts/foobar.

Warning: You may be tempted to name your controllers and actions a certain way to obtain a certain

URL. Resist that temptation. Follow CakePHP conventions (capitalization, plural names, etc.) and create

readable, understandable action names. You can map URLs to your code using “routes” covered later

on.

The single instruction in the action uses set() to pass data from the controller to the view (which we’ll

create next). The line sets the view variable called ‘posts’ equal to the return value of the find(’all’)

method of the Post model. Our Post model is automatically available at $this->Post because we’ve

followed CakePHP’s naming conventions.

To learn more about CakePHP’s controllers, check out the Controllers chapter.

10 Chapter 1. Getting Started

CakePHP Cookbook Documentation, Release 2.x

correspond. (We’ll have to create a folder named ‘Posts’ in this case.) To format this post data into a nice

table, our view code might look something like this

<h1>Blog posts</h1>

<table>

<tr>

<th>Title</th>

<th>Created</th>

</tr>

<?php foreach ($posts as $post): ?>

<tr>

<td>

<?php echo $this->Html->link($post[’Post’][’title’],

array(’controller’ => ’posts’, ’action’ => ’view’, $post[’Post’][’id’])); ?>

</td>

</tr>

<?php endforeach; ?>

<?php unset($post); ?>

</table>

You might have noticed the use of an object called $this->Html. This is an instance of the CakePHP

HtmlHelper class. CakePHP comes with a set of view helpers that make things like linking, form output,

JavaScript and AJAX a snap. You can learn more about how to use them in Helpers, but what’s important to

note here is that the link() method will generate an HTML link with the given title (the ﬁrst parameter)

and URL (the second parameter).

When specifying URLs in CakePHP, it is recommended that you use the array format. This is explained

in more detail in the section on Routes. Using the array format for URLs allows you to take advantage of

CakePHP’s reverse routing capabilities. You can also specify URLs relative to the base of the application in

the form of /controller/action/param1/param2.

At this point, you should be able to point your browser to http://www.example.com/posts/index. You should

see your view, correctly formatted with the title and table listing of the posts.

If you happened to have clicked on one of the links we created in this view (which link a post’s title to a URL

/posts/view/some_id), you were probably informed by CakePHP that the action hadn’t yet been deﬁned. If

you were not so informed, either something has gone wrong, or you actually did deﬁne it already, in which

case you are very sneaky. Otherwise, we’ll create it in the PostsController now:

// File: /app/Controller/PostsController.php

class PostsController extends AppController {

public $helpers = array(’Html’, ’Form’);

public function index() {

$this->set(’posts’, $this->Post->find(’all’));

12 Chapter 1. Getting Started

CakePHP Cookbook Documentation, Release 2.x

public function view($id) {

if (!$id) {

throw new NotFoundException(__(’Invalid post’));

}

$post = $this->Post->findById($id);

if (!$post) {

throw new NotFoundException(__(’Invalid post’));

}

$this->set(’post’, $post);

}

public function add() {

if ($this->request->is(’post’)) {

$this->Post->create();

if ($this->Post->save($this->request->data)) {

$this->Session->setFlash(__(’Your post has been saved.’));

return $this->redirect(array(’action’ => ’index’));

}

$this->Session->setFlash(__(’Unable to add your post.’));

}

Note: $this->request->is() takes a single argument, which can be the request METHOD (get,

put, post, delete) or some request identiﬁer (ajax). It is not a way to check for speciﬁc posted data.

For instance, $this->request->is(’book’) will not return true if book data was posted.

Note: You need to include the SessionComponent - and SessionHelper - in any controller where you will

use it. If necessary, include it in your AppController.

Here’s what the add() action does: if the HTTP method of the request was POST, it tries to save the data

using the Post model. If for some reason it doesn’t save, it just renders the view. This gives us a chance to

show the user validation errors or other warnings.

Every CakePHP request includes a CakeRequest object which is accessible using $this->request.

The request object contains useful information regarding the request that was just received, and can be used

to control the ﬂow of your application. In this case, we use the CakeRequest::is() method to check

that the request is a HTTP POST request.

When a user uses a form to POST data to your application, that information is available in

$this->request->data. You can use the pr() or debug() functions to print it out if you want

to see what it looks like.

We use the SessionComponent’s SessionComponent::setFlash() method to set a message

to a session variable to be displayed on the page after redirection. In the layout we have

SessionHelper::flash which displays the message and clears the corresponding session vari-

able. The controller’s Controller::redirect function redirects to another URL. The param

array(’action’ => ’index’) translates to URL /posts (that is, the index action of the posts con-

14 Chapter 1. Getting Started

剩余1078页未读，继续阅读

kinxp

粉丝: 0
资源: 3

CakePHP框架入门与核心组件详解

cakephp 框架

cakephp 框架1.3.11版本

CakePHP PHP MVC框架

如何使用 cakephp /usr/bin/env

cakephp4 crond 取环境变量

cakephp crond 取环境变量

php saas框架 有哪些

cakephp 怎么使用DOMDocument

cakephp5 在request内添加值

cakephp operation_log

最新资源

CakePHP　PHP MVC框架

php saas框架有哪些