Opened 14 years ago
Closed 9 years ago
#4884 closed defect (bug) (worksforme)
Changing members page doesn't invalidate cache
| Reported by: | markoheijnen | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Core | Version: | |
| Severity: | normal | Keywords: | needs-patch reporter-feedback |
| Cc: |
Description
When you change the member page to something else then the cache isn't invalidated. And because expiration isn't set it means you need to reboot PHP or memcache.
Change History (5)
#5
@
9 years ago
- Milestone Future Release
- Resolution → worksforme
- Status new → closed
If the problem was that associating the members component with another page would lead to broken links when using memcache I cannot reproduce that on latest wp + bp trunk. And since there hasn't been any more reports of this issue on this ticket I think that we can close this one out and reopen with clearer steps to reproduce if needed. :)
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
What do you mean by changing the member page? Do you mean associating the members component with a different page with a different slug, and it breaks the links because of the caching?