Changelog — JPKCom Harden & Trim
Versionsverlauf des WordPress-Plugins JPKCom Harden & Trim.
Versionsverlauf von jpkcom-harden-trim (öffnet in neuem Tab). Die Einträge stammen unverändert aus der README des Projekts. Eine ausführliche Anleitung mit Tipps findest du im Projekt-Guide.
1.1.1
- Changed: the German translations call the defaults "Standardwerte"; "Voreinstellungen" now only means the presets, so the settings page no longer uses one word for both
1.1.0
- Changed: XML-RPC is blocked on every site right after this update, because the new "Disable XML-RPC" switch is on by default and the stored settings of an earlier version do not contain it. Jetpack, the WordPress mobile apps and incoming pingbacks stop working until you untick the switch in Settings → Harden & Trim or set
define( 'JPKCOM_HARDEN_TRIM_XMLRPC', false );inwp-config.php. Every preset keeps it on, so applying a preset also switches it on again - Added: "Disable XML-RPC" switch, mirroring JPKCom Disable XML-RPC 1.0.10:
xmlrpc.phpanswers 403 with an XML-RPC fault, the endpoint is no longer advertised, trackbacks are refused - Added: "Disable comments" switch (off by default, never part of a preset), mirroring JPKCom Disable Comments 1.0.11: comments and pings closed on every post type, existing comments hidden, every post reports zero comments (no comment links or counts in
/feed/and the Atom feed, no "N comments" in themes), comment screens and feeds removed. The REST comment routes answer every request that is not a block editor Notes request with therest_no_route404 a missing route gives (OPTIONStoo, which a missing route answers with an empty 200); a note's route whoseidparameter names a different comment is not a Notes request. Notes keep working, and WordPress' own permission checks decide who may read or write them. Because the routes stay registered for Notes, the REST index at/wp-json/lists them. The query-string comment feeds (?feed=comments-rss2,?p=123&feed=rss2) answer 404 directly instead of redirecting to a pretty URL that would 404 as well; this is deliberate - Added: a hint on the settings page while the matching standalone plugin is active
- Added: German translations of the new texts (
de_DE,de_DE_formal)
1.0.1
- Changed: the updater keeps its manifest cache, its failure marker and its fetch lock in site transients. On multisite the network now fetches the manifest once instead of once per site; on a single site nothing changes
- Changed: uninstalling also removes the updater's network-wide cache entries, and still the per-site ones 1.0.0 wrote
1.0.0
- Added: Initial release.
- Added: performance switches (emoji, self pingbacks, asset versions, post embeds, comment reply, dashicons, block library CSS, global styles, heartbeat, revisions, autosave interval)
- Added:
<head>cleanup, privacy and security switches with harmless defaults - Added: role exemption (off by default), presets, JSON import/export,
wp-config.phpconstants and a kill switch - Added: German translations (
de_DE,de_DE_formal)