Prohibited Terms Scanner

=== Prohibited Terms Scanner === Contributors: apos37 Tags: content moderation, search, compliance, media library, scanner Requires at least: 6.0 Tested up to: 7.0 Requires PHP: 7.4 Stable tag: 1.2.1 License: GPLv2 or later License URI: http://www.gnu.org/licenses/gpl-2.0.txt

Scan your site's posts, pages, comments, taxonomy terms, and media for prohibited terms or phrases so you can find and fix them before they go public.

== Description ==

Prohibited Terms Scanner searches your site for a list of terms or phrases you define, so you can identify content that shouldn't be public facing before it causes a problem.

Paste a list of terms or phrases, choose where to search, and run a scan. Results show you the term found, surrounding context, where it was found, and a direct link to it. Flagged results can be reviewed, marked as OK to ignore going forward, or cleared once resolved.

Features:

• Search post titles, main content, excerpts, comments, taxonomy term names and slugs, media filenames, and media alt text
• Optional file content scanning for plain text, CSV, Word (.docx), and PDF files (opt-in, off by default)
• ERI File Library integration (filenames, titles, descriptions, and file content)
• Case-sensitive and whole-word (strict) matching, set globally or per term
• Batched AJAX scanning with an animated progress bar and running item count, so large sites don't time out
• Cancel a scan in progress; results found so far are kept
• Results table with highlighted context snippets, post type/file type labels, source titles, direct links, and a highlight-and-blink indicator on the linked page
• Mark individual results as OK to exclude them from future scans, or clear them once resolved, including a Clear All option
• Omit specific posts, pages, media, or files from all future scans — directly from the Results page or via a quick action link (with bulk action support) on your admin list tables, viewable and manageable from a dedicated Omitted Sources page
• Front-end shortcode for staff to run scans without accessing wp-admin, restricted to roles you choose, including its own results table
• Optional warning when saving a post/page, uploading a file, or editing alt text that contains a monitored term (warns, does not block)
• Optional scheduled (daily/weekly/monthly) automatic scanning using your saved terms and search locations, with a status readout showing next/last run
• A count badge on the admin menu showing how many unresolved results need attention
• Import/export your term list and settings as JSON to move between sites
• Batch size and context snippet length are both configurable for performance tuning
• An Errors log for troubleshooting scan issues without digging through server logs
• Extendable: developers can register additional scan locations for their own integrations

This plugin does not automatically remove or redact anything it finds. It is a discovery tool to help you locate and manually review content that may need attention.

== Installation ==

1. Upload the plugin files to the /wp-content/plugins/prohibited-terms-scanner/ directory, or install through the Plugins screen directly.
2. Activate the plugin through the 'Plugins' menu in WordPress.
3. Go to Prohibited Terms Scanner in the admin menu to add your terms and run your first scan.
4. Optionally visit Prohibited Terms Scanner > Settings to adjust search locations, post types, batch size, and the save/upload warning.

== Frequently Asked Questions ==

= Does this plugin automatically remove or fix flagged content? = No. It only finds and reports flagged terms so you can review and fix them yourself. Nothing is edited or redacted automatically.

= Will scanning slow down my site? = Scans run in batches over AJAX and only while you're actively on the Scanner page, not in the background or on every page load. You can adjust the batch size in Settings if scans are timing out or running too slowly on a large site.

= What file types are supported for file content scanning? = File content scanning (optional, off by default) currently supports:

• Plain text files (.txt)
• CSV files (.csv)
• Word documents (.docx)
• PDF files (.pdf)

Legacy Word documents (.doc, the pre-2007 binary format) are not supported out of the box, since reliably reading that format requires a separate third-party library this plugin doesn't bundle. Developers can add support for .doc or any other file type using the ptscanner_file_content_mimes filter along with their own extraction logic.

= What happens if I run a full scan again? = A full scan clears previously flagged (unresolved) results before running, so your results always reflect the current state of your site. Results you've marked as OK are kept and are not re-flagged unless the same term is found in a new location.

= Can non-admin users run scans? = Yes, using the [prohibited_terms_scanner] shortcode on any page. Access is restricted to the roles you choose in Settings; there is no public/logged-out option.

= Can I omit specific content from being scanned? = Yes. You can omit individual posts, pages, media, or files from all future scans, either from the Results page (which also clears any existing flagged results for that source) or via a quick "Omit from Terms Scanner" action link on your Posts, Pages, and Media list tables, with bulk action support. Omitted sources are managed from their own Omitted Sources page.

= Can scans run automatically on a schedule? = Yes. In Settings, you can enable daily, weekly, or monthly scheduled scanning using your saved term list and search locations — no need to visit the Scanner page. This runs as a single background process via WordPress's cron system, so very large sites may want to increase their PHP execution time limit for cron requests, or test this on a staging site first. The Settings page shows the next scheduled run and the result of the last run.

= Does the save/upload warning stop me from saving or uploading? = No. It warns you that a monitored term was found so you can double check before continuing, but it will not block you from proceeding.

== Screenshots ==

1. Add terms and choose search locations on the Scanner page
2. Live progress bar while a scan runs
3. Results table with context, links, and resolution actions
4. Settings page with search locations, post types, and performance options

== Changelog ==

= 1.2.2 = // TODO:

• Tweak: Changed results time to AM/PM instead of military time
• Update: Added excluded post types filters

= 1.2.1 =

• Fix: Missing Location column in the Results page table that caused Source, Date, and Actions to misalign
• Fix: Shortcode output leaking into AJAX scan responses on certain sites, corrupting batch results
• Fix: Batch failures during a scan skipping the rest of that location type instead of continuing
• Tweak: Improved scan error messages to be more descriptive and human-readable, including which shortcode tag was involved when applicable
• Fix: HTML entities (e.g. "&") displaying incorrectly in source titles on the front-end results table
• Fix: Various Plugin Check compliance fixes (input sanitization, output escaping, direct database call annotations, global variable prefixing)

= 1.2.0 =

• Update: Added an Omitted Sources system: omit posts, pages, media, or files from all future scans, via the Results page or list table quick/bulk actions
• Tweak: Added source titles to the results table
• Update: Added a Clear All action for results and for term lists
• Tweak: Added collapsible term list accordions that auto-collapse when terms already exist
• Fix: Various bug fixes from real-world testing

= 1.1.0 =

• Update: Added file content scanning for PDF and Word (.docx) documents
• Update: Added ERI File Library integration (titles, filenames, descriptions, and file content)
• Update: Added a results counter badge on the admin menu
• Update: Added optional scheduled (cron) scanning with status display

= 1.0.0 =

• Initial release