| 开发者 | parag44 |
|---|---|
| 更新时间 | 2026年8月15日 17:27 |
| 捐献地址: | 去捐款 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
WPConfigTransformer library to update WordPress debug constants in wp-config.php.wp-config.php.siteintelix.bak backup is created before changes..log filename in protected wp-content/siteintelix/ storage instead of the default wp-content/debug.log.manage_options capability. On Multisite, executable-code and network-sensitive tools require a Multisite super administrator.update_plugins, 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.[siteintelix_panel] on any page or post to display a compact system information table. The shortcode output is visible only to logged-in administrators.
Users need the manage_options capability to access SiteIntelix. On Multisite, Code Snippets, Custom CSS & JS, Debug Log configuration, Database Manager, Download Manager, Plugin Version Switcher, and Safe Mode require a Multisite super administrator. Code modules also require WordPress' unfiltered_html capability.
Yes. Enabled administrator-authored PHP runs locally in an isolated closure. Snippets are syntax-checked before saving or activation, controls require capabilities and nonces, and a captured runtime failure deactivates the affected snippet. The executor intentionally uses PHP eval() for this local feature and never downloads remote code.
Entries are stored in a plugin-owned database table. When external-file loading is selected, generated files use the restricted wp-content/uploads/siteintelix/custom-code/ directory. SiteIntelix only deletes files that match its managed filename pattern.
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.
No. SiteIntelix uses its own randomized private log file so WordPress' default debug.log is not used by this plugin.
By default, randomized ZIP filenames are stored beneath the protected SiteIntelix content directory. Define SITEINTELIX_VERSION_VAULT_DIR with an absolute directory path, or use the siteintelix_version_vault_directory filter, to place licensed builds outside the public web root. The admin interface never publishes package URLs, physical paths, or randomized filenames.
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.
Yes. SiteIntelix clears WordPress' plugin metadata cache but intentionally does not call a global cache flush or opcache_reset(). Integrations can use siteintelix_before_plugin_version_switch, siteintelix_after_plugin_version_switch, and siteintelix_plugin_version_switch_failed for targeted cache handling or audit integrations.
Nginx does not read .htaccess. Administrators using the default WordPress content URL should add this rule inside the relevant server block:
location ^~ /wp-content/siteintelix/ {
deny all;
return 403;
}
If WP_CONTENT_URL is customized, replace /wp-content/ 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.
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 wp-config.php is read-only, the log viewer remains available while configuration changes report the write failure.
Yes. Search and server-side filters are applied to the parsed log dataset before pagination.
SiteIntelix does not collect telemetry or upload diagnostics, logs, email contents, database contents, or generated reports. When an administrator refreshes Server Diagnostics, reachability checks may contact WordPress.org endpoints and the site's own loopback or REST URL. Those checks send normal HTTP request metadata, not SiteIntelix report contents.
Add [siteintelix_panel] to a page or post. Only administrators can see the output.
Yes. Site-scoped tools can be activated per site. Tools that can execute code, inspect network-wide database data, read installed source packages, write safety MU files, or change debug configuration require a Multisite super administrator.
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.
No. File Manager is Safe Mode-only in this release. PHP files remain view-only, while WordPress core, wp-config.php writes, SiteIntelix, must-use plugins, active plugins, and the active theme are protected. WordPress' DISALLOW_FILE_EDIT and DISALLOW_FILE_MODS constants are also enforced.