Đang chuẩn bị liên kết để tải về tài liệu:
Agile Web Application Development with Yii 1.1 and PHP5 phần 5

Bây giờ nếu chúng ta lưu lại và xem kết quả của chúng tôi bằng cách nhìn vào trang chi tiết dự án cho dự án 1 (http://localhost/tasctrak/index.php?r=project/view&id=1), và giả sử bạn đã tạo ra một vài thử nghiệm các vấn đề thuộc dự án đó, bạn sẽ thấy một trang như một trong màn hình sau đây: | Chapter 6 b php echo CHtml encode data- getAttributeLabel descripti on b php echo CHtml encode data- description br b php echo CHtml encode data- getAttributeLabel type_ id b php echo CHtml encode data- type_id br b php echo CHtml encode data- getAttributeLabel status_ id b php echo CHtml encode data- status_id div Now if we save and view our results by looking at the project details page for Project 1 http localhost tasctrak index.php r project view id 1 and assuming you have created a couple of test issues under that project you should see a page like the one in the following screen 131 Iteration 3 Adding tasks As we set the pagination property of our data provider very low remember we set it to just 1 we can add one more issue to demonstrate the built-in paging functionality. Adding one more issue changes the display of issues to have links that allow us to go from page to page within our Project Issues listing as depicted in the following screenshot Project Issues Displaying 2-2 of 2 result s . Name Test Feature for project 1 Description this is a test feature for project 1 Type 1 Status 0 Go to page ỹ Previous T Next Making some final tweaks We now have a list of our issues associated with a project that are displayed from within the project details page. We also have the ability to view the details of an issue R ead as well as links to U pdate and D elete issues. So for the most part our CRUD operations are in place. However there are still a few items that need to be addressed before we can close out this iteration. One thing we notice is that the issues display list is showing numeric ID numbers for the Type Status Owner and Requester fields. We should change this so that the text values for those are displayed instead. Also as issues are under a specific project already it is a bit redundant to have the project ID displayed as part of the issue list data. So we can remove that. Finally we need to address some of the navigational links that are displayed on