Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/uzyn/practera-comments
Comments for Practera, forked from CakeDC's
https://github.com/uzyn/practera-comments
Last synced: 11 days ago
JSON representation
Comments for Practera, forked from CakeDC's
- Host: GitHub
- URL: https://github.com/uzyn/practera-comments
- Owner: uzyn
- License: other
- Created: 2014-11-02T13:51:32.000Z (about 10 years ago)
- Default Branch: master
- Last Pushed: 2015-02-26T09:37:22.000Z (over 9 years ago)
- Last Synced: 2024-04-29T23:55:29.883Z (7 months ago)
- Language: PHP
- Size: 354 KB
- Stars: 0
- Watchers: 5
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: readme.md
- License: license.txt
Awesome Lists containing this project
README
# Comments Plugin for CakePHP #
Version 1.1 for cake 2.x
Comments plugin is a universal comment system that can be attached to any controller with a few lines of code.
## Installation ##
First created the needed tables in database. This plugin comes with two mechanisms to get your database tables setup:
1. You can use the default CakePHP schema method from the console: `cake schema create --plugin Comments --name app`
2. You can use the CakeDC migrations plugin to import your database tables: `cake migrations.migration all --plugin Comments`
If you choose the second method, please ensure you have first installed the [CakeDC migrations plugin](http://github.com/CakeDC/migrations) first.
Finally, you need to have some sort of `users` or `logins` table that keeps member information. This table should contain a slug field, as it is used by the comments plugin.
We recommended to use [CakeDC users plugin](http://github.com/CakeDC/users) that allow all needed for plugin features.
## Usage ##
We have Post model and want to have comments on the /posts/view page.
So we need to choose how we want to display the comments - flat, threaded, or as tree.
In our example we want to use the flat type comments.
First let us add the following code in the PostsController:
```php
public $components = array(
'Comments.Comments' => array(
'userModelClass' => 'Users.User' // Customize the User class
)
);
/**
* Initializes the view type for comments widget
*
* @return string
* @access public
*/
public function callback_commentsInitType() {
return 'flat'; // threaded, tree and flat supported
}
```
By default the component assumes that the action that will be used for comments is named 'view', but we can override it inside the beforeFilter method.
Inside the view (in our case it will View/Posts/view.ctp) we will add the next lines at the end of the view file.
```php
CommentWidget->options(array('allowAnonymousComment' => false));?>
CommentWidget->display();?>
```
## How it works ##
During page rendering the comments component checks if some of the passed named url parameters are filled.
If it is filled we perform operations like add/delete comment. The component works in background of code performed during controller action and needs just one find from controller.
Sometimes you want to know how much comments your user did. In this case all you need to do - add additional field with name "comments" into the table that keep all users information in you systems. It can be any table like users or profiles.
## Component conventions ##
The component needs to have one important convention for any actions where it is enabled:
To work properly, the component needs a specific variable to be set in every action using it. Its name should be either Inflector::variable(Controller::$modelClass) or Comments::$viewVariable should be set to other name of this view variable. That variable should contain single model record. for example you need to have next line in you view action:
```php
$this->set('post', $this->Post->read(null, $id));
```
If you plan to attach comments plugin to model that stored in some plugin its highly recommended to define Model::$fullName property for your model in ClassRegistry format.
For example for Post model of Blogs plugin set $fullName = 'Blogs.Post'.
It is also possible to define a permalink() function in your Post model. This method should return the correct url to the view page where comments displayed.
This required by most antispam systems if you plan to use it.
## Component callbacks ##
It is possible to override or extend the most comments component methods in the controller.
To do this we need to create method with prefix callback_comments
Examples:
* callback\_add will named as callback_commentsAdd in controller,
* callback\_fetchData will named as callback_commentsFetchData in controller.
Callbacks:
* add - add new comment action. Sometimes useful to override, to add some additional preprocessing. See example bellow.
* initType - method that set comment template system type based on vars.
* delete - delete action. Can be overloaded.
* afterAdd - callback called after success adding new comment.
Extend or override any callback without changing component code.
```php
public function callback_commentsAdd($modelId, $commentId, $displayType, $data = array()) {
if (!empty($this->request->data)) {
/* ... */
// Custom model method to manipulate or validate the comment
if (!$this->Model->validateComment($this->request->data)) {
$this->Session->setFlash(__('Please enter necessery information', true));
return;
}
/* ... */
}
return $this->Comments->callback_add($modelId, $commentId, $displayType, $data);
}
```
## Component parameters ##
Plugin uses several named parameters that are passed during comment operations like create, delete, reply or approve is performed.
* comment\_view\_type - Parameter that allow to specify what type of comments system used. Currently allowed to use one of 'flat', 'threaded', 'tree'. This parameter possible and useful to setup in beforeFilter to use only one type of view. If user allowed to choose between tree and flat, then it parameter can be dynamic.
* comment_action - this parameter used, to pass what action should performed. N
* comment - comment id passed here.
* quote - boolean flag that show if you should use quote when generate reply to comment form.
Please note that parameters listed here should not be used as named parameters in your app!
## Component settings ##
All components parameters should be overwritten in beforeFilter method.
* actionNames - Name of actions comments component should use. By default it 'view' and 'comments'. So if you want to have comments on 'display' action you need to set it in beforeFilter method.
* modelName - Name of 'commentable' model. By default it is default controller's model name (Controller::$modelClass)
* assocName - Name of association for comments
* userModel - Name of user model associated to comment. By default it is UserModel. Important to have different name with User model name.
* userModelClass - Class name for the user model. By default it is User. If you use other model for identity purpose you need to setup it here.
* unbindAssoc - enabled if this component should permanently unbind association to Comment model in order to not
* query model for not necessary data in Controller::view() action
* commentParams - Parameters passed to view.
* viewVariable - Name of view variable which contains model data for view() action. Needed just for PK value available in it. By default Inflector::variable(Comments::modelName)
* viewComments - Name of view variable for comments data. By default 'commentsData'
* allowAnonymousComment - Flag to allow anonymous user make comments. By default it is false.
There are two way to change settings values for component. You can change it in beforeFilter callback before component will initialized, or pass parameters during initialization:
public $components = array('Comments.Comments' => array('userModelClass' => 'Users.User'));
## Behavior overloading and configuration ##
Some times during search need to bind some addtional models into result returned in list of comments.
Most logic way for that - overload behavior commentBeforeFind method like this on model level:
```php
/**
* Prepare models association to before fetch data
*
* @param array $options
* @return boolean
* @access public
*/
public function commentBeforeFind($options) {
$result = $this->Behaviors->dispatchMethod($this, 'commentBeforeFind', array($options));
$userModel = $this->Behaviors->Commentable->settings[$this->alias]['userModelAlias'];
$this->Comment->bindModel(array('belongsTo' => array(
'Profile' => array(
'className' => 'Profile',
'foreignKey' => false,
'conditions' => array('Profile.user_id = ' . $userModel . '.id')
)
)), false);
return $result;
}
```
## Helper parameters and methods ##
* target - used in ajax mode to specify block where comment widget stored
* ajaxAction - array that specify route to the action or string containing action name. Used in ajax mode.
* displayUrlToComment - used if you want to have separate pages for each comment. By default false.
* urlToComment - used if you want to have separate pages for each comment. Contain url to view comment.
* allowAnonymousComment - boolean var, that show if anonymous comments allowed
* viewInstance - View instance class, that used to generated the page.
* subtheme - parameter that allow to have several set of templates for one view type. So if you want to have two different representation of 'flat' type for posts and images you just used two subthemes 'posts' and 'images' like 'flat\_posts' and 'flat\_images'.
### Template system structure ###
The template system consists of several elements stored in comments plugin.
It is 'form', 'item', 'paginator' and 'main'.
* Main element is rendered and use all other to render all parts of comments system.
* Item element is a just one comment block.
* Paginator is supposed to used by 'flat' and 'tree' themes. Threaded type theme is not allowed to paginate comments.
* Form element contains form markup to add comment or reply.
All elements are stored in the structure views/elements/comments/...type..., where ...type... is one of view types: 'flat', 'tree', 'threaded'.
It is possible to define any of this elements in any of your plugins or app using this comments system.
Sometimes we need to have several sets of templates for one view type. For example, if we want to have two different representation of 'flat' type for posts and images views we just used two subthemes for 'flat'.
So in elements/comments we need to create folders 'flat\_posts' and 'flat\_images' and copy elements from '/elements/comments/flat' here and modify them.
## Ajax support ##
The plugin was tested with jquery engine. Since cakephp js helper support many engines, theoretically you can choose any of supported js engines and comments plugin should support it.
To turn on ajax mode you need set pass two parameters to the helper:
```php
CommentWidget->options(array(
'target' => '#comments',
'ajaxAction' => 'comments'));
?>
```
Next important to implement in controller special action, by default named comments:
```php
Post->read(null, $id);
$this->layout = 'ajax';
$this->set(compact('post', 'id'));
}
?>
```
It is also necessary to implement comments view, that will just contains previous block and will include ajax element from comments plugin:
```
CommentWidget->options(array(
'target' => '#comments',
'ajaxAction' => 'comments'));
echo $this->element('/ajax');
?>
```
The comments action in controller should be same as view action, the difference only in view.
If you should pass some more params into CommentWidget::display method in ajax element you can call it with addtional displayOptions parameter:
```php
CommentWidget->options(array(
'target' => '#comments',
'ajaxAction' => 'comments'));
$this->element('/ajax', array('displayOptions' => array(/* ... params ... */)));
?>
```
## Supported callbacks ##
* Behavior.Commentable.beforeCreateComment
* Behavior.Commentable.afterCreateComment
Both events called on save comment operation. If needed to prevent comment saving on some conidition event listener for beforeCreateComment must return false. Event afterCreateComment could used on same additional action that should performed on save comments. Event beforeCreateComment get complete comment data that will stored into database. It is possible to override it in listener and return new result. Event afterCreateComment get only comment id in data record and complete record could be readed in listener aciton.
## Requirements ##
* PHP version: PHP 5.2+
* CakePHP version: Cakephp 2.3 Stable
## Support ##
For support and feature request, please visit the [Comments Plugin Support Site](http://cakedc.lighthouseapp.com/projects/59616-comments-plugin/).
For more information about our Professional CakePHP Services please visit the [Cake Development Corporation website](http://cakedc.com).
## Branch strategy ##
The master branch holds the STABLE latest version of the plugin.
Develop branch is UNSTABLE and used to test new features before releasing them.
Previous maintenance versions are named after the CakePHP compatible version, for example, branch 1.3 is the maintenance version compatible with CakePHP 1.3.
All versions are updated with security patches.
## Contributing to this Plugin ##
Please feel free to contribute to the plugin with new issues, requests, unit tests and code fixes or new features. If you want to contribute some code, create a feature branch from develop, and send us your pull request. Unit tests for new features and issues detected are mandatory to keep quality high.
## License ##
Copyright 2009-2013, [Cake Development Corporation](http://cakedc.com)
Licensed under [The MIT License](http://www.opensource.org/licenses/mit-license.php)
Redistributions of files must retain the above copyright notice.
## Copyright ###
Copyright 2009-2013
[Cake Development Corporation](http://cakedc.com)
1785 E. Sahara Avenue, Suite 490-423
Las Vegas, Nevada 89104
http://cakedc.com