[MAGNOLIA-7203] Problem when generating sitemap from browser Created: 17/Apr/17  Updated: 12/Dec/17  Resolved: 24/Nov/17

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: 5.5.8, 5.6.1

Type: Bug Priority: Neutral
Reporter: Jonathan Ayala Assignee: Roman Kovařík
Resolution: Fixed Votes: 4
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
dependency
depends upon MGNLGS-134 Update sitemap URI mapping & config a... Closed
duplicate
is duplicated by MGNLGS-136 URI2RepositoryMapping to sitemap.xml ... Closed
relation
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Sprint: Kromeriz 118, Kromeriz 123, Kromeriz 124
Story Points: 5

 Description   

Solving a ticket concerning sitemaps app I've come across with an issue when I tried to generate a sitemap from web browser with Magnolia 5.5.2: There was a 404 page not found error. However, exporting the sitemap there was no problem.

Doing the same with Magnolia 5.5 there was no problem so I started researching and found that there was an improvement (Jira MGNLGS-120) in gooogle-sitemaps module 2.4.2 (which is used by Magnolia 5.5.2) which had changed the value of the configuration parameter URIPrefix from /sitemaps to /sitemaps/. I tried again changing in the configuration app the value from /sitemaps/ to /sitemaps and after that, I could generate the sitemap from my web browser without problems.



 Comments   
Comment by Viet Nguyen [ 09/May/17 ]

Thanks jayala a lot for using and posting issue on Magnolia CMS. This is a bug from our side and we will schedule a fix soon.

Comment by Antti Hietala [ 28/Sep/17 ]

There are two parts to fixing this:

  • Validate user input in the URI field in the Sitemap app. Trailing slashes should be forbidden.
  • There is probably a bootstrap somewhere that comes with a trailing slash. Update the bootstrap file.
Generated at Mon Feb 12 04:21:41 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.