[MGNLGS-3] Multi-site issues, virtual URIs Created: 19/Nov/10  Updated: 04/Sep/18  Resolved: 04/Nov/15

Status: Closed
Project: Google Sitemap (closed)
Component/s: None
Affects Version/s: 1.2.1
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Antti Hietala Assignee: Unassigned
Resolution: Won't Do Votes: 2
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Edit-page.png     XML File google-sitemap.xml    
Issue Links:
causality
relation
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

Issues with Google Sitemap module:

  • Virtual URI mappings are displayed on the Edit page but are not published to sitemap.
  • The module is not multisite/locale aware. It doesn't let the user decide if locale specific pages should be in the sitemap. They don't show up on the Edit page.

Resolved in 1.2.1:

  • Page URLs in the sitemap are not correct

Workaround exists:

  • All virtual URI mappings are read from the system. Most mappings, such as those defined in adminInterface module, are not relevant for SEO. And search indexers would not understand regular expression toURI values. The user can hide irrelevant virtual URIs from the sitemap.


 Comments   
Comment by Magnolia International [ 19/Nov/10 ]

Hmm, turns out the working version on our corporate website was built from a snapshot that does not entirely correspond to the 1.1 issue.

Comment by Federico Grilli [ 19/Nov/10 ]

If I'm not mistaken, Christian should have already done something to address the issues raised in this ticket.

Comment by Antti Hietala [ 21/Sep/12 ]

Updated issue for Google Sitemap module version 1.2.1. One of the original issues has been resolved. A workaround exists for another issue. The virtual URIs are still not present on the activated page which I consider a bug. And it's not site aware. Dropping priority to Major.

Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 02:05:30 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.