tt_news with many categories showing in different pages
for now there is a problem to create a sitemap for tt_news in situation when i have tens of categories each showing in different page, beacase i can't set a "Display page" unique for each category in "Link configuration". There is no sense to create as many records as much we have categories.
So my question is how to do this in right way?
And why this can't do automatically?
#1 Updated by Sebastiaan de Jonge about 9 years ago
- Category set to Suggestions
- Status changed from New to Needs Feedback
Partially I agree with you, it would make sense if the URL structure is the same that we don't need to duplicate the settings over and over if we have different display pages for our records. However in many cases the display page will be the same for each category.
I think it's also a bit of a challenge to implement something like this into the existing structure. But I can imagine something like a mapping for this with IRRE. Let me know what you think about that.
#2 Updated by Rafal Brzeski about 9 years ago
In my opinion the best solution in this case is get "Single-view page for news from this category" from tt_news category,
this great option in tt_news is often forgotten,
simply set the single-view page for every parent category in tt_news categories settings and all children's inherits this (first you should set "useSPidFromCategory = 1" in tt_news config)
Going this way we have done some modification in Advanced sitemaps, what is showing in screen shot, and voila, everything works great with one news record for sitemap.
I know this is not perfect, but i think this should be definitely done with "Single-view page for news from this category",
what you think about it?
#3 Updated by Nikolas Hagelstein about 9 years ago
i think one very flexible way would be to allow a marker for the "display" within the link configuration tab.
So, Just put an input field beyond the display page group field so poeple can decided whether they would like to use a static detail page or a dynamic one from the QUERY.
Should be pretty easy to implement.