Make WordPress Core

Opened 7 weeks ago

Closed 5 weeks ago

#64366 closed defect (bug) (fixed)

Docs: Replace @since x.y.z with actual version number

Reported by: oztaser's profile oztaser Owned by: westonruter's profile westonruter
Milestone: 6.9.1 Priority: normal
Severity: minor Version: 6.9
Component: Role/Capability Keywords: good-first-bug has-patch fixed-major dev-reviewed
Focuses: docs, coding-standards Cc:

Description (last modified by westonruter)

The x.y.z version number was not replaced with the actual WordPress version in which this feature was introduced.

Introduced in r60364 to fix #43421

<?php
@since x.y.z Support was added for a numerically indexed array of strings for the capabilities array.

Attachments (1)

64366.patch (1.3 KB) - added by solankisoftware 7 weeks ago.
Fix :: Docs: Replace @since x.y.z with actual version number

Download all attachments as: .zip

Change History (15)

#1 @oztaser
7 weeks ago

  • Keywords good-first-bug added

#2 @desrosj
7 weeks ago

  • Milestone changed from Awaiting Review to 6.9.1
  • Type changed from enhancement to defect (bug)

#3 @sabernhardt
7 weeks ago

  • Description modified (diff)
  • Version set to 6.9

@solankisoftware
7 weeks ago

Fix :: Docs: Replace @since x.y.z with actual version number

#4 @solankisoftware
7 weeks ago

  • Keywords has-patch added; needs-patch removed

Title:
Docs: Replace placeholder @since x.y.z with actual version numbers

Description:
Updated documentation comments by replacing all placeholder @since x.y.z tags with the correct released version numbers. This ensures consistency across the docs and improves clarity for users referencing version-specific features.

This ticket was mentioned in PR #10605 on WordPress/wordpress-develop by @solankisoftware.


7 weeks ago
#5

This PR replaces placeholder @since x.y.z tags with the accurate version number 6.9.0 in:

  • wp-includes/class-wp-roles.php
  • wp-includes/capabilities.php

These updates follow WordPress documentation standards and align with Core ticket #64366.

Trac ticket: https://core.trac.wordpress.org/ticket/64366

Fixes #64366.

#6 @westonruter
7 weeks ago

  • Description modified (diff)

#7 @westonruter
7 weeks ago

  • Owner set to westonruter
  • Status changed from new to reviewing

#8 @westonruter
7 weeks ago

  • Resolution set to fixed
  • Status changed from reviewing to closed

In 61354:

Docs: Update @since x.y.z with actual version number.

Follow-up to [60364].

Props solankisoftware, oztaser.
See #43421.
Fixes #64366.

#9 @westonruter
7 weeks ago

  • Keywords fixed-major added
  • Resolution fixed deleted
  • Status changed from closed to reopened

Re-opening for 6.9.1 backport.

#10 @jorbin
7 weeks ago

  • Keywords dev-reviewed added

[61354] looks good to backport to the 6.9 branch

This ticket was mentioned in PR #10606 on WordPress/wordpress-develop by @solankisoftware.


7 weeks ago
#11

Trac Ticket: https://core.trac.wordpress.org/ticket/64366

This PR enhances the WordPress Site Health page cache test by introducing
a robust cache header detection mechanism. The previous method could
produce false positives or negatives depending on the caching system used.

Changes include:

  • Added detect_cache_headers() method for strict, case-insensitive header matching
  • Improved support for common cache headers (x-cache, x-cache-status, cf-cache-status, x-litespeed-cache, x-varnish, etc.)
  • Updated get_test_page_cache() to use detect_cache_headers()
  • Prevents false positives when unrelated text contains words like "HIT" or "MISS"

Testing:

  1. Enable any caching layer (Varnish, NGINX fastcgi_cache, Cloudflare, LiteSpeed, host-level caching)
  2. Go to Tools → Site Health → Status
  3. Verify that page cache detection reflects the real server cache status

This PR is backward compatible and does not change existing Site Health UI behavior.

#12 follow-up: @solankisoftware
7 weeks ago

The PR #10606 was created by mistake and is not related to this ticket.
Please ignore that PR. The correct PR for this ticket is #10605.

#13 in reply to: ↑ 12 @westonruter
6 weeks ago

Replying to solankisoftware:

The PR #10606 was created by mistake and is not related to this ticket.
Please ignore that PR. The correct PR for this ticket is #10605.

I think you're commenting on the wrong ticket. I think you're intending to comment on #64370

#14 @peterwilsoncc
5 weeks ago

  • Resolution set to fixed
  • Status changed from reopened to closed

In 61381:

Docs: Update @since x.y.z with actual version number.

Follow-up to [60364].

Reviewed by jorbin.
Merges [61354] to the 6.9 branch.

Props solankisoftware, oztaser, westonruter.
See #43421.
Fixes #64366.

Note: See TracTickets for help on using tickets.