[MAGNOLIA-977] Cache module never flush cache Created: 19/Jul/06 Updated: 20/Feb/15 Resolved: 21/Jul/06 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 3.0 RC2 |
| Fix Version/s: | 3.0 RC3 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Stephane Galles | Assignee: | Fabrizio Giustina |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Linux |
||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Date of First Response: |
| Description |
|
When a page is published from magnoliaAuthor to magnoliaPublic, the cache module is supposed to flush the cache directory of magnoliaPublic. It never happens as the flushAll function of class info.magnolia.cms.cache.simple.CacheImpl uses the function delete of class java.io.File. This function does not work if the directory is not empty. Moreover, the mkdirs funtion of the cache directory will be called only if the cache directory exists. Say the cache is activated in magnoliaPublic. The end user will see a newly published page as appropriate (first load in cache). If ever modifications on this page are made and the page is republished, it will never be seen. |
| Comments |
| Comment by Fabrizio Giustina [ 21/Jul/06 ] |
|
fixed in svn for rc3 |