- 1 Introduction
- 2 How to Install ZenTao
- 2.1 Choose the best installation
- 2.2 ZenTao Cloud
- 2.3 One-click Installation for Windows
- 2.4 One-click Installation for Linux
- 2.5 Installation with Lampp
- 2.6 Source Code Installation (for all Systems)
- 2.7 Set up Virtualbox for ZenTao
- 2.8 Softaculous service
- 3 Upgrade ZenTao
- 3.1 Upgrade ZenTao
- 3.2 Upgrade by source code (for all systems)
- 3.3 Upgrade for one-click installation for Windows (xampp)
- 3.4 Upgrade for one-click installation package for Linux
- 4 Users and Groups
- 5 Simple Application
- 5.1 Project and Task Management
- 5.2 Bug Management
- 5.3 Product Management
- 5.4 Individual Task Management
- 6 Basic Application
- 6.1 Basic Workflow
- 6.2 Agile and Scrum
- 6.3 ZenTao and Scrum
- 6.4 ZenTao Tutorial for Rookies
- 6.5 Create a Product
- 6.6 Create a Story
- 6.7 Create a Project
- 6.8 Confirm Stories
- 6.9 Story Breakdown
- 6.10 Report a Bug
- 6.11 Manage Contacts
- 6.12 Customization
- 7 Advanced Application
- 7.1 Workflow
- 7.1.1 ZenTao Workflow
- 7.2 Personal management
- 7.3 For Product Owner
- 7.3.1 Manage a Product
- 7.3.2 Manage a Product Line
- 7.3.3 Create and Review a Story
- 7.3.4 Change and Review a Story
- 7.3.5 Story Status
- 7.3.6 Notes for Writing a Story
- 7.3.7 Product Modules
- 7.3.8 Release Plan
- 7.3.9 Create a Release
- 7.3.10 Roadmap
- 7.3.11 Manage Documents
- 7.3.12 Product Planning Meetings
- 7.3.13 Daily Scrum, Review and Retrospective Meetings
- 7.3.14 Story Reports
- 7.4 For Project Manager
- 7.4.1 Create a Project
- 7.4.2 Set up a Team
- 7.4.3 Confirm Stories
- 7.4.4 Story Breakdown
- 7.4.5 Daily Standup Meetings
- 7.4.6 Check Project Progress via Burndown Chart
- 7.4.7 Check Project Progress via Lists
- 7.4.8 Review and Retrospective Meetings
- 7.4.9 Basic reports on tasks
- 7.5 For Development Team
- 7.5.1 Project planning meeting and task breakdown
- 7.5.2 Claim tasks and update
- 7.5.3 Kanban and Tree Diagram
- 7.5.4 Create a Build
- 7.5.5 Test Task
- 7.5.6 Resolve a Bug
- 7.5.7 Manage Documents
- 7.5.8 Confirm Bugs
- 7.6 For QA Team
- 7.6.1 Bug Management
- 7.6.2 Report a Bug
- 7.6.3 Confim and Close a Bug
- 7.6.4 Activate a Bug
- 7.6.5 Locate a Bug
- 7.6.6 Test Cases
- 7.6.7 Create and Review Test Cases
- 7.6.8 Manage Test Tasks
- 7.6.9 Test Suites, Public Case Libs and Reports
- 7.6.10 Manage Test Tasks
- 7.6.11 Execute Cases and Report Bugs
- 7.6.12 Reports
- 8 Configuration
- 8.1 Maintain ZenTao
- 8.1.1 Initialize scripts
- 8.1.2 Back up ZenTao
- 8.1.3 Recover the Deleted
- 8.1.4 Update Burndown charts
- 8.1.5 ZenTao remote host
- 8.2 Deploy ZenTao
- 9 Custom Development
- 9.1 ZenTao customization
- 9.2 ZenTao Directory
- 9.3 Locate and Change Files
- 9.4 ZenTao Database Structure
- 9.5 Common Modules
- 9.6 Add Features to Menu
- 9.7 Set Privileges to Modules
- 9.8 Examples: Modify Language Prompt
- 9.9 Examples: set priority when creating bugs
- 9.10 Web Editor
- 9.11 Packaging Standards of ZenTao 1.1
- 10 Other Relevant Issues
ZenTao has code editor. You can log in ZenTao as a super administrator to develop.
Go to Admininstrator-> Develop->Editor, and you will find extension editor as shown in the screenshot.
Click the module you want to develop and all the extensible files in this module will show at the right, including control.php and model.php.
All these files are sequenced, which aremodel.php and its method;
control.php and its method;
templates, language files, configuration file config.php in the view folder;
The sequence of the extension files are the same as the sequence of files above, so that you can find the files to extend easily.
There are links at the end of each file. Click these links to edit and extend online.
2. Web editor
2.1 model.php extension
You can develop the existing methods of model.php. The editor will automatically generate simple codes. You can also add new methods to model.php.
2.2 control.php extension
It will prompt whether to use existing code when extending the existing control.php.
If "Yes", it will generate a control.php class of this module. The extended method can also have the control.php methods of this module. If not, you should define the method again.
Simlilarly, you can also add new methods to control.php.
2.3 Extension of template files
There are also two ways to extend template files. One is to rewrite a template to override the orginal one. The other is to make partial modification to the original page via hook scripts.
2.4 Extension of other files
For extension of other files, it will display the source file for reference.
2.5 Compile the files extended
You can edit and delete the extended files in the directory of ext.
3. Save extended files3.1 File name unnecessary
When you extend the methods of control.php and override template files, file names are defined, so you don’t have to enter one.
3.2 File name optional
When you extend the methods of model.php, language files and configuration files, file names will be saved as the default file names if you don't enter names for it. If you did, they will be saved as the name you entered.
3.3 File name required
Newly added methods, pages, hooks and extensions can only be saved when you enter file names.
Notes1. When saving the files, make sure that the programs have the privilege to write and read.
2. If there is file names are conflicting with each other and you can not save it, change the file name or select "Overwrite" the file.
3. The editor is designed just for the convenience extension, so it is very simple. Your problems and solutions when using this editor are welcome to share.