This forum is primarily for reporting issues about Web Accessibility such as difficulty using mojoPortal with a screen reader or other assistive technology.
Post any feedback here related to improving the accessibility or usability of mojoPortal. As stated in our Accessibility documentation, it is an important goal of the project that both the front-end customer experience and the back end administration and content publishing features be accessible to as many people as possible. Ideally, if you post about problems, we will also be glad to have suggestions on how the problems can be fixed but all constructive feedback on these issues is welcome.
Added a blog module to the site and a few sample posts, there seems to be an issue with the blog paging see below (Viewing only excerpts so that screen shots can be taken)
Page 1 :http://img231.imageshack.us/img231/894/page1xm.png Page 2: http://img205.imageshack.us/img205/2953/page2bm.png url: http://localhost/th/Blog/ViewList.aspx?pageid=1&mid=6&pagenumber=2 Page 3:ttp://img267.imageshack.us/img267/8571/page3x.png here the problem starts it is showing post from previous page too Page 5: http://img215.imageshack.us/img215/1161/page5.png shows all the posts from page 2 onwards url: is http://localhost/th/Blog/ViewList.aspx?pageid=1&mid=6&pagenumber=1 System Info: mojoPortal Version 2.3.4.5 SQLite Operating System Microsoft Windows NT 6.1.7600.0 ASP.NET Version v4.0.30319 Running in Full Trust
Page 1 :http://img231.imageshack.us/img231/894/page1xm.png
Page 2: http://img205.imageshack.us/img205/2953/page2bm.png url: http://localhost/th/Blog/ViewList.aspx?pageid=1&mid=6&pagenumber=2
Page 3:ttp://img267.imageshack.us/img267/8571/page3x.png here the problem starts it is showing post from previous page too
Page 5: http://img215.imageshack.us/img215/1161/page5.png shows all the posts from page 2 onwards url: is http://localhost/th/Blog/ViewList.aspx?pageid=1&mid=6&pagenumber=1
System Info:
Please assist :)
thanks n regards,
nitin
Hi Nitin,
Thanks for the bug report.
I was able to reproduce the issue and fix it. It is now fixed in the source code repository and will be fixed in the next release.
Thanks also for the coffee!
Best,
Joe