Issue Feature Under Review Quiet

#14277Start/Stop time for pages is ignored in standard menu objects

Michael Stucki 08/20/04, 08:45 updated 10/22/26, 10:28

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)

Reviews 2

History 1518

  1. Thomas Hempel commented <span data-processor="relativetime" data-value="2006-06-01T14:11:47+00:00" > 06/01/06, 14:11 </span>

    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

  2. Michael Stucki commented <span data-processor="relativetime" data-value="2006-08-09T12:37:40+00:00" > 08/09/06, 12:37 </span>

    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

  3. Alexander Opitz commented and changed status Accepted Needs Feedback target version TYPO3 Version 3.6.2 3.6 <span data-processor="relativetime" data-value="2013-10-21T09:18:29+00:00" > 10/21/13, 09:18 </span>

    Hi,

    as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (4.5 or 6.1)?

  4. Alexander Opitz commented and changed status Needs Feedback Closed <span data-processor="relativetime" data-value="2014-02-20T16:59:23+00:00" > 02/20/14, 16:59 </span>

    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.

  5. Simon Schaufelberger commented and changed status Closed New <span data-processor="relativetime" data-value="2014-02-20T22:06:09+00:00" > 02/20/14, 22:06 </span>

    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?

  6. Riccardo De Contardi commented <span data-processor="relativetime" data-value="2018-03-24T18:29:45+00:00" > 03/24/18, 18:29 </span>

    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

  7. Christian von Holten commented <span data-processor="relativetime" data-value="2019-06-03T10:08:28+00:00" > 06/03/19, 10:08 </span>

    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.

  8. Gerrit Code Review pushed patch set 1 for master to change 61395 status New Under Review <span data-processor="relativetime" data-value="2019-07-31T07:18:14+00:00" > 07/31/19, 07:18 </span>

  9. Benni Mack commented <span data-processor="relativetime" data-value="2025-04-04T06:59:33+00:00" > 04/04/25, 06:59 </span>

    Current status update – The problem still exists AFAIK:

    1. We need to take into account that pages might expire (= enddate in 1h)

    For this, the cache lifetime needs to be calculated with the items that have an enddate and use page[enddate] ? min($lifetime, $page[enddate]) : $lifetime for each item.

    2. We need to take into account that new pages will be “published” in e.g. 1h (= starttime in now + 1h)

    This gets more tricky, because this would mean, we need to fetch records that have a starttime in the future FROM THE DB, then loop over all of them in PHP (+ calculating the lifetime of the cache entry with the starttime) and then filter them (no limit in SQL possible with this). Ideally, this would work with language overlays and workspaces as well…

  10. Gerrit Code Review pushed patch set 1 for main to change 96945 status Accepted Under Review <span data-processor="relativetime" data-value="2026-10-20T16:36:02+00:00" > 10/20/26, 16:36 </span>