You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Posts in category ID 208 are still appearing on my post-sitemap.xml. I know it's not a caching issue because I subsequently added a test post and it appeared in the sitemap immediately. I have tested this with numerous different categories and with including single or multiple IDs in the array.
The code should probably either be corrected or removed.
[X ] I've searched for any related issues and avoided creating a duplicate issue.
UPDATE: The only way I was able to actually successfully filter the sitemap was using the wpseo_sitemap_entry filter. Filters I tried that didn't seem to ever run: wpseo_exclude_from_sitemap_by_term_ids, wpseo_sitemap_exclude_post, and a query with wpseo_sitemap_posts_query. Some sort of clearer documentation might have saved me some time.
The text was updated successfully, but these errors were encountered:
Please give us a description of the issue
On https://github.com/Yoast/developer/blob/main/docs/features/xml-sitemaps/api.md you give a function for removing taxonomy terms from site maps.
I've aadded the following code to my theme functions.php:
Posts in category ID 208 are still appearing on my
post-sitemap.xml
. I know it's not a caching issue because I subsequently added a test post and it appeared in the sitemap immediately. I have tested this with numerous different categories and with including single or multiple IDs in the array.The code should probably either be corrected or removed.
UPDATE: The only way I was able to actually successfully filter the sitemap was using the
wpseo_sitemap_entry
filter. Filters I tried that didn't seem to ever run:wpseo_exclude_from_sitemap_by_term_ids
,wpseo_sitemap_exclude_post
, and a query withwpseo_sitemap_posts_query
. Some sort of clearer documentation might have saved me some time.The text was updated successfully, but these errors were encountered: