question about cache on approval
| Project: | modr8 |
| Version: | 5.x-2.5 |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Can someone please tell me if using the approval page in admin/content/modr8 clears or not the page cache?
If it is not cleared on approval then the cache may not expire until the next node is added thus leaving approved nodes in limbo until it finally expires again.
This is when cron is not running during the day, thus relying on page adds to reset cache_flush in cache_clear_all().
I have a site with an issue of pages not refreshing under a certain amount of traffic, and approved nodes are indeed not shown when intended.
If modr8 do clear the cache then i have some other problem to investigate, but this is one of the suspects and i couldn't find any cache clears in the modr8 module.
On the tested site nodes are added at a certain times, like in the morning and evening, then approved hours afterwards at noon, night and early morning for the respective shifts.
With minimum cache lifetime of one hour nodes approved by 10:00 show up about 13:00 after new nodes are added between 11:00 and 12:00 and thus are not shown during the morning.
Nodes approved by noon show as normal because cache expires soon enough, and afternoon nodes have a smaller delay.
Nodes approved by the evening are fine because cron runs at night and clears the cache.
If modr8 approval doesn't clear the cache then do you think using the modr8 hook would be the right way to solve this?
Thank you
