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
As you can see, it is hard for the developer tool and check which content types we need to exclude from the sitemap one by one.
Suggested solution(s)
It would be better either to add a new property includeType or make the plugin check only the API content types, so things get easier, even more, it should only include those types and exclude the types we want from API content types since all plugins and Strapi content types are not public in the most of the cases.
As you can see from the comment yarn strapi content-types:list , the only content types we want to see are the following:
SalahAdDin
changed the title
Ignore all content types but the created by content type builder, i.e., api content types
[FEAT] Ignore all content types but the created by content type builder, i.e., api content types
May 7, 2024
Feature request
Summary
Checking the sitemap configuration for the setup of the URLs we find the following content-type hell:
It shows a lot of content types that we don't want to make part of any website.
We manually excluded them, but they are too much for the beginning, and no, it does not only include third-party plugin types:
Why is it needed?
As you can see, it is hard for the developer tool and check which content types we need to exclude from the sitemap one by one.
Suggested solution(s)
It would be better either to add a new property
includeType
or make the plugin check only the API content types, so things get easier, even more, it should only include those types and exclude the types we want from API content types since all plugins and Strapi content types are not public in the most of the cases.As you can see from the comment
yarn strapi content-types:list
, the only content types we want to see are the following:Related issue(s)/PR(s)
Let us know if this is related to any issue/pull request.
The text was updated successfully, but these errors were encountered: