Last post 2 hours 36 min ago
Posts last week 81
Average response time last week 44 min
All time posts 70354
All time tickets 10858
All time avg. posts per day 20

Helpdesk is open from Monday through Friday CET

Please create an (free) account to post any question in the support area.
Please check the development versions area. Look at the changelog, maybe your specific problem has been resolved already!
All tickets are private and they cannot be viewed by anyone. We have made public only a few tickets that we found helpful, after removing private information from them.

#6345 – Help with K2 -- redundant blog/user and feed URLs

Posted in ‘Pre-sale questions’
This is a public ticket. Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.
Tuesday, 13 September 2016 20:50 UTC
atomhbc
Hello,

I wonder what advice is regarding the following issue.

Since the last major K2 update -- and the introduction of the K2 sh404 plugin -- K2 has triggered sh404 creating URLs that were not created before the K2 update. There are two main parts of the URLs: blog/user URLs and the feed URLs. In one of my websites where there is search feature, this creates 000's of more URLs. In another website, I have lots of subscribers, and now there is a blog/user URL for every subscriber.

I asked K2 support how I can stop K2 to trigger sh404 to create the URLs. They answered "No, this cannot be done ... A prefix is needed in order for the extension to differentiate between types of content." (They were referring to the "blog" and "feed" prefixes.

Do you think this is something that the K2 team should address?
The fact that I have few thousand redundant URLs in the sh404 database, should this be a concern? Would this slow the rendering of website?

Regards,
Tom
 
Wednesday, 14 September 2016 11:25 UTC
wb_weeblr
Hi

1 - Please note that K2 last release did not introduce the K2 sh404SEF plugin. K2 has always provided support for sh404SEF, and they have always had such plugin. They simply decided to take it out of the main package and make it a separate download.
2 - Based on #1, I don't know if they actually changed something in the way they built URL. I actually doubt it: why would they changed something if it was working before? They are the only ones who can reply to that however.
3 - Having less URLs in the DB is alway better. That said, if you only are talking about a few thousands, that should not be a problem. Queries are indexed and optimized, so reading should not be affected, at least on the front end, where it matters.
4 - Not sure what you mean by "redundant". They are different URLs to different things.


Rgds
 
Wednesday, 14 September 2016 16:32 UTC
atomhbc
Thank you for your response.

What I mean by redundant is that the given URL loads a page that doesn't have meaningful content for the visitor and that we want to shield from Google.

For example:
baysidefurniture.com/blog/gabor (the URL lists the k2 items the user called Gabor created.);
baysidefurniture.com/search/bed/feed (the combination of search and feed creates 000s of "redundant" URLs

Regards,
Tom

Ps.: I am sorry, I realize that I should have entered this inquiry to the tickets section.
 
Wednesday, 14 September 2016 16:38 UTC
wb_weeblr
Indeed, you might want to open a ticket about this, this is not realy pre-sale!

Rgds
 
This ticket is closed, therefore read-only. You can no longer reply to it. If you need to provide more information, please open a new ticket and mention this ticket's number.