Drupal 5.7.

TAC Lite 5.x-1.1 and Taxonomy are being used to create private pages for members only. These "private" pages of various content types show up on the generated xmlsitemap (along with the public pages). How can the private pages be kept off the sitemap? Thanks.

Comments

vickil5’s picture

vickil5 commented
Title: Removing remove private urls from xmlsitemap » Removing private urls from xmlsitemap
tebb’s picture

tebb commented

Subscribing

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Title: Removing private urls from xmlsitemap » Remove private URLs from the sitemap
Component: Other » xmlsitemap_term

Actually the module doesn't have the concept of private taxonomy; if you don't want those pages to appear, just disable the xmlsitemap_term module.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Title: Remove private URLs from the sitemap » Removal of private URLs
tebb’s picture

tebb commented

I don't know the intricacies of TAC lite or how you are using it, but in case it helps, there is also the option of not showing a particular vocabulary in the sitemap.

Edit the vocabulary and set it's "Site map priority:" to "Not in sitemap"

My understanding is that you could leave "xmlsitemap_term" enabled, but disable selected vocabularies.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Status: Active » Fixed

That is correct.
Working on both the Drupal 6, and Drupal 5 versions, I don't remember which features are in one version, and which in the other versions.

What Dru-p says it's absolutely true; set the taxonomy to not be in the site map, and their terms will not appear.

tebb’s picture

tebb commented

Oops, yes, to clarify, I have only used this on D6.

I don't know if this feature is available in the current D5 version.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented

I can confirm the functionality is present in the version for Drupal 6.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.