[MGNLGS-137] CLONE - Improved sitemap publication Created: 17/Oct/17  Updated: 22/Jun/20  Resolved: 22/Jun/20

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

Type: Improvement Priority: Neutral
Reporter: Michael Kemser Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: sitemap
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Debian 8


Issue Links:
Cloners
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

Hello Magnolia Team!

Right now we are working on the sitemap module and came across an issue.
Editing sitemap entries (like hiding it in the sitemap) actually requires the page itself to be published which is somehow inefficient.

We thought about possible changes / improvements to make managing sitemaps more comfortable and came up with the following ideas

  • Creating a new Action which also publishes the corresponding pages selected in the sitemap (only pages which were already published). This basically works but has the flaw of also publishing pending changes which may not be ready to be published.
  • Moving the relevant page properties to a subnode of the page and only publish this node. This would require some work as the whole sitemap process would have to be patched to reflect this.
  • Right now we just moved the "Edit sitemap entries" dialog to the page properties dialog itself, which makes it more comfortable to manage the sitemap.

--> The desired approach would be some kind of partial publication of the pages for the sitemaps which only publishes the relevant part. This would definitely improve the whole sitemap app by a lot.

We're also open for other suggestions.

Best regards
Olaf Kozlowski / Vivian Steller (on behalf of Michael Kemser of AllSecur)



 Comments   
Comment by Viet Nguyen [ 17/Oct/17 ]

Supporting ideas:

Right now we just moved the "Edit sitemap entries" dialog to the page properties dialog itself, which makes it more comfortable to manage the sitemap.

--> This is a great idea as an improvement, anyway when we are moving our pages, the parent page also affected then you would also have to go to your parent page to activate the publication.

The desired approach would be some kind of partial publication of the pages for the sitemaps which only publishes the relevant part. This would definitely improve the whole sitemap app by a lot.

--> This would possible but required us a lot of efforts when traversing the whole sitemaps for any change, any move, any update and run a complicated graph algorithm to detect 'the relevant part' to publish. Would be great if you could also have some idea or suggestion for an affordable solution then we will happily go with that.

Anyway detaching sitemap info from website workspace, probably move it to googleSitemaps workspace would also a good idea for the very first refactoring and improvement step. Please let me create an improvement ticket so that our development team could be aware of this.

Comment by Viet Nguyen [ 22/Jun/20 ]

This module has been closed due to issues affecting its functionality. We recommend that you create a sitemap from a Solr index as an alternative.
https://documentation.magnolia-cms.com/display/DOCS57/Google+Sitemap+app

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