Advanced Settings
Advanced Settings covers less common configuration options that you may only need once or when troubleshooting a specific problem. Each setting is explained below so you know exactly when and why to use it.
Scan Roles
Section titled “Scan Roles”What it does: Controls which types of site visitors Omnalingo impersonates when scanning your pages for translatable content.
When Omnalingo scans a page, it fetches the page the same way a visitor would — but it can do this as different user types to capture content that’s only visible to certain roles. Each scan role triggers a separate pass over your content.
Default: Visitor and Administrator
Available roles:
- Visitor — scans the page as a logged-out user (what most of your visitors see)
- Administrator, Editor, and any other WordPress roles on your site — scans the page as that role, revealing any content that’s hidden from regular visitors
When to change it:
- If you have a membership site with content gated behind subscriber or member roles, add those roles so Omnalingo can discover and translate that content.
- If your site has WooCommerce shop manager content only visible to staff, add the shop manager role.
- If scan times are slow and you don’t have role-specific content, you can remove Administrator from the list and scan as Visitor only.
Orphaned Plugin Data (Flagged Domains)
Section titled “Orphaned Plugin Data (Flagged Domains)”What it does: When you deactivate or uninstall another plugin, some of the strings Omnalingo collected from that plugin become orphaned — the plugin is gone, but its text is still sitting in your translation database. Omnalingo detects this automatically and shows a notice for each affected plugin.
You have two options for each flagged plugin:
| Action | What happens |
|---|---|
| Clean up | Permanently deletes all strings and translations from that plugin. Use this when you’ve removed the plugin for good. |
| Dismiss | Removes the notice but keeps the data. Use this if the plugin is only temporarily deactivated (for example, while debugging). |
Database Maintenance
Section titled “Database Maintenance”Over time, Omnalingo’s internal database can accumulate orphaned records — entries that point to content that no longer exists. This doesn’t affect translation quality, but it can cause your database to grow larger than necessary.
Check for Orphaned Records
Section titled “Check for Orphaned Records”Click Check for Orphaned Records to see how many there are. This is a read-only check and makes no changes.
Clean Up Orphaned Records
Section titled “Clean Up Orphaned Records”Click Run Cleanup to remove the orphaned records. This only removes structural orphans — broken links in the database — not your actual translations or string content. Your translations are untouched.
Schedule Automatic Cleanup
Section titled “Schedule Automatic Cleanup”You can enable automatic cleanup to run once every 30 days. This keeps your database tidy without any manual action. Enable it from the database maintenance section and it runs in the background.
Factory Reset
Section titled “Factory Reset”What it does: Resets Omnalingo completely — all settings, all translations, all scanned content, and all database tables are wiped. The plugin then behaves as if freshly installed.
What is preserved after a reset:
- Your API key (you won’t need to re-enter it)
- The Omnalingo settings entry (reset to defaults, not deleted)
What is destroyed:
- All translations and scanned strings
- All language configuration
- All glossary rules and AI context settings
- All scan history and processing data
When to use it: Only use factory reset as a last resort — for example, if you’re starting a completely new translation project and want a clean slate, or if support has asked you to reset as part of a troubleshooting step.
After a reset, Omnalingo immediately starts re-discovering your content. You’ll need to reconfigure your languages, AI context, glossary, and any other settings before scanning and translating again.