New to Translating WordPress? Read through our Translator Handbook to get started. Hide
| Prio | Original string | Translation | — |
|---|---|---|---|
| ↑ | Developer tools for diagnostics, debugging, maintenance, and site administration. | You have to log in to add a translation. | Details |
Original untranslated
Developer tools for diagnostics, debugging, maintenance, and site administration.
You have to log in to edit this translation. |
|||
| ↑ | SiteIntelix – Developer & Admin Toolkit | You have to log in to add a translation. | Details |
Original untranslated
SiteIntelix – Developer & Admin Toolkit
CommentPlugin name. You have to log in to edit this translation. |
|||
| If <code>WP_CONTENT_URL</code> is customized, replace <code>/wp-content/</code> with that installation's actual content URL path. Keep the rule scoped to the complete SiteIntelix directory, reload Nginx after validating the configuration, and use SiteIntelix's authenticated admin interfaces to access private data. This rule also protects the default Version Vault; placing the vault outside the public web root is stronger. | You have to log in to add a translation. | Details | |
Original untranslated
If <code>WP_CONTENT_URL</code> is customized, replace <code>/wp-content/</code> with that installation's actual content URL path. Keep the rule scoped to the complete SiteIntelix directory, reload Nginx after validating the configuration, and use SiteIntelix's authenticated admin interfaces to access private data. This rule also protects the default Version Vault; placing the vault outside the public web root is stronger.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Yes. SiteIntelix clears WordPress' plugin metadata cache but intentionally does not call a global cache flush or <code>opcache_reset()</code>. Integrations can use <code>siteintelix_before_plugin_version_switch</code>, <code>siteintelix_after_plugin_version_switch</code>, and <code>siteintelix_plugin_version_switch_failed</code> for targeted cache handling or audit integrations. | You have to log in to add a translation. | Details | |
Original untranslated
Yes. SiteIntelix clears WordPress' plugin metadata cache but intentionally does not call a global cache flush or <code>opcache_reset()</code>. Integrations can use <code>siteintelix_before_plugin_version_switch</code>, <code>siteintelix_after_plugin_version_switch</code>, and <code>siteintelix_plugin_version_switch_failed</code> for targeted cache handling or audit integrations.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| No. Version Switcher replaces plugin files only. It cannot reverse database migrations, changed options, custom tables, post metadata, or scheduled events. Use a staging site and create a database backup before comparing versions that may change stored data. | You have to log in to add a translation. | Details | |
Original untranslated
No. Version Switcher replaces plugin files only. It cannot reverse database migrations, changed options, custom tables, post metadata, or scheduled events. Use a staging site and create a database backup before comparing versions that may change stored data.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| By default, randomized ZIP filenames are stored beneath the protected SiteIntelix content directory. Define <code>SITEINTELIX_VERSION_VAULT_DIR</code> with an absolute directory path, or use the <code>siteintelix_version_vault_directory</code> filter, to place licensed builds outside the public web root. The admin interface never publishes package URLs, physical paths, or randomized filenames. | You have to log in to add a translation. | Details | |
Original untranslated
By default, randomized ZIP filenames are stored beneath the protected SiteIntelix content directory. Define <code>SITEINTELIX_VERSION_VAULT_DIR</code> with an absolute directory path, or use the <code>siteintelix_version_vault_directory</code> filter, to place licensed builds outside the public web root. The admin interface never publishes package URLs, physical paths, or randomized filenames.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Can caches react after a successful version switch? | You have to log in to add a translation. | Details | |
Original untranslated
Can caches react after a successful version switch?
CommentFound in faq header. You have to log in to edit this translation. |
|||
| Does switching a plugin version roll back its database changes? | You have to log in to add a translation. | Details | |
Original untranslated
Does switching a plugin version roll back its database changes?
CommentFound in faq header. You have to log in to edit this translation. |
|||
| Where are Plugin Version Switcher builds stored? | You have to log in to add a translation. | Details | |
Original untranslated
Where are Plugin Version Switcher builds stored?
CommentFound in faq header. You have to log in to edit this translation. |
|||
| Plugin Version Switcher requires <code>update_plugins</code>, validates package identity and SHA-256 checksums, rejects traversal and symbolic-link archive entries, keeps recovery copies until verification succeeds, and never exposes vault paths or stored filenames to the browser. | You have to log in to add a translation. | Details | |
Original untranslated
Plugin Version Switcher requires <code>update_plugins</code>, validates package identity and SHA-256 checksums, rejects traversal and symbolic-link archive entries, keeps recovery copies until verification succeeds, and never exposes vault paths or stored filenames to the browser.
CommentFound in description list item. You have to log in to edit this translation. |
|||
| 🔁 <strong>Plugin Version Switcher</strong> — keep private plugin ZIP builds in a protected Version Vault and switch the installed files with WordPress' native upgrader while preserving activation state. | You have to log in to add a translation. | Details | |
Original untranslated
🔁 <strong>Plugin Version Switcher</strong> — keep private plugin ZIP builds in a protected Version Vault and switch the installed files with WordPress' native upgrader while preserving activation state.
CommentFound in description list item. You have to log in to edit this translation. |
|||
| <strong>Modules</strong> — enable or disable installed toolbox modules and open available tools from one screen. | You have to log in to add a translation. | Details | |
Original untranslated
<strong>Modules</strong> — enable or disable installed toolbox modules and open available tools from one screen.
CommentScreenshot description. You have to log in to edit this translation. |
|||
| SiteIntelix removes its settings, scheduled events, logs, and only signature-verified SiteIntelix safety MU bootstrap files. Custom CSS & JS entries, generated assets, Code Snippets, and File Manager-owned backups, trash, metadata, and audit records are removed only when their independent uninstall-retention settings are enabled. Version Vault builds and switching history remain until they are deleted from Version Switcher. Debug constants are not silently rewritten during deletion; the viewer should be used to disable them first. | You have to log in to add a translation. | Details | |
Original untranslated
SiteIntelix removes its settings, scheduled events, logs, and only signature-verified SiteIntelix safety MU bootstrap files. Custom CSS & JS entries, generated assets, Code Snippets, and File Manager-owned backups, trash, metadata, and audit records are removed only when their independent uninstall-retention settings are enabled. Version Vault builds and switching history remain until they are deleted from Version Switcher. Debug constants are not silently rewritten during deletion; the viewer should be used to disable them first.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Yes, only when an authorized administrator starts debugging or changes a Debug Log setting. SiteIntelix uses WPConfigTransformer, validates an allowlist of debug constants, and writes a restricted adjacent backup first. If <code>wp-config.php</code> is read-only, the log viewer remains available while configuration changes report the write failure. | You have to log in to add a translation. | Details | |
Original untranslated
Yes, only when an authorized administrator starts debugging or changes a Debug Log setting. SiteIntelix uses WPConfigTransformer, validates an allowlist of debug constants, and writes a restricted adjacent backup first. If <code>wp-config.php</code> is read-only, the log viewer remains available while configuration changes report the write failure.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| WordPress writes to a randomized file in the protected SiteIntelix content directory. The viewer shows only its WordPress-relative path, not the complete server path. | You have to log in to add a translation. | Details | |
Original untranslated
WordPress writes to a randomized file in the protected SiteIntelix content directory. The viewer shows only its WordPress-relative path, not the complete server path.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
Export as
Comment
Short description.