LinkSentinel – Internal Link and Broken Link Scanner

Changelog

5.8

• Naming: Renamed all stored options, transients, the custom database table, cron events, AJAX/admin-post actions, nonces, and the localized admin script object to the unique link_sentinel_ / LinkSentinel prefix. Existing installs begin with a fresh scan history; re-run a scan to repopulate.
• Developer: Removed the legacy hook aliases retained in 5.6 — use the link_sentinel_* names.
• Compliance: Removed runtime error_reporting() adjustments in the scanner.

5.7

• Renamed the plugin to “LinkSentinel – Internal Link and Broken Link Scanner” for a clearer, more descriptive listing. No functional changes.

5.6

• Compliance: Addressed WordPress Plugin Check findings — escaped remaining admin output, added translators comments and ordered i18n placeholders, and unslashed/sanitized all request input.
• Developer: Public hooks renamed to the link_sentinel_* prefix (e.g. link_sentinel_follow_external_redirects); legacy aliases were retained for back-compat (removed in 5.8).
• Developer: Debug logging is now only written when WP_DEBUG is enabled.
• Removed the manual load_plugin_textdomain() call; WordPress loads translations automatically.

5.5

• Bug Fix: Redirects to a different domain with an identical path are no longer misclassified as self-redirects; they are now logged for review.
• Bug Fix: Starting a manual scan no longer resets a scan already in progress (e.g. one started by another admin).
• Bug Fix: The Change Link form now accepts site-relative paths (e.g. /about-us/) in addition to full http(s) URLs.
• Stability: The scan progress loop now stops with a clear message after repeated batch failures instead of retrying indefinitely.

5.4

• First public, open-source release under GPL-2.0-or-later.
• Security: reviewed and hardened AJAX handlers and database queries.
• Added a translation template (languages/link-sentinel.pot) and tidied translatable strings for full internationalization support.
• Hardened files against direct access and improved inline documentation.

5.2.2

• Critical Bug Fix: Fixed race condition where manually fixed broken links would become “stuck” in the pending queue during subsequent scans.
• Improved Duplicate Detection: Enhanced scanner logic to prevent re-logging manually resolved links regardless of resolution status.
• Database Efficiency: Optimized duplicate detection queries for better performance.
• Stability: Prevented infinite redirect loops with improved URL normalization.

5.0.1

• Batch processing for manual scans.
• Auto-fix permanently redirected links (301/308).
• Queue temporary redirects and broken links for review.
• Scheduled scans with timezone-aware cron control.
• Dashboard with progress indicators and CSV export.

4.6 – 2025-11-17

• Added: Resolve All batching controls in settings with checkbox gating, custom links-per-batch, and cooldown inputs to prevent rate limits.
• Added: Shared preference helper so PHP and JavaScript stay in sync when honoring user pacing choices.
• Improved: Resolve All localization, timers, and AJAX handler now respect saved batch/cooldown limits to avoid regressions.

4.4 – 2025-11-17

• Added: A throttled mode for hosts with strict rate limits — single-item batches, longer pacing, and tighter server-side throttles to prevent 429 errors.
• Added: Resolve All diagnostics in the browser console for fast root-cause analysis.
• Improved: Resolve All batching now self-tunes based on step durations and memory ceilings; logging hardened with safer output buffering.
• Updated: Documentation and admin UI messaging for the throttled workflow and recommended troubleshooting steps.

3.5 – 2025-11-12

• Introduced timezone-aware scheduled scans with daily/twice daily/weekly frequency controls.
• Added progress indicators, scan history, and concurrency protection between manual and scheduled runs.

1.9 – 2025-10-22

• Added “Resolved By” tracking for manual actions plus table wrapping fixes and accountability improvements.