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
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