Feature #14277
open
Start/Stop time for pages is ignored in standard menu objects
0%
Description
Since menu objects are normally cached they will not change even if a new page would appear/disappear because the start/stop time was set.
Suggestion: Check start/stop time always, just before the object is fetched from the cache.
(issue imported from #M297)
Updated by Thomas Hempel almost 18 years ago
Seems to work now. Can't reproduce this with TYPO3 4.0. With enabled cache the pages doesn't appear if the start end/or enddate disables them.
Greets,
Thomas
Updated by Michael Stucki over 17 years ago
I still think there must be a problem with this:
- Imagine you have a page A that is listed in the navigation of page B
- Page A has stop time set to d+1 days
- No notification happens to the cache of Page B
Updated by
Updated by Alexander Opitz over 10 years ago
- Status changed from Accepted to Needs Feedback
- Target version deleted (
0) - TYPO3 Version changed from 3.6.2 to 3.6
Hi,
as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (4.5 or 6.1)?
Updated by Alexander Opitz about 10 years ago
- Status changed from Needs Feedback to Closed
No feedback within the last 90 days => closing this ticket.
If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.
Updated by Simon Schaufelberger about 10 years ago
- Status changed from Closed to New
Hi Alexander, yes this issue still exists, since it is NOT fixed!
Should the sitemap be cached generally? If yes for how long? Should the sitemaps cache get deleted via some logic to delete all sitemap caches whenever a page changes its online status?
Should the sitemap check every page check every single page recursively if the page is currently active?
Updated by Mathias Schreiber about 9 years ago
- Target version set to 7.2 (Frontend)
Updated by Benni Mack almost 9 years ago
- Target version changed from 7.2 (Frontend) to 7.4 (Backend)
Updated by Susanne Moog over 8 years ago
- Target version changed from 7.4 (Backend) to 7.5
Updated by Riccardo De Contardi about 6 years ago
This issue is still present on 9.2.0-dev (latest master); it can be easily verified in this way:
1) insert an HMENU TypoScript object in your pages or
1.1) Create a content element "Menu of pages"
2) add to 1) or 1.1) a page with an expiration date/time in the near future
3) open your site with a different browser; you still will see the page in both menus even after the expiration date, until you clear the cache
Updated by Christian von Holten almost 5 years ago
Still exits in 9.5.7. and i have to clear all caches if a pages will be enabled by starttime. Is there any workaround to disable cache for hmenu or something else? I wonder why I did not noticed such a essential problem in the last 10 years I worked with TYPO3.
Updated by Gerrit Code Review over 4 years ago
- Status changed from New to Under Review
Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/61395
Updated by Susanne Moog over 4 years ago
- Status changed from Under Review to Accepted
Updated by Benni Mack over 1 year ago
- Related to Bug #98964: Menu object caching creates too many records resulting in huge cache_hash table added