#106776PageTypeSuffix of RouteEnhancer
Description
When I added a PageTypeSuffix in order to have a fine URL for the XML sitemap, I get into massive problems assumably with the POST method of forms based to the news.
PageTypeSuffix:
type: PageType
default: '/'
index: 'index'
map:
news_sitemap.xml: 1533906435
My site news based, that means, there is hardly other content than news. So I configured the search of indexed search to the news. And I configured the comment extensions (pw_comments) as well to it.
But after adding the PageTypeSuffix, no results are displayed by searching. Indexing of pages (respectively news, that are route enhanced) worked as I checked in the database tables of indexed_search. And searching by GET method worked as well.
Similar happens to the EXT pw_comments. Adding normal comments to pages works. But when I tried to comment a news, the POST transfer from the form to the Controller action failed without any error. During debugging I recognized, the variable $newComment in the createAction is NULL.
Maybe there are correlations to [[https://forge.typo3.org/issues/88836]] or [[https://forge.typo3.org/issues/87104]] and it has to do with special page types, that are used in this case, too?
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
History 3
-
Holger Drosdek commented <span data-processor="relativetime" data-value="2025-05-27T09:17:50+00:00" > 05/27/25, 09:17 </span>
-
Holger Drosdek commented <span data-processor="relativetime" data-value="2026-03-26T13:03:25+00:00" > 03/26/26, 13:03 </span>
PageTypeSuffix: type: PageType default: '' index: 'index' map: sitemap.xml: 1533906435default has to be an empty string. So sitemap.xml will be callable and POST method of indexed_search works.
This Bugreport can be closed. -
Benni Mack commented and changed status
NewClosed <span data-processor="relativetime" data-value="2026-11-13T10:02:43+00:00" > 11/13/26, 10:02 </span>Thanks for the follow-up. default: ‘/’ is a supported value of the PageType decorator, and routing does not depend on the request method. Losing POST data without an error usually means a trailing-slash redirect (web server rule or redirect record) turned the POST into a GET. Since default: ‘’ solves it for you, as you said, I’m closing the issue. Please reopen with a reproducible setup if it shows up again without such a redirect.
In addition, deleting default and index values does not help: