DateSweep
| 开发者 | digtiz |
|---|---|
| 更新时间 | 2026年7月22日 17:57 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPL-2.0-or-later |
| 版权网址: | 版权信息 |
详情介绍:
- Pre-launch freshness pass — you built a new site from an older template or a copy of an existing site, and everything still carries dates from years ago. One run on the "All content" tab (optionally with drafts included and both dates set equal) makes the whole site look current before launch.
- After an import or migration — imported content often ends up with a single identical date on every post, or wrong dates from a timezone mix-up. Spread realistic dates across a chosen range in one pass.
- Content maintenance for SEO — you reviewed and batch-edited older articles and want their modified dates to reflect that work naturally over the past weeks instead of one suspicious spike.
- Comments that match — after an import, comments dated before their own posts look broken. The Comments tab redates them plausibly (a comment is never dated before its post).
- Batched AJAX processing with a live progress bar — works on sites with tens of thousands of posts without PHP timeouts.
- All public post types — posts, pages and custom post types each get their own tab, plus a Comments tab.
- Filter by any taxonomy (categories, tags, custom taxonomies) with AND/OR relation, or pick specific pages.
- Choose the field: modified date, published date, or both set equal.
- Safety guard: never sets a modified date earlier than the published date (the classic plugin's known flaw).
- Comments stay plausible: a comment is never dated before its parent post.
- No external CDNs — native date pickers, vanilla JavaScript, everything loaded locally.
- Undo built in: every run records the previous dates first, and your most recent run can be restored with one click.
- Hardened: capability checks, nonces, full input sanitization and output escaping, prepared SQL statements, object-cache invalidation after every update.
- Developer friendly: actions and filters for every stage (
datesweep_post_dates_updated,datesweep_collected_post_ids,datesweep_new_timestamp,datesweep_form_rowsand more).
安装:
- Upload the
datesweepfolder to/wp-content/plugins/, or install the zip via Plugins → Add New → Upload. - Activate the plugin.
- Go to Tools → DateSweep, pick a tab, choose a range and click Update Dates.
屏幕截图:
常见问题:
Will this time out on a large site?
No. Items are processed in batches of 100 over AJAX; the browser drives the queue and shows progress. Only the ID collection happens up front.
Can I undo an update?
Yes. Every run records the previous dates before writing, and the Recent runs list on the plugin page lets you undo your most recent run with one click. DateSweep Pro extends this to an undo history of your last 10 runs. A database backup before large operations is still good practice.
Does it change dates in the future?
No. The range is always capped at the current time.
Does it change my content?
No. Only the date columns of posts/pages (post_date, post_modified and their GMT counterparts) or comment dates are touched. Titles, content, excerpts, custom fields and settings are never modified.
Does it work with page builders like Elementor, Avada or Divi?
Yes. Builders store their layouts in content and meta fields, which DateSweep never touches — only the core date columns change. If your theme displays a date from a custom field instead of the WordPress date, see DateSweep Pro's ACF integration.
Does it work with custom post types?
Yes, automatically. Every public custom post type — whether registered by a theme, a plugin or ACF — gets its own tab and is included in the "All content" pass.
Is it safe for SEO? Will Google penalize me?
DateSweep changes dates, not content. Search engines reward genuinely updated content; refreshing dates without any real changes can be ignored or, at worst, erode trust in your dates. Use it where the dates are genuinely misleading (imports, rebuilds, migrations) or alongside real content maintenance — not as a substitute for it.
Why did nothing change on my site after a run?
Your dates did change in the database — but a caching plugin or CDN may still serve old pages. Clear your page cache after a run. (Object caches are already flushed automatically.)
Where do I find the plugin after activating it?
Under Tools → DateSweep.
Can I schedule automatic refreshes?
That's a DateSweep Pro feature: daily, weekly or monthly schedules with a "Save & Run Now" button, age targeting so recently edited content is left alone, and IndexNow submission so search engines re-crawl the refreshed URLs quickly.
更新日志:
- Renamed internal prefixes to
datesweep_(fromdsw_) to meet WordPress.org’s 4-character prefix guideline. Fresh installs only; no data migration. Removed bundled translation files and the manual textdomain load (WordPress.org handles translations automatically).
- Undo history: the free plugin keeps your most recent run (previously 5). The new
datesweep_keep_runsfilter lets add-ons extend the history — DateSweep Pro keeps the last 10 runs.
- The "no items match" check now runs after extensions filter the job, so add-ons that narrow the selection (e.g. age targeting) report empty results correctly.
- Undo progress and success message now count items (posts/comments) instead of internal snapshot rows, so runs that include ACF fields report correct numbers.
- Plugin renamed to DateSweep. Slug, text domain and all internal prefixes updated (
datesweep_). No functional changes.
- New extension seams for add-ons:
datesweep_form_rowsaction (extra form rows),datesweep_job_datafilter (attach data to a job),datesweep_batch_processedaction (post-batch processing) anddatesweep_restore_snapshotaction (restore custom snapshot types).
- Translations added: German (de_DE), Dutch (nl_NL, nl_BE) and French (fr_FR, fr_BE), plus a POT template.
- The dry-run preview limit is now filterable (
datesweep_preview_limit) for the Pro add-on. - New public helper
DSW_Processor::range_from_preset()used by scheduled (Pro) runs. - Confirmation dialog now mentions that runs can be undone.
- Undo/rollback: every run snapshots the previous dates before writing; the new "Recent runs" list restores them with one click (batched, with progress).
- The last 5 runs are kept; snapshots are pruned automatically and removed on uninstall.
- New action hook:
datesweep_post_dates_restored.
- New "All content" tab: one freshness pass across every public post type at once — ideal before launching a site built from an older template.
- Dry-run preview: see current → proposed dates for a sample of matching items before committing.
- Post status selection: optionally include drafts, pending and private items.
- New extension filters:
datesweep_collected_post_ids,datesweep_new_timestamp.
- Complete rewrite: OOP architecture, batched AJAX processing with progress bar.
- Native date pickers; removed all CDN dependencies (moment.js, daterangepicker).
- Full sanitization, escaping, nonce and capability hardening.
- Fixed: modified date can no longer be set before the published date (optional guard, on by default).
- Object cache is now invalidated after every update.
- Added
datesweep_post_dates_updatedaction hook. - Uninstall cleanup.