| 开发者 | shaounchandrashill |
|---|---|
| 更新时间 | 2026年9月20日 01:26 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
<head> tags, throttles the Heartbeat API, caps stored post revisions, disables self-pingbacks, and eases wp-admin memory/time limits for heavy builders — all reversible with one toggle./wp-content/plugins/reloadify-frontend-sync, or install through the WordPress plugins screen.Check Reloadify Sync → Cross-Browser Reload: confirm Developer Mode is on and that browser/mode is toggled on. Everything is on by default, but if you turned things off before, check there first.
No — it's a best-effort heuristic. Several browsers deliberately make private mode indistinguishable from normal mode. When it can't tell, the plugin defaults to running the reloader anyway rather than staying silent.
memory_limit, max_execution_time, and three of the six opcache.* directives (enable, validate_timestamps, revalidate_freq) genuinely can be applied live by any WordPress plugin — that's just how PHP classifies them. The other three opcache directives (memory_consumption, interned_strings_buffer, max_accelerated_files) size shared memory once at PHP startup and truly can't be touched without editing php.ini and restarting PHP — same for post_max_size, upload_max_filesize, and realpath cache. For those, the panel writes a best-effort .user.ini/.htaccess (works on many hosts) or generates a copy-paste snippet, instead of pretending to apply them for you.
No — turn it on only while you're actively testing, then switch it back off yourself. It's off by default for exactly this reason: while it's on, every visitor's browser polls the server, which is fine for staging but adds real load with real traffic. Unlike earlier versions, Developer Mode no longer disables itself automatically — it stays exactly as you set it until you change it, so remembering to switch it off is now on you.
The frontend check is a small static file the webserver answers directly — no PHP or WordPress involved — so it's cheap per check. The main thing that adds load is leaving Developer Mode on for a long time on a busy live site, since every visitor's browser then polls continuously; keep it switched on only while you're actually testing.
No. For images, the original file you uploaded is never modified — only the generated thumbnail/medium/large sizes get WebP or AVIF versions alongside them, and only if your server's image library actually supports that format (checked with WordPress's own detection, never assumed). Video compression only runs if the server has ffmpeg available; if it doesn't, video is left completely untouched rather than pretending to optimize it. The whole feature is one toggle — turn it off any time to leave media exactly as WordPress would handle it by default.
.pot file..htaccess validation, permissions, error handling, and backups.blueprint.json support for WordPress Playground Live Preview.