I'd like to see an option on each page titled 'Show in site map' (checked by default).

I have several 'Thank you' pages on my site which I want to be 'active' so that they can be seen after submitting the relevant form, but I don't want to display them in the primary navigation. I can achieve both of these things with the current settings, however they then appear in the site map using {site_mapper}.

At present there's no way to hide certain pages from the site mapper except for manually entering the page alias and using some Smarty logic. This is obviously not ideal.

Share On:

site_mapper is MenuManager basically, so if a page is set to "Show in menu" it is shown in site_mapper.If parameter "showall" is enabled all pages will be shown, means also pages that have option "Show in menu" unchecked.

The tag {site_mapper} might sound as some standalone module but basically you don't have to use that tag as it is the same as if you were using {menu} and following MenuManager help and parameter options.

Share On:

But doesn't that mean there should be a better way? The only way I thought of doing it was adding a bit of text (e.g. 'hide') into one of the 'Extra1/2/3' attributes, but that means you can't use those fields for other information.

Anyway, it's just an annoyance of mine that there's no quick way to generate a site map and hide particular pages from it, but keep them active and/or in the site navigation.

Share On:

As mentioned above {site_mapper} has the same behavior as {menu} so if a page is set to "show in menu" it will appear in sitemap else not.

With parameter show_all="1" pages that were set to not show in menu will still be shown, if set to "0" then behavior should be the same as {menu}.Active/Inactive pages should not show at all, no matter of Menu or Sitemap setting.

Share On:

There are multiple pages that will need to be selectively hidden, and multiple that will need to selectively be shown.

I'm sure this isn't a scenario that comes up often, but it's still not easy. Plus, it would be a lot easier to simply check a box than have to edit the function call every time I create/edit/change the alias of a page.

Share On:

I'm sure this isn't a scenario that comes up often, but it's still not easy

Exactly thats why i hardly can see it comming into core, it is not common and i didn't see anyone else asking for it.You can still try to submit a FR and see if it makes into core.

Quote:

Plus, it would be a lot easier to simply check a box than have to edit the function call every time I create/edit/change the alias of a page.

Alias shouldn't be changed that offten (think of SEO and Search engine indexing, then you need to redirect that page every time you change it's alias), but still you can use "content_id" that way no matter what you alias is, content id number will never change.When you edit a page you will see content id in the url bar or when hovering over a page link in backend, so simply enter exculdeprefix='32' for example.

Share On:

Yeah, I was mainly thinking about my scenario and whether others would have the same problem. Imagine a site with 200 pages and more created every day, having to go and add that page ID to the list rather than just ticking a box when creating the page.

Share On:

Who is online

Users browsing this forum: No registered users

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot post attachments in this forum