[WordPress] 外掛分享: WP Developers Homepage

首頁外掛目錄 › WP Developers Homepage
WordPress 外掛 WP Developers Homepage 的封面圖片
⚠ 此外掛已下架 — 不再更新維護,建議勿安裝。
全新外掛
安裝啟用
尚無評分
837 天前
最後更新
問題解決
WordPress 5.0+ PHP 7.2+ v1.1.0 上架:2016-11-10

內容簡介

WP Developers Homepage 為 WordPress 外掛和佈景主題開發人員提供一個集中的地方,可以查看以下資訊:

查看並回應所有未解決的外掛和佈景主題支援要求。
查看所有外掛和佈景主題的有用統計數字。

基於 Mickey Kay 出色的 WP Dev Dashboard。

功能

將外掛和佈景主題支援要求以可排序的表格形式顯示,讓使用更容易。
以可排序和易於分析的表格形式顯示所有外掛和佈景主題。
按使用者名稱和/或 slug 選擇要顯示的外掛和佈景主題。
選擇是顯示所有支援票證還是僅未解決的票證。
實施快取以減少外掛和佈景主題支援票證資訊的加載時間。
包括快取破壞「刷新」選項,以強制刷新外掛和佈景主題支援票證資料。
排除外掛和佈景主題。
票證的附加資訊,包括上次張貼者和時間。
設定顯示的票證年齡限制。
設定新資料加載之前的逾時時間。
定期使用 WP Cron 工作後台加載資料。
Shortcode/Gutenberg 区塊以在前端顯示票證和統計資料。
選擇性地包括來自 GitHub 的票證。

GitHub 支援

在 GitHub 上託管外掛?WP Developers Homepage 也可以從那裡提取您的票證資訊!

只需將您的 GitHub 使用者名稱添加到 WP Developers Homepage 設定中。

注意:您的 GitHub 存儲庫必須與您的 slug 匹配。因此,例如,這個外掛的 slug 是 wp-developers-homepage,因此它的存儲庫的 GitHub url 是 https://github.com/toolstack/wp-developers-homepage。

WP Developers Homepage 使用 GitHub API 檢索票證資訊,默認情況下對未經身份驗證的用戶每小時限制為 60 個請求。每個外掛/佈景主題都將生成至少一個請求,如果您有大量票證(超過 100 張),則每個存儲庫將生成 1 個請求/每插件或主題的100項目。

因此,如果您有 5 個外掛,每個外掛有 150 張票證,您將生成 10 個請求(每外掛 2 次)。

如果您需要超過 60 個請求/每小時,可以 創建訪問權杖,以增加此限制。權杖應僅限於您擁有的插件/主題存儲庫,並且不應分配任何權限。請勿重用您已分配權限的現有權杖。

警告:存取權杖將以明文形式存儲在 WordPress 數據庫中!

獲取權杖後,進入 WP Developers Homepage 設定並保存它。

Shortcode

短碼的格式為 [wp-developers-homepage type=tickets|stats]。

type 可以省略(此時票證為預設值),也可以設置為 tickets 或 stats,以顯示相應的表格。

請注意,統計表格非常寬,因此如果您安裝的主題比較窄,它可能會溢出到滾動窗口中。

外掛標籤

開發者團隊

⬇ 下載最新版 (v1.1.0) 或搜尋安裝

① 下載 ZIP → 後台「外掛 › 安裝外掛 › 上傳外掛」
② 後台搜尋「WP Developers Homepage」→ 直接安裝(推薦)
📦 歷史版本下載

原文外掛簡介

WP Developers Homepage provides a central place for developers of WordPress plugins and themes to see their information:

View and respond to all of your unresolved plugin & theme support requests.
View useful statistics for all of your plugins & themes.

Based on Mickey Kay’s great WP Dev Dashboard.
Features

Displays plugin and theme support requests in a sortable table for ease of use.
Displays all plugins and themes in a sortable, easy-to-parse table.
Select which plugins and themes to show by username and/or slug.
Choose whether to show all support tickets, or just unresolved ones.
Implements caching to reduce load time for plugin and theme support ticket information.
Includes cache-busting “refresh” option to force refresh plugin and theme support ticket data.
Exclusion of plugins and themes.
Additional information on tickets, including last poster and time.
Set an age limit for the tickets displayed.
Set the timeout before new data is loaded.
Schedule a WP Cron job to load the data in the background.
Shortcode/Gutenberg Block to display both tickets and stats on the frontend.
Optionally includes tickets from GitHub.

GitHub Support
Host your plugins on GitHub? WP Developers Homepage can pull your ticket information from there too!
Simply add your GitHub username to the WP Developers Homepage settings.
Note: Your GitHub repos for your themes/plugins must match your slug. So for example, this plugin’s slug is wp-developers-homepage, so the GitHub url for it’s repo is https://github.com/toolstack/wp-developers-homepage.
WP Developers Homepage uses the GitHub API to retrieve the ticket information, which by default has a limit of 60 request/hour for unauthenticated users. Each plugin/theme you have will generate at least one request, and if you have a significant number of tickets (over 100) it will generate 1 request/repo/100 items.
So if you have 5 plugins, with 150 tickets per plugin, you’ll generate 10 requests (2 per plugin).
If you need more than 60 requests/hour, you can create an access token that will increase this limit. The token should be limited to the plugin/theme repos you have and should have no permission assigned to it. DO NOT reuse an existing token that you have assigned permissions to.
Warning: The access token will be stored in plain text inside of the WordPress database!
Once you have the token, go to the WP Developers Homepage settings and save it.
Shortcode
The shortcode is in the format of [wp-developers-homepage type=tickets|stats].
Type came be either left off (tickets are the default in that case), or be set to either tickets or stats to display the respective table.
Be aware that the stats table is very wide, so if you have a narrow theme installed it may overflow into a scrolling window.

延伸相關外掛

文章
Filter
Mastodon