Anil Parmar

manish24790

This is a woocommerce addon which helps to put like and dislike 
button on the product loop pages as well as on the single 
product page.
Woocommerce plugin is necessary to have to work this plugin.
Count is restricted based on IP address and one IP address user can 
give on like or dislike vote. 
Duplicate IP address user’s vote will be removed if already voted.

WooCommerce Like Counter

This is a woocommerce addon which helps to put like and dislike

erumfaham

Posts Like Dislike is the Free WordPress Plugin to enable Like and Dislike Icons for default WordPress Posts or blog page with different type of posts. Display Like and Dislike in text form with sliding Thumbs Up or Thumbs Down effect as well as how many people like/dislike the post show number of count aside with button. Immediately add the count when user clicked on button.
Posts Like Dislike increases the interaction with the WordPress posts/post types by enabling likes and dislikes buttons along with the count. These values are stored in database where those recodes are managed. Only Logged-in user can see Like/Dislike buttons at post page and like/dislike the post.
In addition, simply install it and it’s ready to go on the other hand its automatically show on post after the content section as well as create recodes in WordPress database when uninstalled plugin.
A few notes about the sections above:
<ul>
<li>“Contributors” erumfaham</li>
<li>“Tags” like, likes, dislike, dislikes, post like dislike, like dislike post, thumbs-up post, thumbs-down post, post value, post store in database</li>
<li>“Requires at least” 5.3 version that the plugin will work on</li>
<li>“Tested up to” is the highest 5.8 version that you’ve successfully used to test the plugin. Note that it might work on 
higher versions… this is just the highest one you’ve verified.</li>
<li>
Stable tag should indicate the Subversion “tag” of the latest stable version, or “trunk,” if you use <code>/trunk/</code> for 
stable.
Note that the <code>readme.txt</code> of the stable tag is the one that is considered the defining one for the plugin, so 
if the <code>/trunk/readme.txt</code> file says that the stable tag is <code>1.0.0</code>, then it is <code>/tags/1.0.0/readme.txt</code> that’ll be used 
for displaying information about the plugin. In this situation, the only thing considered from the trunk <code>readme.txt</code> 
is the stable tag pointer. Thus, if you develop in trunk, you can update the trunk <code>readme.txt</code> to reflect changes in 
your in-development version, without having that information incorrectly disclosed about the current stable version 
that lacks those changes — as long as the trunk’s <code>readme.txt</code> points to the correct stable tag.
If no stable tag is provided, it is assumed that trunk is stable, but you should specify “trunk” if that’s where 
you put the stable version, in order to eliminate any doubt.
</li>
</ul>
<h3>A brief Markdown Example</h3>
Ordered list:
<ol>
<li>Automatically buttons showed on all post after the content.</li>
<li>It stores the values in database.</li>
<li>It also show the liked or disliked counts on screen where users can idealize about the popularity of post.</li>
</ol>
Unordered list:
<ul>
<li>something</li>
<li>something else</li>
<li>third thing</li>
</ul>
Here’s a link to <a href="https://wordpress.org/" title="Your favorite software" rel="ugc">WordPress</a> and one to <a href="https://daringfireball.net/projects/markdown/syntax" title="Markdown is what the parser uses to process much of the readme file" rel="nofollow ugc">Markdown’s Syntax Documentation</a>. 
Titles are optional, naturally.
Markdown uses email style notation for blockquotes and I’ve been told:
<blockquote>
Asterisks for emphasis. Double it up for strong.
</blockquote>
<pre><code><?php code(); // goes in backticks ?>
</code></pre>

Likes and Dislikes Plugin

It helps to like or dislike post as well as store its value in database against user ID and post ID.

WooCommerce Like Counter vs Likes and Dislikes Plugin