Product Twenty Site Defaults

开发者	producttwenty
更新时间	2026年9月4日 01:37
PHP版本:	7.4 及以上
WordPress版本:	7.1
版权:	GPLv2 or later
版权网址:	版权信息

下载

1.0.0

详情介绍:

Site Defaults makes a repeated fresh-site setup visible and deliberate:

Choose an Agency, Business, Blog, or Development preset.
Preview every proposed value beside the site's current value.
Apply the preset explicitly.
Review future configuration drift and restore or accept each change.
Customize cleanup and access policies without adding a second utility plugin.

The plugin does not add ads, telemetry, remote requests, or dashboard spam. It does not remove content or other plugins. After a preset is applied, Site Defaults monitors its WordPress options. The plugin reports differences on its settings screen and in Site Health. When a setting needs review, a contextual Site Defaults notice appears throughout WordPress admin with a direct link to the configuration report. It is omitted from the Site Defaults page, where the full report is already visible. Administrators remain in control: changes are never automatically reverted. Cleanup policies can disable emoji assets, WordPress post embeds, XML-RPC, comments, author archives, attachment pages, public REST API user enumeration, and Application Passwords. They can also remove generator, shortlink, RSD, and WLW metadata and low-value dashboard widgets. Integration-sensitive controls include clear cautions. The audited Agency, Business, and Blog presets disable XML-RPC while keeping Application Passwords available for modern REST API integrations and automation. Development leaves cleanup and access behavior at WordPress defaults. User enumeration controls Agency and Business reduce two common public user-enumeration paths: anonymous WordPress REST API user listing and public author archives, including the users sitemap. Blog protects the REST API user listing while retaining author archives for publishing. Development leaves both behaviors at WordPress defaults. These controls reduce common public user-enumeration paths; they do not guarantee that usernames or author identities cannot be discovered through published content, themes, plugins, feeds, caches, or other integrations. The unified preset table shows every WordPress setting and cleanup behavior in one place. Choose a built-in preset, then use Customize this preset to make its Preset behavior column editable. Unchanged values remain inherited from the selected preset. Applying the edited configuration saves it as Custom, records which preset it came from, and establishes the complete Custom configuration as the monitoring baseline.

安装:

Install Product Twenty Site Defaults from Plugins > Add New in WordPress, or upload the plugin ZIP.
Activate Product Twenty Site Defaults.
Open Settings > Site Defaults.
Choose a preset and review its proposed changes before applying it.

屏幕截图:

常见问题:

Does uninstalling restore the old WordPress settings?

No. Applying a preset is an explicit edit to WordPress settings. Uninstall removes only the plugin's own record of the last application and leaves the site's current configuration intact.

Does drift monitoring automatically undo changes?

No. The plugin reports differences and lets an administrator restore the baseline, accept the new value, or stop monitoring that setting.

Does the plugin delete sample content or other plugins?

No. The plugin changes only the WordPress options and cleanup policies shown in its preview. It does not delete posts, comments, media, users, themes, or plugins.

What does blocking WordPress post embeds mean?

It prevents other sites from embedding this site's posts. It does not disable YouTube, Vimeo, or other external media embeds in the WordPress editor.

Why do the main site presets disable XML-RPC but keep Application Passwords available?

Agency, Business, and Blog block the older XML-RPC interface and remove its pingback response header. Application Passwords remain available so modern REST API integrations and automation continue to work. Sites using Jetpack, legacy publishing tools, or another XML-RPC integration can customize the selected preset and make XML-RPC available before applying it. Development leaves XML-RPC available.

Does Site Defaults prevent user enumeration?

Site Defaults reduces common public user-enumeration paths without claiming to prevent every possible form of username discovery. Agency and Business require sign-in for REST API user listing, return not found for author archives, and remove the users sitemap. Blog requires sign-in for REST API user listing but keeps author archives available. Development leaves these features at WordPress defaults. Authorized signed-in users and normal editor functionality remain available. Public author information may still appear in posts, themes, plugins, feeds, caches, or external integrations.

Does it work with multisite?

The plugin can be activated on an individual site. Network-wide behavior has not yet been declared or tested.

更新日志: