TYPO3 Core

Hello,

we have got the same issue at hoster mittwald, but not at any other hoster we are using. @Sybille Peters : were are you hosting?

@Christian von Holten

We host ourselves (university website).

Can you find out more, what is different on your hosters?

Question is, is it just the cache duration that is maybe shorter so the issue does not come up or is some mechanism established to adjust the cache for the pages with a publish date?

Hello,

I found a problem when hemnu is used like this:

tt_content.menu_newslist =< lib.contentElement
tt_content.menu_newslist {
    templateName = NewsList
    dataProcessing {
        10 = TYPO3\CMS\Frontend\DataProcessing\MenuProcessor
        10 {
            special = updated
            special.value.field = pages
            special.mode = starttime
            special.limit = 4
            as = news
        }
    }
}

When starttime of a page is set in a future time and finaly this date passes by, then this page will not appear until you flush the whole typo3 cache. And I mean not only flushing frontend-cache. You have to flush all. I dont know if there is an extra cache for hmenus, but I found a little work around. Instead of the code above I am using:

tt_content.menu_newslist =< lib.contentElement
tt_content.menu_newslist {
    templateName = NewsList
    dataProcessing {
        10 = TYPO3\CMS\Frontend\DataProcessing\DatabaseQueryProcessor
        10 {
            table = pages
            orderBy = starttime DESC
            pidInList.field = pages
            as = news
            max = 4
        }
    }
}

Therefor I had to change some little things in the used fluid template. Because there is no {newsItem.link} oder {newsItem.title} anymore I changed it to {newsItem.data.title} and for the link I have used <f:link.page pageUid="{newsItem.data.uid}">{newsItem.data.title}</f:link.page>

Maybe someone can have a look for this strange and bad behaviour in HMENU Processor?

@Christian Can you open a separate issue for the HMENU issue? It seems to be related but is a different problem, I think.

My original problem was that the starttime / endtime (of content on same page) did not work at all - (I suspected due to page being cached). I will now try to reproduce this.

Looking in the code, it should actually work, so I should not be seing this problem see \TYPO3\CMS\Frontend\Controller\TypoScriptFrontendController::getFirstTimeValueForRecord() as Xavier pointed out in #91561