內容簡介
Posts Like Dislike 是一個免費的 WordPress 外掛，可為預設 WordPress 文章或部落格頁面與不同類型的文章啟用「讚」和「踩」圖示。以滑動的「讚」或「踩」效果以文字形式顯示「讚」和「踩」，以及「喜歡/不喜歡」文章的人數，並在按鈕旁邊顯示數量計數。點擊按鈕時立即增加計數。
Posts Like Dislike 通過啟用「讚」和「踩」按鈕以及數量計數來增加與 WordPress 文章/文章類型的互動。這些值存儲在數據庫中，這些記錄是由插件管理的。只有已登錄的用戶可以在文章頁面上看到讚/踩按鈕並喜歡/不喜歡文章。
此外，只需安裝它，它就可以隨時使用，另一方面，當卸載插件時，它會自動顯示在文章的內容部分之後，並在 WordPress 數據庫中創建記錄。
關於上面的部分的一些注意事項：
“Contributors” erumfaham
“Tags” like, likes, dislike, dislikes, post like dislike, like dislike post, thumbs-up post, thumbs-down post, post value, post store in database
“Requires at least” 5.3 版本是插件運行的最低版本
“Tested up to” 是您已成功使用測試該插件的最高版本 5.8。請注意，它可能適用於更高版本...... 這只是您驗證過的最高版本。
穩定標籤應該指最新穩定版本的 Subversion“標籤”，或“trunk”，如果您使用
穩定的/的/code>/，它可以穩定。
請注意，穩定標籤的readme.txt是被視為定義插件的文件，所以，如果/trunk/readme.txt文件說穩定標籤是1.0.0，那麼就是/tags/1.0使用來顯示有關插件的信息。在這種情況下，唯一從樹幹readme.txt認為是穩定的標籤指針。因此，如果您在樹幹中開發，您可以更新樹幹readme.txt，以反映在開發版本中的更改，而沒有將那些變更不正確地披露有關當前穩定版本的信息，缺少這些變更 - 只要樹幹的readme.txt指向正確的穩定標籤。
如果未提供穩定標籤，則假定樹幹是穩定的，但如果您將穩定版本放在樹幹中，則應指定“樹幹”，以消除任何疑問。
簡短的 Markdown 示例
有序列表：
自動顯示所有帖子後按鈕。
它在數據庫中存儲值。
它還顯示了在用戶可以理想化文章的受歡迎程度的屏幕上喜歡或不喜歡的次數。
無序列表：
某事
其他事情
第三個東西
這裡是連接到WordPress和 Markdown 語法文檔 的 link。 標題是可選的。
Markdown使用電子郵件樣式的表示方法進行引用，我被告知：
用星號進行強調。 加倍強調加強。
<?php code(); // goes in backticks ?>
外掛標籤
開發者團隊
原文外掛簡介
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:
“Contributors” erumfaham
“Tags” like, likes, dislike, dislikes, post like dislike, like dislike post, thumbs-up post, thumbs-down post, post value, post store in database
“Requires at least” 5.3 version that the plugin will work on
“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.
Stable tag should indicate the Subversion “tag” of the latest stable version, or “trunk,” if you use /trunk/ for
stable.
Note that the readme.txt of the stable tag is the one that is considered the defining one for the plugin, so
if the /trunk/readme.txt file says that the stable tag is 1.0.0, then it is /tags/1.0.0/readme.txt that’ll be used
for displaying information about the plugin. In this situation, the only thing considered from the trunk readme.txt
is the stable tag pointer. Thus, if you develop in trunk, you can update the trunk readme.txt 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 readme.txt 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.
A brief Markdown Example
Ordered list:
Automatically buttons showed on all post after the content.
It stores the values in database.
It also show the liked or disliked counts on screen where users can idealize about the popularity of post.
Unordered list:
something
something else
third thing
Here’s a link to WordPress and one to Markdown’s Syntax Documentation.
Titles are optional, naturally.
Markdown uses email style notation for blockquotes and I’ve been told:
Asterisks for emphasis. Double it up for strong.
