| 开发者 | aipluginfactory |
|---|---|
| 更新时间 | 2026年10月13日 20:00 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
No. Recording a review only writes to the plugin's own tables. Post content, post_modified, and post meta of the reviewed content are never modified.
Revisions are automatic snapshots WordPress keeps when content is edited. This plugin records a human decision: who checked the content, when, with what outcome and note, and when it is due again. If the content is edited after a review, the queue flags it and links to the WordPress revision comparison.
Each item has a check interval in months (its own setting, or the default for its content type; 0 means no regular schedule). If no manual date is set, the due date is the interval added to the last review date, or to the post's last-modified date when it was never reviewed (month ends are clamped, e.g. 31 January + 1 month = 28/29 February). A manual date on the record always overrides the computed date. A "Needs follow-up" review without a chosen next date defaults to 7 days later.
No. It is optional and off by default. Turn it on under Settings to show your overdue count in the WordPress admin bar. It appears only inside the admin, never on the public site, and only when you have overdue items.
Anyone with edit_posts can open the queue, but without edit_others_posts they only see content they authored or own. Recording a review needs edit permission for that post. Changing schedules, owners, and bulk actions needs broader edit rights. Settings and log export are administrator-only (manage_options).
The review fingerprint includes title, content, excerpt, status and Elementor data, so Elementor edits are detected directly. Other builders store their output in post content, so their changes are covered through the content check.
Your records are kept and migrated into the new tables, including the imported review history. Deactivate the old plugin first and do not run both at the same time. Never run the old plugin's uninstaller against the shared data.
Yes. The weekly digest is sent by WordPress cron, so the site must receive visits for the schedule to run. Settings shows the last run, what was sent, and the next run; if the next run is more than 1 hour in the past you will see a "WP-Cron may not be running" warning. Low-traffic sites should set up a real server cron calling wp-cron.php. A "Send me a test digest" button checks delivery without waiting a week.
Deactivation keeps everything. Deleting the plugin (uninstall) drops both plugin tables, including any legacy table, and deletes all aipluginfactory_cr_* options and the digest schedule. Export anything you need first; deleting a post also removes its review record (the activity log rows are kept).
evosolve-content-review). Deactivate the earlier private build "Content Review: Dates & Notes" first; its records and history are migrated automatically.