Details
-
Bug
-
Status: Closed
-
Resolution: Duplicate
-
6.2.X EE, 7.0.0 DXP FP27, Master
-
None
-
3
Description
Description
For a given site, generating sitemap.xml can involve requesting a layout (e.g., display page) that might not exist, due to an inconsistent database or some other reason. In those cases no file is generated, a message of "Not Found" is displayed:
and the following trace is printed to log:
ERROR [http-bio-9090-exec-10][PortletRequestProcessor:466] Forward does not exist
The expected behavior could be:
- to print a WARN log trace informing that such and such layout cannot be found,
- to generate a sitemap.xml without the inconsistent references.
Reproducing steps
A quick way to generate the error message and the log trace would be
- In the site, create at least a display page and a web content pointing to it.
- In the database, table layout, modify the value of layoutuuid for the display page.
- Request http://localhost:8080/sitemap.xml.
Observed: No file is produced. A message of "Not Found" is displayed and a trace of "Forward does not exist" (see Description section).
Expected: A file without inconsistencies is produced. A WARN log trace is printed showing information about the layout that couldn't be found.
Attachments
Issue Links
- duplicates
-
LPS-67693 Sitemap results in "Resource not found" when display page is a private page
- Closed
- is caused by
-
LPS-62450 Navigating to sitemap.xml can cause high CPU usage
- Closed
- relates
-
LPE-15988 Generating sitemap.xml does not complete successfully if a journal article references a nonexistent layout
-
- Closed
-