[#15792] - [4.0] Enable Caching, Hit counter doesnt increment
- Closed
- 3 May 2017
- Medium
- Build: staging
- # 15792
Steps to reproduce the issue
Enable caching in Joomla 4.0
Progressive and Platform specific on
Cache handler = file
reload a content item on the frontpage
Expected result
Hit counter increments, while still allowing the page to be cached.
Actual result
Hit counter doesn't increment on the page - BUT IT DOES increment in the database meaning once the cache is cleared, or expires the page updates
joomla-cms-bot
- | Labels |
Added:
?
|
||
franz-wohlkoenig
- | Category | ⇒ | com_cache |
Also, how many of these issues you've reported are unique to 4.0? Because surely this doesn't seem like something that's different from current 3.7 behaviors.
Also, how many of these issues you've reported are unique to 4.0?
Im only testing 4.0
It would be interesting to see what performance gain is being got by showing outdated information but still doing a sql update...
If this is the way its meant to be then I guess thats ok..
| Status | New | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2017-05-03 14:08:23 |
| Closed_By | ⇒ | PhilETaylor |
It would be interesting to see what performance gain is being got by showing outdated information but still doing a sql update...
Well, for this part at least the component view isn't being triggered, a cache file is being read. So the view isn't having to load the model, issue the database query(ies), trigger plugin events, or render the layout. So, seems like a fair trade off to me.
If the counters are incrementing in the database then what's the issue? Aside from showing an outdated number based on when the cache snapshot was created.
If the counter had to update correctly on each load, that would basically invalidate caching. Only possible ways around that are partial caching or using a plugin event to put in the right number, still requiring an extra database query.