Bug #47070
closed
History cleanup (clearHistory) inconsistent
0%
Description
In my opinion, the setting history maxAgeDays should be become an install tool setting, because the function setHistory / clearHistory from tcemain also acts globally.
Imagine a multi domain installation with two page trees as follows:
For the first tree history.maxAgeDays is set to 0 (via page TS), that means history entries should be kept forever. For the second tree history.maxAgeDays is not set, therefore the default value of 30 days comes into effect.
If someone now updates some content within the second tree, all history entries older than 30 days will be deleted - also the ones that affect the first tree ...
Updated by Mathias Schreiber over 9 years ago
- Target version set to 7.4 (Backend)
- Is Regression set to No
Updated by Susanne Moog over 8 years ago
- Target version changed from 7.4 (Backend) to 7.5
Updated by Benni Mack over 6 years ago
- Status changed from New to Needs Feedback
AFAICS This functionality does not exist anymore (did not find that) - can you help me out?
Updated by Riccardo De Contardi over 6 years ago
history.maxAgeDays has been removed in TYPO3 6.0 as far as I can read here:
https://docs.typo3.org/typo3cms/TSconfigReference/6.0/PageTsconfig/TCEmain/Index.html#tcemain-tables
Updated by Riccardo De Contardi over 6 years ago
- Status changed from Needs Feedback to Closed
Closed. See my previous comment: the functionality has been removed.
If you think that this is the wrong decision or there is still work that should be done, please reopen it or open a new issue with a reference to this one. Thank you.