Comments (12)
@Namstel Hi, I have created a ticket for our scrum board so that this issue gets a higher priority. We are busy with a project related with Strapi so that the issue/bug process will be a lot faster in the future. We are also still expanding and maintaining our plugins. You will hear from us as soon as we have something ready for this issue, I hope to have informed you sufficiently.
Kind regards, Tim Schipper.
from strapi-plugin-sitemap.
Hey @AlexDede
Thank you for the feature request.
I just want to clarify a couple of things.
How do you want to use the multiple patterns for a single collection type?
- Have multiple URLs going to the same page
- Select which pattern to use for each collection entry
from strapi-plugin-sitemap.
Hey @boazpoolman
Thank you for the reply.
How do you want to use the multiple patterns for a single collection type?
In my case I only need this for multi collection type. But I think that in some cases single collection type can be used for a few URLs on a site too (use different parts of data from single collection type).
Select which pattern to use for each collection entry
In my case I need each pattern for each collection entry and I think it will be enough for first version of this feature. In the future maybe it is possible to add an ability to select patterns to the block on a screenshot below.
from strapi-plugin-sitemap.
So if I understand correctly; you would end up with multiple URLs in the sitemap which will go to the same page?
Like:
/products/1
/products/1/addition
/products/1/other-addition
Which all correspond to the same entry (id: 1) in Strapi.
And also all show the same page in your website.
Why would you want that?
from strapi-plugin-sitemap.
you would end up with multiple URLs in the sitemap which will go to the same page?
Not exactly. In our case all this pages will be related to the same product but will show different parts of information related to this product. For example:
/products/1 -> some general information about the product with id=1 (like name, image, description, etc.)
/products/1/specifications -> specification of the product with id=1 (like width, height, weight, etc.)
/products/1/addition -> addition information about the product with id=1
But all this part of data will be saved in the same collection in Strapi with the same entry with id = 1.
from strapi-plugin-sitemap.
Ah allright, I get it.
Let me think about this for a little.
Probably just allowing a collection type to be used multiple times in URL bundles does the trick.
from strapi-plugin-sitemap.
Probably just allowing a collection type to be used multiple times in URL bundles does the trick.
We also need this feature in our project, we need multiple URL bundles for one collection type. is there an update on this? or any other solution we could use?
If you could give me a general idea of how it works or where to start, I'd be happy to give it a try and make a PR if it works.
from strapi-plugin-sitemap.
Hey @boazpoolman.
We too need this.
Here's why:
- We're looking to generate a Google News sitemap for a certain amount of recent articles.
- We're looking to generate a sitemap for a number of recent articles (less than 7 days old) with the changefreq of hourly
- Older articles would then have a changefreq of monthly
I had a pop at getting this working myself in a fork, but not having any React experience is really holding me back, and it all seems tighly coupled based on ContentTypes, making it very hard to have URL bundles be an array rather than a key-value based object where the key is the ContentType.
If you could point me in the right direction, I'd love to give it another go, but at this moment, the plugin doesn't meet our requirements.
from strapi-plugin-sitemap.
I hate to be a nag, but are there any updates on this?
from strapi-plugin-sitemap.
For our interest: Is this a feature you would pay for? We can then maybe give this priority on our roadmap.
from strapi-plugin-sitemap.
That would then be something I'd have to pay out of my own pocket, which I'm willing to do, but it's not going to be hundreds of dollars.
from strapi-plugin-sitemap.
I have an use case where I have a complex content type. And based on different columns I can have listing pages or single item pages.
Let's say
/item/[id]
/items/[city]
/items/[city]/[other_filter_param]
So I have all items in the city, single item or items in the city limited by param. Depending of combination each page can have its own unique content.
I'd even suggest that we do not have multiple sitemaps for same content type but rather multiple sitemaps based on custom filters. Same map can include one or several content types.
e.g. separate map for products and product images can be generated from same content type.
All maps together can work as composite sitemap.
At some point it can get to complex Feeds generator plugin.
But by limiting the scope to just sitemaps it should be possible to create them in a more flexible way.
my json suggestion
"sitemaps": {
"some_sitemap": {
"contentTypes": [
{
"type": "api::type.type",
"languages": {
"und": {
"pattern": "/en/[city]/[other_filter_param]",
"changefreq": "daily"
}
}
},
{
...same type with different filters or different content type
}
]
}
},
for now the workaround is to either hook into plugin or decompose entity into different content types
from strapi-plugin-sitemap.
Related Issues (20)
- Update dependencies to mitigate vulnerabilities HOT 1
- Not working with strapi 4.11.5 HOT 2
- Support excluding sites by condition HOT 2
- how to exclude a specific url for sitemap HOT 9
- Allow URL translation sets for custom URLs HOT 2
- How to combine multiple content-types? HOT 2
- Server.js configuration for the sitemap plugin HOT 12
- Error when generating sitemap on Strapi 4.14.4 and Node v18 HOT 2
- Multiple hostnames/host profiles HOT 1
- Critical dependency: the request of a dependency is an expression HOT 5
- Allow relational fields be declared in url patern recursively HOT 3
- Bug: excludedTypes config setting doesn't seem to work HOT 5
- Bug: missing settings labels HOT 5
- Make the <xhtml:link> element in XML optional HOT 1
- feature request: pretty print option HOT 6
- Feature Request: i18n `prefix_except_default` strategy HOT 8
- Sitemap Breaks When Exceeding Limit and Strapi Port Differs from Default HOT 4
- Add an additional link tag with hreflang x-default to improve locale detection fallback HOT 5
- Does not work with ADMIN_PATH and STRAPI_ADMIN_BACKEND_URL HOT 1
- Add extension points / hooks. HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from strapi-plugin-sitemap.