[MGNLGS-12] Hiding a page does not work Created: 21/Sep/12  Updated: 13/Feb/14  Resolved: 10/Sep/13

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

Type: Bug Priority: Neutral
Reporter: Antti Hietala Assignee: Karel de Witte
Resolution: Workaround exists Votes: 7
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

When you hide a page from the sitemap (Edit properties > Hide in sitemap) it is still displayed on the activated sitemap on the public instance. So the page is marked for hiding but not actually hidden. However, if you request the sitemap page on the author instance using .xml extension, the hidden page is truly hidden.



 Comments   
Comment by Hugo Venancio [ 21/Aug/13 ]

i have the same issue. I guess the problem is related with the fact that Magnolia (in the Author instance) doesn't really realize the page was modified. If i look at the Status & Mod.Date of the page, it doesn't get changed, so "there is nothing to activate" in fact...

Comment by Karel de Witte [ 10/Sep/13 ]

The hideIngoogleSiteMap property is stored in the page itself, this means that the page that should be hidden in the sitemap should be activated as well, activating the sitemap only is not enough.
A discussion on whether this has to be taken in charge by the sitemap activation only has to be instantiated, but a contrario, doing it this (the current) way is pretty much the "magnolia" way of doing things since automatic activation of dependent pages or adding properties some where else could have other nefast side effects.

Comment by Hugo Venancio [ 10/Sep/13 ]

Hi Karel,

That was the trick we didn't find out ourselves
It works.

Thanks a lot for the info.

BR,
Hugo

Comment by Antti Hietala [ 10/Sep/13 ]

I agree that publishing the dependent pages automatically is not recommended. Consider reporting the dependencies to the user. Magnolia already does a dependency check when deleting a page (see attachment). Perhaps this functionality can be repurposed.

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