Content Expiry Checker Testing 2

Okay, based on the current date (April 3, 2025) and the logic in the enhanced plugin (Content_Expiry_Checker_Pro), here are examples of content that would likely be flagged, and why:

2 weeks ago. I saw him two weeks ago.

1. Based on Relative Time Phrases:

• Content: “Our annual report from last year showed significant growth.” What about next year?

  • Why: The phrase “last year” refers to 2024. Since 2024 is now in the past relative to the current year (2025), the plugin flags this.
  • Status: Outdated
  • Message Hint: Contains “last year”. Verify if content for 2024 is outdated.

• Content: “We achieved great results last month.” (Assuming the post was published before April 2025, e.g., in March 2025 or earlier)

  • Why: Because the current month is April, “last month” (relative to now) is March. If the post is older than the current month, mentioning “last month” likely refers to a period now further in the past.
  • Status: Outdated
  • Message Hint: Contains “last month”, may refer to a past month.

• Content: “Looking ahead, next year we plan to launch version 3.0.”

  • Why: “next year” refers to 2026. While not outdated now, it’s time-sensitive and will become outdated once 2026 arrives. The plugin flags it as needing future review.
  • Status: Reminder
  • Message Hint: Contains “next year”. Content may need updating next year.

• Content: “The feature preview for next month is exciting.”

  • Why: “next month” refers to May 2025. Similar to “next year”, this is flagged as potentially needing an update once May arrives.
  • Status: Reminder
  • Message Hint: Contains “next month”. Content may need updating soon.

• Content: “Our targets for this year are ambitious.” (If the current date were Nov/Dec 2025)

  • Why: Although it refers to the current year (2025), the logic flags “this year” late in the year as a reminder to review before the year ends. (In April 2025, this would not be flagged).
  • Status (in Nov/Dec): Reminder
  • Message Hint (in Nov/Dec): Contains “this year”. Review before the year ends.

• Content: “Complete the survey this month to be entered into the draw.” (If the current date were April 21st, 2025 or later)

  • Why: The logic flags “this month” later in the month (after the 20th by default) as a reminder. (On April 3rd, this would not be flagged).
  • Status (Late April): Reminder
  • Message Hint (Late April): Contains “this month”. Review before the month ends.

2. Based on Specific Years:

• Content: “This research paper was originally published in 2026.”

  • Why: The plugin detects the year “2023”. Since 2023 < 2025 (current year), it’s flagged as referring to a past year.
  • Status: Outdated
  • Message Hint: Refers to past year: 2023.

• Content: “The 2024 conference proceedings are available online.”

  • Why: Detects “2024”, which is less than the current year 2025.
  • Status: Outdated
  • Message Hint: Refers to past year: 2024.

• Content: “See our 2025 event schedule.” (If the current date were Nov/Dec 2025)

  • Why: Detects the current year “2025”. When scanned late in the year, it flags this as a reminder. (In April 2025, this would not be flagged).
  • Status (in Nov/Dec): Reminder
  • Message Hint (in Nov/Dec): Refers to current year (2025), review before year end.

3. Based on Custom Phrases/Regex (Examples):

• Scenario: User added event concluded as a custom phrase in settings.

  • Content: “Following the meeting, the event concluded successfully.”
  • Why: Matches the custom phrase exactly. Custom phrases default to reminders.
  • Status: Reminder
  • Message Hint: Contains custom term: “event concluded”. Review required.

• Scenario: User added /sale ends w+/i (matches “sale ends” followed by a word, case-insensitive) as custom regex.

  • Content: “Hurry, the Spring Sale Ends Friday!”
  • Why: Matches the custom regex pattern.
  • Status: Reminder
  • Message Hint: Contains custom term: “Sale Ends Friday”. Review required.

Combined Example:

• Content: “Published Jan 10, 2025: Our review of 2024 showed strong results, beating last year‘s figures. We anticipate the product launch happening next month.” (Assuming ‘product launch’ is a custom phrase)
  • Why:
    • 2024: Detected as past year -> Outdated.
    • last year: Refers to 2024 -> Outdated.
    • product launch: Custom phrase -> Reminder.
    • next month: Refers to May 2025 -> Reminder.
  • Overall Status: Outdated (Outdated takes precedence over Reminder).
  • Message Hint: Would likely combine messages, e.g., “Refers to past year: 2024. Contains “last year”… Contains custom term: “product launch”… Contains “next month”…”

The plugin aims to catch explicitly time-sensitive references that are likely to become inaccurate as time passes, giving editors a prompt to review and update the content.