| 开发者 |
rtomo
rotistudio |
|---|---|
| 更新时间 | 2026年7月27日 21:17 |
| 捐献地址: | 去捐款 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
?ver= from front-end CSS/JS (can break cache busting; prefer CDN purge or hashed filenames).DISALLOW_FILE_EDIT so theme/plugin editors stay off.AUTOMATIC_UPDATER_DISABLED and WP_AUTO_UPDATE_CORE when defined.manage_options always keep access. Front-end admin-ajax.php is intentionally not blocked.manage_options.REMOTE_ADDR only). Optional IP whitelist (one address per line). Covers wp-login.php and other wp_signon() paths (including WooCommerce).wp_is_mobile(); sends Vary: User-Agent (full-page caches must honour it).rel attributes.[refi-year] and [refi-year from="2006"].
More plugins: rotistudio.com
Author site: rottenbacher.hu
GitHub: github.com/rotisoft/refitune/wp-content/plugins/refitune (or install from WordPress.org).No. Most modules remove unused front-end work or add checks only on login/upload. Features are opt-in.
Only if your theme and plugins work with current jQuery. Test first; leave it off when unsure.
The WordPress mobile app, Jetpack sync, and other remote clients that need XML-RPC may stop working.
It uses REMOTE_ADDR only (not spoofable X-Forwarded-For). Failed attempts are counted per IP and per IP+username pair. Add static office or trusted egress IPs to the whitelist (one per line). Behind a CDN or shared NAT, many visitors share one address - whitelist only IPs you control.
Yes. Email logins are canonicalized to usernames where possible, and lockouts are checked on authenticate so wp_signon() paths (including WooCommerce) are covered.
Yes. Restrict Admin Access limits the wp-admin UI by role. Anyone with manage_options always retains access. AJAX is not blocked so front-end admin-ajax.php callbacks keep working; each handler must still check capabilities.
Short downtime windows. Guests get a 503 page; selected roles still browse. Admin, AJAX, and cron remain available so developers can test plugins that need those endpoints.
Yes. AUTOMATIC_UPDATER_DISABLED and WP_AUTO_UPDATE_CORE override RefiTune background update settings when defined. Update check frequency still follows RefiTune cron scheduling.
It forces automatic updates for every plugin or theme and overrides per-item toggles on the Updates screen. "Disable all" blocks them; "WordPress default" leaves native behaviour unchanged.
No. While WP_ENVIRONMENT_TYPE is production, RefiTune will not run without encryption/certificate verification, and the test-mode checkbox cannot be enabled. Set the environment type correctly on live sites.
REMOTE_ADDR only; IP whitelist (one per line)manage_options; documents intentional AJAX skip for front-end callbacksVary: User-Agent; asset ?ver= removal warnings clarified.po updated.pot / .po)