-
Notifications
You must be signed in to change notification settings - Fork 0
FAQ
No. Never. Any account with a w4os_uuid value is completely invisible
to this plugin at all times. Established residents with avatars cannot
be selected, flagged, emailed, or deleted by Royal Flush under any
circumstances.
No. Any user with the edit_posts capability (Administrators, Editors)
is permanently exempt from all plugin activity.
No. Your own user ID is hardcoded as protected at deletion time. Even if you somehow selected yourself in the queue, the server-side check would skip you.
Absolutely not. Nothing is ever auto-deleted. Every deletion requires you to manually select accounts, click the flush button, and confirm twice. You are always in full control.
No. Each email is sent exactly once per account, ever. The sent timestamp is stored in user meta the moment it is sent and the scan never sends that email again.
No. This is expected behavior on first activation. If an account is already 60+ days old when the plugin is first activated, both emails fire in the first scan pass since neither has been sent before. This only happens once — after that, each email fires at its proper threshold going forward.
Not in v1.0.0. Configurable email templates are planned for a future release. The emails currently use your WordPress site name dynamically and reference your avatar creation URL automatically.
The plugin records the send attempt regardless of delivery. If an email bounces, the account will still be flagged at Day 60 and appear in your review queue as normal.
Simply don't check the box next to it when you flush. The queue is for review — you decide who gets flushed. Legitimate accounts can sit in the queue indefinitely without harm.
Not via the UI in v1.0.0. If you want to manually clear the queue
flag for a specific user, go to Users → Edit User for that account
and delete the orf_queued user meta value. The account will no longer
show as Queued but will re-enter the queue on the next scan if it is
still past 60 days.
As often as you like. The queue builds up over time — weekly or monthly review sessions work well for most grids. The daily cron handles emails and flagging automatically in the background.
Add gmail.com to your trusted domains list under
Users → Royal Flush Settings. Gmail is pre-populated in the
default trusted domains list — if it is showing as a bot farm domain,
it may have been accidentally removed. Click Reset to Defaults
to restore the full default list.
Click the "Add to trusted domains →" link in the bot farm warning bar and add the domain to your trusted list. It will never be flagged again.
Any email domain that is not on your trusted list AND has more than one no-avatar account registered under it. The threshold is simply more than one account — even two accounts from the same obscure domain will trigger the warning.
Yes. The plugin only requires w4os to be installed and configured.
WooCommerce is not required. The Last Seen column uses wc_last_active
user meta if WooCommerce is present, but will simply show — if it is not.
Not officially tested in v1.0.0. Multisite support is planned for a future release.
The WP-Cron schedule is cleanly removed on deactivation. User meta flags remain in the database but are completely harmless. Reactivating the plugin will pick up exactly where it left off.
Plugin files are removed. User meta flags (orf_email_d30,
orf_email_d59, orf_queued) remain in the database. If you want
a completely clean removal, delete these meta keys manually via
phpMyAdmin or a user meta cleanup plugin.
The Disabled feature requires the
Disable User Login
plugin to be installed and active. Royal Flush detects disabled accounts
via the _is_disabled user meta key that this plugin writes. Without it,
no accounts will have that meta key and the Select Disabled button will
have nothing to select.
← How It Works | Changelog →