1.4.0 2017-02-05 13:15 UTC

This package is not auto-updated.

Last update: 2020-10-25 19:06:58 UTC


This is a complete upvote and downvote solution for Laravel >= 5.3.

  • Allows upvoting & downvoting, binary or multiple steps.
  • Records memos (comments) by the voting user in the same table.
  • Out-of-the-box migration tool for data from rtconner/laravel-likeable package.
  • Allows assigning objects to favorite categories (only one per voted object though).

Contributors welcome. Any feature suggestions? Submit an issue.

Current version:

Latest Stable Version Total Downloads

List of all features

This package delivers several solutions working in the same DB table. Pick one or use all to get functionality you need. Three values available for storing likes and upvotes are up to you: binary, negative value or null.

  • importance - might be used for observing and prioritizing content with values from range 0 to 10, or just any, including negative.

  • attitude - might store values -1, 0, 1 for dislikes and likes (upvotes and downvotes). As above, the scope of the values can be decided by developer, e. -2 for hate and -3 for going Berserk over the object is possible.

  • activated - just to give an example the field might store values -1, 0, 1. Useful for for content filtering features.

  • favoritetype_id - Just a scaffold for future development. An item might be stored in favorites under a certain subcategory. null would mean the root folder. This feature would require an extra model Favoritetype.

  • user_notes - allows user to take notes concerning a model (still to do). I suggest a maximum number of characters at 150, so that the table won't be heavy.

To do

  • functions for votes counters
  • example views for various cases of voting counters
  • example for adding user notes
  • splitting the collection used for migrating from rtconner - now it submits to php timeout limits


While the package does the job perfectly now, please give me some time to make the code look more professional. Contributors welcome!


  1. Add this line to your 'composer.json`

"unrulynatives/attitudes": "^1.0"

  1. register the service provider in config/app.php.


  2. In your User.php model register this trait.

    use Unrulynatives\Attitudes\AttitudesUserExtensions;

    class User extends Authenticatable

    use AttitudesUserExtensions;

The trait will make these two functions available. (As an alternative, you can implement them directly in the model file.)

    public function importances() {
        return $this->hasMany(\App\Models\Userattitude::class, 'creator_id');
    public function attitudes() {
        return $this->hasMany(\App\Models\Userattitude::class, 'creator_id');

  1. Register trait in your models

To all models you want to enable the voting ystem, register this trait:

use Unrulynatives\Attitudes\UserAttitudes;

class Yourmodelname extends Model  {

    use UserAttitudes;

The trait will make the below three functions available. (As an alternative, you can implement them directly in the model file.)

    public function importances() {
        return $this->hasMany(\App\Models\Userattitude::class, 'creator_id');
    public function attitudes() {
        return $this->hasMany(\App\Models\Userattitude::class, 'creator_id');

    public function user_approach($user)
        return $this->morphMany(\App\Models\Userattitude::class, 'item')->where('creator_id', ($user ? $user->id : NULL))->first();


  1. Publish assets Publish migrations, views, controller and other assets from this package into your Laravel app:

php artisan vendor:publish --provider="Unrulynatives\Attitudes\AttitudesServiceProvider" --force

  1. Run migrations Now run the migrations with command php artisan migrate. Verify that the table userattitudes was created.

Note: make sure to make your adjustments on copies, as newer version of this package might overwrite your changes (note the --force option in the publish command.)

  1. (optional) Setup the demo feature

While the DB in demonstration page will be seeded by controller function, you can also seed the DB here.

in your \database\seeds\DatabaseSeeder.php run() function declare this seed file: \database\seeds\UnAQuotationsTableSeeder.php and run php artisan db:seed.

8. (optional) Use your own routes 

Properly working routes necessary for this package to work are locatad within ths package:

Route::any('{itemkind}/{id}/set_user_attitude', ['as' => 'attitudes.set_user_attitude', 'uses' => 'AttitudesController@set_user_attitude']); Route::any('{itemkind}/{id}/set_user_importance', ['as' => 'attitudes.set_user_importance', 'uses' => 'AttitudesController@set_user_importance']);

You can put them in your location of choice, but make sure that the new location is parsed first. In case of problems, reverse the order of service providers of this package and `App\Providers\RouteServiceProvider::class,`

9. Attach the js and css files to your template. 

Mind the file paths if you decide to place them somewhere else than they are published to.

<script type="text/javascript" src="{{URL::to('js/minitool_attitudes.js')}}"></script>

10. Include the below view files in your `foreach` loop. Note that the looped variable should be changed accordingly. Here I use `$o->`.

<?php $itemkind = 'quotes'; ?> // features is a name of your model
@include('userattitudes._userattitudes_attitude_toggle_abstracted', ['itemkind' => $itemkind,'o' => $o, 'attitude' => (($cua = $o->user_approach(Auth::user())) ? $cua->attitude : NULL)])

@include('userattitudes._userattitudes_importance_toggle_abstracted', ['itemkind' => $itemkind,'o' => $o, 'importance' => (($cua = $o->user_approach(Auth::user())) ? $cua->importance : NULL)])
Note: `itemkind` is plural lovercase name of your model. Take a look at the controller function: the `itemkind` name is changed into class name in order to process your request.

11. Define the morph class
The models which are attituded should have the morph class defined. The names are stored in the DB table `userattitudes` in column `item_type`.
I myself define the morph class definitions manually, just to be sure that Laravel functions won't use some unusual defaults. 
Do it in `app\Providers\AppServiceProvider.php`. Use the instructions in https://laravel.com/docs/5.3/upgrade.

For this package to work with predefined example, open the file and inside the 
put the following code:

use Illuminate\Database\Eloquent\Relations\Relation;

// ...

public function boot()

        'user' => User::class,
        'quotation' => \App\Models\UnAQuotation::class,

12. Define a csrf token
Be sure that the head of your page contains the below declaration, otherwise you will meet with unexpected behavior of the script:
`<meta name="csrf-token" content="{{ csrf_token() }}" />`

### That's it! Now  user choices should be stored in the database table `userattitudes`.

## Working demo. 

If you installed this package correctly, point your browser to `attitudes-demo`.
- You should be logged in
- you sould have the `app\Models\Feature` model defined and at least one record in your database present. You can just simply use your own model for your test run - it's up to you.

An online demo is available at http://dev.unrulynatives.com/attitudes-demo

## Data migration from other packages

Added feature to migrate data from rtconner's package. See url `attitudes-migrate-likeable`

## Usage & Examples

### Count total votes of an object

`$this->countallvotes` - prints total number of votes cast by all users
`$this->countdownvotes`- prints total number of DOWN-votes cast by all users
`$this->countupvotes`- prints total number of UP-votes cast by all users

### collections
- `Quotation::whereUpvotedBy(Auth::id())->get();` // collection of Quotations upvoted by the user
- `Quotation::whereDownvotedBy(Auth::id())->get();` // collection of Quotations downvoted by the user
- `Quotation::whereVotedBy(Auth::id())->get();` // collection of Quotations voted in any way by the user (mind that the function counts records existing in DB, so it includes `null` and `0`)

### backend

IMPORTANT NOTE: In this package the assumed convention for model names is singular with capitalized first letter.
Mind the variable `itemkind`. It MUST be plural form of your model name.
If you have another system, you must rework the backend solutions of this package.

### Frontend

After publishing the views, in your app's `resources/views/` folder you will find a folder `userattitudes`. Inside you will find several files. In files included by the below templates you can define classes for your voting buttons and model affected by them. 
To have everything work well, start with including

(works with Bootstrap 4 and font Awesome (for thumbs up & down icons))

Other frontend solutions
`@include('userattitudes.set_attitudes_1')` will work nice with 
(works well with the UnrulyNatives Starter Kit package - need extra icon fonts installed)

## Help and documentation

point your browser to `attitudes-docs` to see instructions. If you cannot see the docs, then you have a problem to solve. Good luck!
After you use the `publish` command, the file will be located at `resources/views/userattitudes/features/index.blade.php`