Support for term/blog/post/user/etc cache flushes

Open
#108 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
wordpress
Domain
cli

Research direction

Start by reviewing the cache command's existing CLI entry points and the WordPress functions named in the issue, including clean_term_cache() and clean_comment_cache(). Determine which term, blog, post, user, and related cache flushes should be exposed without raw PHP, then define the command behavior and coverage needed for each supported cache type.

Written by the indexing model from the issue text.

Description

command:cache-flush

Feature Request

Describe your use case and the problem you are facing

Flushing the entire cache can be expensive, and sometimes you can flush just a group but that doesn't cover everything.

On the other hand there are functions that clear term caches that also touch some options, these aren't represented in CLI without forcing you to open a shell and execute the PHP call directly. Not all hosts allow this.

Describe the solution you'd like

A way to do something like https://developer.wordpress.org/reference/functions/clean_term_cache/ or https://developer.wordpress.org/reference/functions/clean_comment_cache/ etc without writing raw PHP code

Dominant language
Gherkin
Stars
16
Forks
25
Avg merge
7m
Merged PRs (30d)
2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Similar issues

More CLI issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.