內容簡介
Shared Counts 是一個 WordPress 社交媒體分享按鈕外掛。分享按鈕可以增加流量和參與度，幫助讀者將您的文章和頁面分享給他們在社交媒體上的朋友。
包含的按鈕:
Facebook 分享按鈕
Pinterest Pin 按鈕
Yummly 按鈕
Twitter Tweet 按鈕（使用第三方 Twitcount.com API）
電子郵件分享（帶有 reCAPTCHA 支持，以防止濫用）
分享計數總數
列印按鈕
LinkedIn 分享按鈕
Facebook、Pinterest、Yummly 和 Twitter 按鈕支援社交計數顯示和追蹤。
基本使用方法
在「設置 > Shared Counts」內，您可以選擇自動顯示分享按鈕的位置（文章內容前、後或前後）。編輯文章時，您可以在右側欄位的「Shared Counts」框中使用勾選框，以停用此特定文章的自動按鈕。
您可以使用 [shared_counts] 簡碼來手動顯示按鈕。
風格和顯示
我們包括許多分享按鈕風格選項，因此您可以為站點選擇完美的外觀。此外，您還可以自動在文章內容前後插入分享按鈕。想要更精細或手動控制？沒問題！您還可以使用 [shared_counts] 簡碼，將其插入到您覺得合適的內容中。
HTTP 回復 / 升級到 HTTPS
我們提供了一個點擊操作，以恢復 HTTP 和 HTTPS 的分享計數，確保您在將網站升級到 HTTPS 時不會丟失計數。
GDPR
與其他社交分享工具不同，此外掛不使用 cookie、追蹤腳本或存儲任何用戶數據。
效能
Shared Counts 是針對網站效能而建立的，即使在大規模的環境下也是如此。它被用於數個每月有數千萬次頁面瀏覽量的大型網站上。我們獨特而富有創意的緩存方法對站點的開銷影響極小。藉助 SharedCount.com API，我們可以在單個請求中檢索（幾乎）所有分享計數。
開發人員
此外，Shared Counts 還是以開發人員為主的！我們提供了非常寬鬆的勾子和過濾器使用。一切都可以自定義，可實現的可能性幾乎無限。與其他外掛不同，所有數據（計數）都存儲和緩存於 post_meta 中，易於存取和擴展（例如，獲取網站上分享次數前 10 的文章）。我們在我們的網站上有廣泛的文檔，並且我們也在GitHub上。
插件附加功能
Shared Counts - Pinterest Image - 上傳 Pinterest 分享的單獨圖像
Shared Counts - Cache Status - 建立和檢查 Shared Counts 緩存的狀態
自定義
有關詳細信息，請參閱Shared Counts 網站和我們的GitHub wiki。
錯誤
如果您發現任何錯誤或問題，請通過創建問題告訴我們。
貢獻
歡迎貢獻！
在
外掛標籤
開發者團隊
② 後台搜尋「Shared Counts – Social Media Share Buttons」→ 直接安裝（推薦）
原文外掛簡介
Shared Counts is a WordPress social media share buttons plugin. Sharing buttons increase traffic and engagement by helping readers share your posts and pages to their friends on social media.
Included Buttons
– Facebook Share Button
– Pinterest Pin Button
– Yummly Button
– Twitter Tweet Button (using the third-party Twitcount.com API)
– Email Sharing
– Share Count Total
– Print Button
– LinkedIn Share Button
Facebook, Pinterest, Yummly, and Twitter buttons support social count display and tracking.
Basic Usage
In Settings > Shared Counts you can select where the share buttons can appear automatically (Before Content, After Content, Before & After Content). When editing a post, you can use the checkbox in the “Shared Counts” box in the right column to disable the automatic buttons on this specific post.
You can use the [shared_counts] shortcode to manually display the buttons.
Styling and Display
We include many share button styling options, so you can pick the perfect look for you site. Additionally, you can automatically insert the share buttons before and/or after the post content. Want granular or manual control? No problem! You can also use the [shared_counts] shortcode to insert them inside your content as you see fit.
HTTP Recovery / Upgrading to HTTPS
We provide a one-click option to retrieve both HTTP and HTTPS share counts, ensuring you don’t lose your share counts when upgrading your website to HTTPS.
GDPR
Unlike other social sharing tools, this plugin does not use cookies, tracking scripts, or store any user data.
Performance
Shared Counts was created with site performance in mind, even at large scale. It is used on several large websites that get tens of millions of page views each month. Our unique and creative caching methods have a minimal affect on site overhead. Leveraging the SharedCount.com API, we can retrieve (almost) all share counts in a single request.
Developers
Additionally, Shared Counts was built to be developer friendly! We provide very liberal usage of hooks and filters. Everything is customizable and the possibilities are near limitless. Unlike other plugins all data (counts) are stored and cached in post_meta which makes it easy to access for extending (e.g. fetch top 10 most shared posts on your site). We have extensive documentation on our website and we’re also on GitHub.
Add On Plugins
Shared Counts – Pinterest Image – Upload a separate image for Pinterest sharing
Shared Counts – Cache Status – Build and check the status of the Shared Counts cache
Customization
For details on this please see the Shared Counts website and our GitHub wiki.
Bugs
If you find an bug or problem, please let us know by creating an issue.
Contributions
Contributions are welcome!
Open an Issue on GitHub.
Fork Shared Counts on GitHub.
Create a new branch off of develop; branch name should be issue/### to reference the issue.
When committing, reference your issue and provide notes/feedback.
Send us a Pull Request with your bug fixes and/or new features.
