Preview of page from docheader button shows root page when starttime is set
When the preview button in the docheader is pressed, not the actual site is shown but the root page. The preview button in the page details or in the page-tree context menu shows the selected page. Buttons on language columns also show the root page.
Failing buttos are red, working buttons are green:
Typo3 Version: 9.5.23 and 10.4.10
To test this:
1. create a page and set starttime to a future date.
2. click on preview button in docheader while in column/language view
See the page content of the selected / current page
What i can see:
The root page is shown with the parameter "?ADMCMD_simTime=123456789"
Updated by André Buchmann 8 months ago
Updated by Dennis Prinse 6 months ago
As I just mentioned at ticket #87759 this is still an issue at TYPO3 v10 and even worse than in TYPO3 v9.
The button in the last screenshot from within the page properties view doesn't work in TYPO3 v10. In TYPO3 v10, users even get send to the homepage using that button. In TYPO3 v9.5.24, the button from within the properties does indeed send users to the correct page and the preview seems to be working as expected by showing the page. And from within the pagetree context menu, the editor gets send to the correct page too.
However in TYPO3 v10.4.12 I can't seem to get the preview working from within the pagetree context menu of manually editing the url, users keep ending up at an error page (404 or 403 for example).
Where the view page module in TYPO3 v9 was working as a workaround too, the view page module in v10 has the same issues as using the docheader buttons and list module where te user is being send to the homepage.
Updated by André Buchmann about 2 months ago
This issue was partially solved with 9.5.25 by the changes made to the PageRepository in #92944 (https://github.com/TYPO3/TYPO3.CMS/commit/8b0e90c9a4)
For the default language the right url is now called with the "ADMCMD_simTime" param. This works fine on the server but locally I get 403 "Page Not Found Reason: ID was not an accessible page" (Can be local issue).
Translations work only if they have the exact same slug as the default language.
|Default Language||example.com/example-page||should be working|
|Translation with modified slug||example.com/de/beispiel-seite||results in 404 error|
|Translation with same slug||example.com/fr/example-page||works like default lang|