| 开发者 | ashiquzzaman |
|---|---|
| 更新时间 | 2026年11月15日 01:14 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv3 or later |
| 版权网址: | 版权信息 |
checklistdek folder to the /wp-content/plugins/ directory on your hub server.checklistdek-client.php from the panel setup section in the site editor and upload the full client panel bundle to wp-content/mu-plugins/ on the client site.ChecklistDek is built for WordPress agencies, freelancers, and in-house web teams who manage multiple client sites and want repeatable checklists, client-visible progress in wp-admin, and audit-friendly history—without moving SOPs into a separate SaaS product.
Yes. Every managed remote site must have ChecklistDek’s bundled must-use client checklist panel in wp-content/mu-plugins/ (one-time setup per site). That panel is how checklists appear, how manual steps are completed, and how notes and progress sync with your hub. There is no supported “hub only, no client UI” workflow.
checklistdek-client.php from the panel setup block in the site editor (or onboarding / connection tester).wp-content/mu-plugins/ on the client site (create the folder if needed).mu-plugins or uploads automatically—you install the bundled files yourself. The client panel ships with ChecklistDek; it is not a separate WordPress.org plugin listing.
No. Email, exports, or hub-side tracking alone are not substitutes for the in-dashboard checklist experience ChecklistDek delivers through the client panel.
Yes. Integrations are optional. You can register sites manually with Application Passwords, deploy the client panel, and run checklists without any connector plugin.
Community (this WordPress.org plugin) is complete for its scope: unlimited hub sites, custom checklists, batch runs, integrations, Activity Logs, manual drift verification, 17 built-in templates in four categories, and three client panel layout choices in Settings. Client sites use the bundled mu-plugin you upload manually (this build does not auto-write panel files to remote servers). Pro and Agency are separate downloads from Asphalt Themes with a larger template library, Private Agency Vault, Auto-Capture, email and webhook notifications, scheduled drift cron, hub auto-deploy of the client panel, nine panel layout choices, and licensed site tiers on paid plans. Application Password encryption in Settings is included in Community and Pro. They replace this plugin on your hub; your existing sites and checklists stay in the database.
When enabled under Settings → Application password encryption, site Application Passwords are encrypted at rest using your WordPress salt keys. Decrypted passwords are never exposed in REST responses or audit entries shown to non-privileged users.
No. Application password encryption (Settings, included in Community and Pro) protects Application Passwords stored on your hub for remote site connections. Private Agency Vault is a Pro feature for saving your own checklists as reusable team templates on the Checklists → Templates tab—it does not store site passwords.
wp_mail when those events are enabled in the separate paid packageNo. WooCommerce-specific steps appear in some built-in templates, but the hub and client panel work with any WordPress 6.0+ site that supports Application Passwords and REST.
Yes. The hub can manage local and remote URLs. The remote client may require the ?rest_route= fallback when pretty permalinks are broken; ChecklistDek handles that automatically for REST calls. Admin-ajax handlers are used for some heavy lists on memory-constrained local installs.
Uninstall removes ChecklistDek tables, options, and custom capabilities from the hub site. Client sites retain the mu-plugin files until you remove them manually from wp-content/mu-plugins/. Completed hub run history is deleted with the plugin—export checklists first if you need archives.
Purchase from Asphalt Themes, install the Pro or Agency plugin package on your hub (replacing this WordPress.org build), and complete license activation in that package. Your existing sites and checklists remain in the database.
rest_route URLs and reject bogus HTTP 200 responses so step completions cannot silently fail when the hub is unreachable or misconfigured.wp_str_ends_with() is unavailable (replaced with PHP-compatible path suffix check).manage_options).checklistdek_checklists_after_builtin_templates hook lets Pro inject Private Agency Vault UI without vault markup in the free package.is_vault checklist column when Agency Vault is unavailable (cleanup omitted from WordPress.org zip).is_vault checklist column for Private Agency Vault.format_row(); legacy cached feed rows backfill show_site_label only.