I have a RadGrid with SEO Paging and Routing turned on. I'm using the NextPrevNumericAndAdvanced mode with TopAndBottom position.
When entering a custom page number (i.e. page 33 of 66) and click on the go button it just goes to the current page.
The individual page number buttons are fine (except the CSS issue I've reported before) and go to the correct page.
7 Answers, 1 is accepted
I'm fine with making the Go button a post back.. in reality a search engine is not going to enter a value in the custom page box and click on the go button... they'll just go through the pages via the numbered links.
This is just unusable by my actual users and I want search engines to spider though all the pages so I can't just turn off seo paging.
I am afraid this is not supported. Nevertheless, I log it as a feature in our Ideas&Feedback portal where you can track the progress and vote for it. I hope our developers to include it soon.
Also I am unable to understand your point in the second inquiry. Could you please provide more detailed information?
That makes no sense. Why have a box to change the page number if you can't use it?
To me that's a bug not a feature request.
What I mean is you don't need to have SEO features on the box as search engines will spider though the SEO page links. They won't use the change page box so why not keep the box and button a regular post back? Especially as it's broken right now. That would work for me.
I have to say I'm really disappointed by your response. What? I've got to VOTE for a fix to a BUG? Yea.. not many people are using SEO with Routing with Mobile Render Mode like I am so it doesn't get enough votes so then what?
It's a BUG and you should give me telerik points for finding it.
Now I have to go build my own paging component and as I'm going to do that I'll be ditching RadGrid as I don't need all the features for my project and I'll just skin the base ASP Grid or use a repeater.
I will be seriously considering not renewing my subscription to Telerik products which I've had for over 10 YEARS. This isn't the first time I've received this type of response and what's the point of using your controls if I've got to constantly find a work around. The whole POINT to using Telerik is to save me development time!
I have created a fix for this issue as I don't need the custom page box for search engines I've changed my code so that users who are logged on will not get the SEO version and therefore a post back is fine even on numbered buttons.
I added this to the head of the page:
and in the code behind something like this:
Due to using routing I also added code to the code behind for the PageIndexChanged event when the page index is changed to perform a redirect to the correct URL. Not ideal but it works.
I'm still not happy though as I've once again had to add yet another "fix" in my code for things that Telerik should be doing but at least now my users won't be bugging me about this not working (unless they aren't logged on as they won't be able to enter a custom page).
Telerik, if you add great features such as SEO and Routing (which is the main reason I used a RadGrid) then you should support every combination of those features and not tell me it's not a bug. It's a BUG! If something doesn't work then it's a bug not a feature request. If I told my boss that he'd laugh his ass off. "Sorry, if you want a page to work correctly you'll need to put in a feature request boss.. that button you click on is on the page but not usable as that feature hasn't been implemented." LOL! You might get away with that if your boss isn't a programmer but we all know better around here. If one of my guys did that I'd tell them they did a half-arsed job and go back and fix it.
I remember when I first purchased your product over 10 years ago I would get responses back within the same day (sometimes within an hour) and fixes for BUGS within a very short period of time. It sounds to me you have less people (or more products) and they are stretched too thin and creating excuses because you don't have the man power.
I completely understand your frustration but the reported issue can be considered as limitation in the SEO paging since it is design to work correctly only with the default pager mode. We have to note this in our documentation so our customers to be better informed. Nevertheless, I will increase the priority of the issue and I hope our developers will fix it for the upcoming official release. Please excuse us for any inconvenience this might have caused you.