OST Site Inspection

In a dedicated database table ({prefix}ostins_logs). No log file is created on the server, so there is no risk of a log being read directly over HTTP.

Identical entries (same level, message, file and line) are merged into a single record with an occurrence counter. There are also limits on the number of records written per request and on the total number of stored records.

Use the following action: do_action( 'ostins_log', 'manual', 'message', $_POST, $post_id ); Because it is called through do_action(), your theme will not raise an error if this plugin is deactivated or deleted. Add the call in functions.php or another theme file, and enable "Manual log" under "Current recording settings" on the Log tab for it to be recorded.

Masking is enabled by default. In manual logs, values whose key suggests a name, phone number or email address are replaced with ****. In mail logs the key names are not available, so email addresses, phone numbers and postal codes found in the recipient, subject and body are masked instead. Names and street addresses cannot be identified reliably and are therefore kept, so it is recommended to disable mail logging and delete the stored logs before handing a site over. Manual logs and mail logs are both disabled by default. The request URL recorded with an error always has query-string tokens (password reset keys, nonces and similar) masked, regardless of the masking setting.

Lower "Pages per batch" on the Settings tab. The scan is split into batches and can be re-run safely after an interruption.

Add their host names to "Excluded hosts" on the Settings tab, one per line. A host also excludes its subdomains. Developers can change the list with the ostins_domain_excluded_hosts filter.

No. Bulk replacement can corrupt serialized data. This plugin only detects occurrences; use a tool such as WP-CLI's wp search-replace to perform the replacement.