# Changelog — JPKCom Disable Comments

> Versionsverlauf des WordPress-Plugins JPKCom Disable Comments.

Source: https://www.jpkc.com/db/changelog/jpkcom-disable-comments/

Versionsverlauf von [`jpkcom-disable-comments`](https://github.com/JPKCom/jpkcom-disable-comments). Die Einträge stammen unverändert aus der README des Projekts. Eine ausführliche Anleitung mit Tipps findest du im [Projekt-Guide](https://www.jpkc.com/db/guides/jpkcom-disable-comments/).

## 1.0.9
* Fixed: existing comments were still publicly readable through the comment feeds. `/comments/feed/` and `<post>/feed/` are built by `WP_Query` directly via `$wpdb` and bypass the `comments_array` filter this plugin relied on, so approved comments stayed retrievable after comments had been switched off. Both now return 404 and the feed discovery links are gone; the regular post feed at `/feed/` is unaffected
* Fixed: the dashboard kept showing comments. `remove_meta_box( 'dashboard_recent_comments', … )` had no effect for two reasons — no widget of that name has existed since WordPress 3.8 (recent comments live inside the Activity widget), and `admin_init` runs before `wp_dashboard_setup()` anyway. "At a Glance" therefore still linked a comment count to the redirected comments screen, and the Activity widget still rendered the full moderation list. Replaced by zeroing `wp_count_comments()` and short-circuiting `comments_pre_query`
* Fixed: comment and trackback support is now removed on `wp_loaded` instead of `admin_init`, so it applies to REST and front-end requests too, not just wp-admin. The two supports are also checked independently — a post type declaring `trackbacks` without `comments` previously kept them
* Fixed: REST responses reported the stored `comment_status`, typically `open`, on a site that refuses comments. Removing post type support cannot change this for `post`, `page` and `attachment`: `WP_REST_Posts_Controller::get_item_schema()` carries a hardcoded `$fixed_schemas` list in which `comments` is always present. `comment_status` and `ping_status` are now reported as `closed`. The stored value is left alone, and the fields keep their place in the response so the block editor sees the shape it expects
* Changed: `comments_open`, `pings_open` and `comments_array` are filtered at `PHP_INT_MAX` instead of priority 20/10, so a theme or plugin hooking in later cannot re-open them
* Added: `tests/test-hooks.php` covers the hook surface and the new callbacks; CI runs it on every pull request and push to `main`

## 1.0.8
* Fixed: the update manifest no longer reports `network: true` for this plugin. The generator defaulted a missing `Network:` header to true, while WordPress' own default for a missing header is "not network-only". Metadata only — WordPress derives network-only from the plugin header via `is_network_only_plugin()`, not from the update manifest
* CI: the lint and guard workflow now also runs on pushes to `main`. It only covered pull requests, so a direct push with bypass rights skipped every check
* Changed: comments, workflow step names and CI output across the repository are now English throughout, and the developer notes in `CLAUDE.md` were translated and trimmed. No effect on the shipped plugin

## 1.0.7
* Changed: `Tested up to` raised to WordPress 7.1
* Changed: the bundled updater's runtime floor now matches the plugin's own minimum. It bailed out below WordPress 6.8 while the plugin header has required 6.9 for several releases, so the check could never fire on a supported installation
* CI: the release manifest's fallback values for `requires` and `tested` now say 6.9 and 7.1. They only apply when the README metadata cannot be read, but a stale fallback would have published a minimum the plugin no longer supports

## 1.0.6
* Added: plugin banners (`assets/banner-1544x500.avif`, `assets/banner-772x250.avif`) — a plain `#3c4955` surface with no lettering. The update manifest already advertised these two URLs, but nothing was published under them, so the plugin card in wp-admin had a broken banner

## 1.0.5
* CI: the release step no longer copies the staging directory into itself, so the ZIP has no empty `jpkcom-disable-comments/jpkcom-disable-comments/` folder
* CI: bumped the pinned GitHub Actions (checkout v7.0.1, setup-python v7.0.0, action-gh-release v3.0.2, fetch-metadata v3.1.0), still pinned to full commit SHAs
* CI: the release ZIP now excludes the development-only `tests/` and `tools/` directories
* CI: security and regression tests now run on every pull request, where a plugin has them

## 1.0.4
* Security: update packages are now verified *before* installation — the verified file is handed to WordPress instead of being downloaded a second time, so the bytes that were checked are the bytes that get installed
* Security: a missing or unfetchable SHA-256 checksum now aborts the update instead of installing unverified code (previously it silently skipped verification)
* Security: pinned every GitHub Action to a full commit SHA and added Dependabot with a 7-day cooldown, so a moved tag can no longer change the release build
* Security: tightened which download the updater claims, so sibling plugins cannot match each other's package
* Fixed: `sprintf()` calls in the updater bound named arguments to a variadic parameter, which raises `ArgumentCountError` on PHP 8.3
* Fixed: the "View Details" modal could fail with a `TypeError` when the manifest omitted `requires_plugins`
* Performance: a failed manifest fetch is now cached for an hour instead of being retried on every admin request
* Added: CI workflow on every pull request (PHP lint, named-argument check, YAML validation, action-pinning guard)

## 1.0.3
* Docs: linked the published PHPDoc API documentation

## 1.0.2
* Added secure self-hosted plugin updates via GitHub with SHA256 checksum verification
* Added an automated release workflow (builds the ZIP, generates the manifest and deploys to gh-pages on tag push)
* Raised the minimum WordPress version to 6.9 and "Tested up to" to WordPress 7.0
* Switched license metadata to the SPDX identifier `GPL-2.0-or-later` with the HTTPS license URI
* Added PHPDoc-generated API documentation, built and deployed to gh-pages on release
* Hardening: enabled `declare(strict_types=1)` and tidied the REST endpoint loop

## 1.0.1
* Removed REST API endpoint for comments

## 1.0.0
* Initial Release