litespeedtech / litespeedtech/lscache_wp
edit_post and save_post commented out of src/purge.cls.php - surely a mistake?
Open
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 257
- Forks
- 123
- PR merge metrics
- No merged PRs in 30d
Description
edit_post and save_post were commented out of src/purge.cls.php in March: https://github.com/litespeedtech/lscache_wp/commit/ce68bb7e7ffa559ff9f4c70b474fddb0ebbfdf6f
This is surely a mistake?
//register purge actions
$purge_post_events = array(
// 'edit_post',
// 'save_post',
'delete_post',
'wp_trash_post',
'clean_post_cache', // This will disable wc's not purge product when stock status not change setting
// 'wp_update_comment_count', // TODO: check if needed for non ESI
);
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in src/purge.cls.php at the purge_post_events array and compare the March commit linked in the issue with the current hook registration. Confirm whether edit_post and save_post should trigger purging, then verify the resulting behavior for post edits and saves; done means the intended hooks are correctly registered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php, wordpress
- Domain
- backend, performance
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100