I have a project that uses 6 different databases, most of all my important data is in a database different from the main Laravel database that I called "core". However my main User database is in the main "core" database, almost everything else is in a 'data' database.

Using this setup I am able to use Laravel Love without a hitch so far.. I can add/remove reactions and all the tables and counts are working correctly.

My main use of Laravel Love is that users can like other users. Very simple.

Today I tried to do this:

$users = User::with('profile')->whereReactedBy($user, 'Like')->get();

And I ran into this error:

<!--
Illuminate\Database\QueryException: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'core.love_reactants' doesn't exist (SQL: select * from `core`.`users` where exists (select * from `love_reactants` where `core`.`users`.`love_reactant_id` = `love_reactants`.`id` and exists (select * from `love_reactions` where `love_reactants`.`id` = `love_reactions`.`reactant_id` and `reacter_id` = 6176 and `reaction_type_id` = 1)) and `core`.`users`.`deleted_at` is null) in file /Volumes/Memories/Photos/2012/PictureBright/DEV/_NS/2020/omega-api.nomadsoulmates.com/vendor/laravel/framework/src/Illuminate/Database/Connection.php on line 671

I've run into such issues with other relations cross-database and usually the fix is as simple as going inside the model file and prefixing the table with the database name

So something like this:

class Comment extends Model
{
    protected $table = 'data.matches';

The problem is I can't do this with the Love models since they are in your codebase. I haven't tried binding my own models in place of yours so I can add this one extra line.

I did define in the love.php configuration file that it should use my database connection and things have worked so far. I guess this would work if you also prefixed the database name to the definition of your tables in your vendor models when the user specifies a custom database connection.

If you have another solution to offer I would love to hear it.

Thank you very much!

Resolves #105

Need to add 2 Artisan commands for populating love_reacter_id & love_reactant_id columns.

Register Reacterable models as Reacter

Variant 1

love:register-reacter --model=User --ids=1,2

Variant 2

love:reacter-register --model=User --ids=1,2

Variant 3

love:register reacter --model=User --ids=1,2

Variant 4

love:reacter register --model=User --ids=1,2

Variant 5

able:register love-reacter --model=User --ids=1,2

Register Reactable models as Reactant.

Variant 1

love:register-reactant --model=Comment --ids=1,2

Variant 2

love:reactant-register --model=Comment --ids=1,2

Variant 3

love:register reactant --model=Comment --ids=1,2

Variant 4

love:reactant register --model=Comment --ids=1,2

Variant 5

able:register love-reactant --model=Comment --ids=1,2

Proof of concept https://github.com/cybercog/laravel-love/issues/164#issuecomment-622610209 Resolves #163

Define any custom table name in config/love.php file

'storage' => [
    'database' => [
        'connection' => env('DB_CONNECTION', 'mysql'),
        'tables' => [
            'love_reacters' => 'custom_reacters',
            'love_reactants' => 'custom_reactants',
            'love_reaction_types' => 'data.reaction_types',
        ],
    ],
],

Table names with null value will use values from Model's $table class property.

Different schema/database could be defined for cross-schema queries by adding its name with dot on the end before the table name, eg. data.reaction_types. More details read in #163

hi, I'm fighting with this package a bit owing to the lack of examples and have a bunch on quesitons.

In order to keep the processing to a minimum, I would like to get the name of the reaction from the getReactionCounters(). currently I don't think this is possible. or is it?

• I don't seem to be able to see a way to get love_reaction_type table data from getReactionCounters()

Would you have an example to achieve this please?

hey @antonkomarev Am trying to use the react to function, the new react has been stored successfully in love_reactions table, while cannot store the related records in love_reactant_reaction_counters and love_reactant_reaction_totals so I cannot get the reaction count!

here is my code for following up: Am using **MySQL 5.6

function reactTo($type,  $weight = 1)
    {
        $user = getAuthUser();
        if ($user){
            // get reaction type
            if (is_null($type)){
                $type = 'like';
            }
            $reactionType = ReactionType::fromName($type);
            $typeName = $reactionType->getName(); 

            if ($this->isNotRegisteredAsLoveReactant()){
                $this->registerAsLoveReactant();
            }

            if ($user->isNotRegisteredAsLoveReacter()){ // false
                $user->registerAsLoveReacter();
            }
            $reacterFacade = $user->viaLoveReacter();

            $isNotReacted = $reacterFacade->hasNotReactedTo($this);
            if ($isNotReacted){
                $reacterFacade->reactTo($this, $typeName, $weight);
            }
        }
        return false;
    }

It seems that as a result of the PR here https://github.com/cybercog/laravel-love/pull/11

Even if you publish the migrations, the changes are ignored and instead the package's migrations are used.

On a side note, I personally feel that it was ok how you were doing it before, that in order to use the package the user is required to publish the migrations first.. this is how 90% of packages that depend on migrations are doing it.. and it leaves more flexibility

So I would just revert that PR and include publishing the migrations in the docs, which you already do.

I love the package but the background jobs are being process after the view is being send to the frontend which makes it very strange for the user. So if we have a website with posts. Each post have love and hate reaction. If the user clicks to add a new reaction because this reactions are processed in the background the user needs to wait few seconds which is not possible in some cases or not good.

@cybercog Can you explain how to deal with this? The easiest way is to specify queue which to process this reactions.

Idea by @jwktje first appeared in Reddit comment.

Allow someone to vote/react once per day for example.

Need to collect all feature requirements before implementation.

Possible names:

• Reaction Power
• Reaction Rate
• Reaction Force
• Reaction Strength

Case 1

Allow Reacter to react to Reactant with same reaction type more than once.

Example: In social news application user Jane can vote up article up to 5 times.

Similar to Medium's Claps:

• https://uxdesign.cc/fifty-shades-of-claps-a-case-study-for-clapping-on-medium-22c6e7b71140

Case 2

Reacter has some kind of authority inside of the application and his reactions should have more weight among others.

Example: In Question & Answer application user Jane solved more than 1000 questions. Jane's reactions will have more power now.

Additionally by this way it will be easier segregate reactions from more notable application users.

Fairly straightforward. These two artisan commands can be invoked to register any or all existing model rows for reactants or reacters. Both commands accept the same parameters, as outlined below.

Command Help

Here is the output of artisan help for the love:register-reactant command (the reacter command follows a similar pattern):

Use Cases

Process all records for the passed model:

php artisan love:register-reactables App\\Models\\Entry
php artisan love:register-reacters App\\Models\\User

Process specific records for the passed model:

php artisan love:register-reactables App\\Models\\Entry --ids=1,2,3,4,19
php artisan love:register-reacters App\\Models\\User --ids=200,312,319

Sample output (yes, I love progress bars lol):

Feel free to merge and make any changes or tweaks that you feel necessary.

Hi, my scenario is I'm showing all the recent posts to user and I have added the heart icon on each post and when the user likes a post it's highlighted in red and if not it's just showing the border of the heart. so that the user knows a post has already been liked or no. the question is how to highlight the posts that like by the user with in all posts. That's my code: My controller:

 $newUser = User::where('uid', '=', $user->uid)->first();

        $posts = Post::where('status', 'published')->latest()->take(75)->get();

        //Return collection of posts as resource
        return PostSource::collection($posts);

My resource:

public function toArray($request)
    {
        return [
        'id' => $this->id,
        'source_id' => SourceResource::collection($this->whenLoaded('source')),
        'source_name' => $this->source,
        'category_id' => CategoryResource::collection($this->whenLoaded('category')),
        'category_name' => $this->category,
        'fav_info' => $this->users,
        'title' => $this->title,
        'created_at' => $this->created_at,
        ];
    }

So I know there's nothing in the code above related to this library but I;m already using it to add likes and deslikes and grab the current users posts that he liked. but I can't highlight the liked posts within all the posts. Thanks

I got these warnings with this package:

[2022-12-22 23:49:49] local.WARNING: Since symfony/console 6.1: Relying on the static property "$defaultName" for setting a command name is deprecated. Add the "Symfony\Component\Console\Attribute\AsCommand" attribute to the "Cog\Laravel\Love\Console\Commands\ReactionTypeAdd" class instead. in /home/project/vendor/symfony/deprecation-contracts/function.php on line 25  
[2022-12-22 23:49:49] local.WARNING: Since symfony/console 6.1: Relying on the static property "$defaultName" for setting a command name is deprecated. Add the "Symfony\Component\Console\Attribute\AsCommand" attribute to the "Cog\Laravel\Love\Console\Commands\Recount" class instead. in /home/project/vendor/symfony/deprecation-contracts/function.php on line 25  
[2022-12-22 23:49:49] local.WARNING: Since symfony/console 6.1: Relying on the static property "$defaultName" for setting a command name is deprecated. Add the "Symfony\Component\Console\Attribute\AsCommand" attribute to the "Cog\Laravel\Love\Console\Commands\SetupReactable" class instead. in /home/project/vendor/symfony/deprecation-contracts/function.php on line 25  
[2022-12-22 23:49:49] local.WARNING: Since symfony/console 6.1: Relying on the static property "$defaultName" for setting a command name is deprecated. Add the "Symfony\Component\Console\Attribute\AsCommand" attribute to the "Cog\Laravel\Love\Console\Commands\SetupReacterable" class instead. in /home/project/vendor/symfony/deprecation-contracts/function.php on line 25  
[2022-12-22 23:49:49] local.WARNING: Since symfony/console 6.1: Relying on the static property "$defaultName" for setting a command name is deprecated. Add the "Symfony\Component\Console\Attribute\AsCommand" attribute to the "Cog\Laravel\Love\Console\Commands\RegisterReactants" class instead. in /home/project/vendor/symfony/deprecation-contracts/function.php on line 25  
[2022-12-22 23:49:49] local.WARNING: Since symfony/console 6.1: Relying on the static property "$defaultName" for setting a command name is deprecated. Add the "Symfony\Component\Console\Attribute\AsCommand" attribute to the "Cog\Laravel\Love\Console\Commands\RegisterReacters" class instead. in /home/project/vendor/symfony/deprecation-contracts/function.php on line 25  
[2022-12-22 23:49:49] local.WARNING: Since symfony/console 6.1: Relying on the static property "$defaultName" for setting a command name is deprecated. Add the "Symfony\Component\Console\Attribute\AsCommand" attribute to the "Cog\Laravel\Love\Console\Commands\UpgradeV5ToV6" class instead. in /home/project/vendor/symfony/deprecation-contracts/function.php on line 25  
[2022-12-22 23:49:49] local.WARNING: Since symfony/console 6.1: Relying on the static property "$defaultName" for setting a command name is deprecated. Add the "Symfony\Component\Console\Attribute\AsCommand" attribute to the "Cog\Laravel\Love\Console\Commands\UpgradeV7ToV8" class instead. in /home/project/vendor/symfony/deprecation-contracts/function.php on line 25  

I've looked all through the github info, and all through the docs here: https://laravel-love.readme.io/docs but still can't find a way to see it. Help.

The joinReactionTotal (scopeJoinReactionTotal) all scoped methods are not working with a database prefix. You get an "column not found" error.

This is a continuation of an idea started in https://github.com/cybercog/laravel-love/issues/181

I would find it extremely useful to be able to easily retrieve the reaction date when using scopeWhereReactedTo or scopeWhereReactedBy

I have users liking other users and I would like to be able to display to a user who has liked them and when specifically that like has been received

Right now those scopes return the users that have reacted to/by the specfied reaction type.. but I'm not seeing an easy way to also retrieve more details about that reaction, namely the datetime it occurred at

The following lends itself to a n+1 problem.. but this is the workaround I came up with to retrieve the raw reaction from the db table in order to expose the datetime of the reaction itself which is useful in my case

$rawReaction = (new Love)->getRawReaction($user, User::find(request('viaResourceId')), 'LIKE');

<?php

namespace App\Helpers;

use App\Models\LoveReaction;

class Love
{
    public function getRawReaction($reactable, $reacterable, $reactionType)
    {
        $rawReaction = LoveReaction::where('reactant_id', $reactable->love_reactant_id)
        ->where('reacter_id', $reacterable->love_reacter_id)
        ->where('reaction_type_id', config('love.reaction-types')[$reactionType])
        ->first();

        return $rawReaction;
    }
}

<?php

namespace App\Models;

use Illuminate\Database\Eloquent\Model;

class LoveReaction extends Model
{
    protected $table = 'love_reactions';
}

When I try to use $model->likeBy($user->id) the following is returned:

Call to undefined method App\Product::likeBy() {"exception":"[object] (BadMethodCallException(code: 0): Call to undefined method App\\Product::likeBy() at /home/vagrant/sites/site-server/vendor/laravel/framework/src/Illuminate/Support/Traits/ForwardsCalls.php:50)

In order to trigger a like action (or at least see data land in the love_reactions table), I have to use this pretty verbose code:

$reactionType = ReactionType::fromName('Like');
$reacter = $user->getLoveReacter();
$reactant = $product->getLoveReactant();
$reaction = $reacter->reactTo($reactant, $reactionType);

Yet when I dd($reaction) it is empty.

What am I missing here? The readme or documentation doesn't really explain how to explicitly set a like/dislike, so I'm really grabbing what I can from closed tickets and a lot of trail and error.

This MR adds whereReactedTo & whereNotReactedTo query scopes to Reacterable trait to find all Reacterable models who reacted to the Reactable model. This concept was born after discussion with @vesper8 in #181

Find users who reacted with any type of reaction to the article

$article = Article::whereKey(1)->firstOrFail();

$usersReactedToArticle = User::whereReactedTo($article);

Find users who reacted with one concerete type of reaction to the article

$article = Article::whereKey(1)->firstOrFail();
$likeReactionType = ReactionType::fromName('Like');

$usersLikedTheArticle = User::whereReactedTo($article, $likeReactionType);

This MR doesn't have tests yet and I'm not sure if we should add it to the minor release.