NFXBeats
Customers
Post Count:299
 |
| 11 Feb 2011 01:04 PM |
|
- Type of Feedback: Something I hate
Setup: According to Will this issue is "Intended Design" but was going to be "looked at". It was originally reported in October 2010. Issue: After replying to a post on page 2 or greater, AF will always return the user to the top of Page 1. Scenario: User sees a 5 page post that has some great discussion. User is on page 2 and replies to a post. User get tossed back to page 1. User is a little annoyed, but navigates back to page 2 and continues reading. On Page 4 is another post user wants to reply to. User replies and is taken back to page 1 again. User is now very annoyed and can't recall if he was on page 3 or 4 so he goes to page 3 and then 4 to find his place to continue reading. User finds yet another post to reply to in this great discussion. User looks at reply button and thinks "aw screw it. It's not worth it" and leaves thread. User sees another popular topic with many pages. User stops participating because it's just too annoying. Thoughts: This has to be changed. FWIW AF did not function like this until vanity urls went it. I am NOT using vanity urls. I get complaints daily about this. I am losing users who just get so annoyed at this they would rather go elsewhere to have discussions. I consider this a SERIOUS FLAW in the product and more important than any new feature that might prevent a speedy fix. Please give me an official stance on whether this is an issue that is going to be fixed. |
|
| Status: I'm no longer moderated. |
|
|
Will Morgenweck
Forum Admin
DotNetNuke Staff
Post Count:7672
|
| 11 Feb 2011 01:07 PM |
|
As I mentioned in my previous replies to you about this same subject, it was the intended behavior due to changes with vanity urls. I also mentioned that it would be changed. Have you tried 4.3.4? |
|
Will Morgenweck
Director of Product Management
DotNetNuke Corp.
|
|
|
NFXBeats
Customers
Post Count:299
|
| 11 Feb 2011 01:26 PM |
|
I have tried that 4.3.4 and it is not fixed. Your previous comment was that it would be "looked at". If you would kindly please just respond with clarification that:
a) It is a bug that will be fixed
or
b) It works as intended and will remain.
I'm sorry to rail on about this, but it is completely a serious serious flaw ( IMO ) that is causing me to lose forum participation and field support message daily.
I fear you do not see the gravity of this situation and how quickly this needs to be fixed, since it's going on four months since I reported it. I was hopeful it would be fixed in the recent release of 4.3.4 and was very disappointed that it wasn't.
|
|
| Status: I'm no longer moderated. |
|
|
C Poole
Customers
Post Count:35
|
| 13 Feb 2011 03:16 PM |
|
I hate to throw my 2 cents in here, but..
NFXBeats - I agree this is an issue, it is causing a bit of a problem for me too. However, you need to tone it down quite a few notches. Will is continuously working to improve these products for us, and application life-cycle management requires him to set priorities for each bug or enhancement. IMHO, the squeaky wheel isn't going to get greased, it may just get ignored or prioritized much lower than hoped. |
|
|
|
|
NFXBeats
Customers
Post Count:299
|
| 13 Feb 2011 04:27 PM |
|
Really? Tone what down exactly? I'd like to know how I'm overblowing this issue. |
|
| Status: I'm no longer moderated. |
|
|
NFXBeats
Customers
Post Count:299
|
| 13 Feb 2011 04:37 PM |
|
Unless I misinterpret you C Poole, you are saying that by bringing light to this important issue, you are afraid that Will will give it less priority out of spite for someone to dare mention it? ie. The squeaky wheel won't get greased?
How would you handle this?
I really hope you are wrong about it. I hope that when more people like you admit that this affects them negatively, it will be seen as important enough to get fixed. I believe that Will has more character than you give him credit for.
My main problem is that Will has in the past refused to say this is a bug. He called it intended design. Yet he also stated it will be looked at. To me this is ambiguous. All I want is a simple YES or NO this will fixed. You are saying thats too much too ask? |
|
| Status: I'm no longer moderated. |
|
|
ron dyar
Customers
Post Count:91
|
| 13 Feb 2011 10:56 PM |
|
Our forum is currently offline so i am not really bothered by anything, but I think I remember something like this being a problem for me, so I would throw my vote as this being a problem.
LOVE the "Stauts: I'm no longer moderated" - that is funny. |
|
|
|
|
drew curry
Customers
Post Count:338
|
| 14 Feb 2011 08:18 AM |
|
Since feedback matters in helping Will make decisions: this is a simple usability factor that very clearly will drive new and not yet loyal users away. The same principle applies to every link that is built to any thread. If a post is implied as the area of focus for a link, then the focus of the target must be the post in question, not the end of the thread, not the start of the thread, but the *post* in question. Each post in each thread for most forums i frequent are anchored with an ID and the return or the link has as a parameter that ID and the view is set to take you to that post. Facebook does this well, so should we.
The irony of this is that loyal and dedicated clients are "pestering" for this in order to get their own loyal and vested clients. |
|
|
|
|
NFXBeats
Customers
Post Count:299
|
| 14 Feb 2011 12:04 PM |
|
Heres an example of the top threads in one of my forums  Imagine a user trying to participate in some of those threads being kicked to page 1 after each reply. How many replies would you make before you gave up? |
|
| Status: I'm no longer moderated. |
|
|
drew curry
Customers
Post Count:338
|
| 14 Feb 2011 01:46 PM |
|
;) some of us can only dream about threads of that size.. |
|
|
|
|
drew curry
Customers
Post Count:338
|
| 14 Feb 2011 01:47 PM |
|
as a related aside: after completing a post, why not roll the screen to the post you just entered? Why rest at the top of the page? I just posted the last and realized i might have made a booboo and had to scroll down, when in reality, the standard experience is that you see the last post, your post, after posting. |
|
|
|
|
paidinfull
Customers
Post Count:59
|
| 14 Feb 2011 04:21 PM |
|
Isn't this a part of the user preferences?
My Settings > My Preferences > Sort Order |
|
|
|
|
paidinfull
Customers
Post Count:59
|
| 14 Feb 2011 04:22 PM |
|
Additionally, quick reply doesn't cause this functionality either... if I'm understanding the issue correctly.
|
|
|
|
|
Will Morgenweck
Forum Admin
DotNetNuke Staff
Post Count:7672
|
| 15 Feb 2011 07:39 AM |
|
Just changed my default page size to 10 and now replying with quick reply to make sure it is working as intended. |
|
Will Morgenweck
Director of Product Management
DotNetNuke Corp.
|
|
|
Will Morgenweck
Forum Admin
DotNetNuke Staff
Post Count:7672
|
| 15 Feb 2011 07:39 AM |
|
Test again |
|
Will Morgenweck
Director of Product Management
DotNetNuke Corp.
|
|
|
Will Morgenweck
Forum Admin
DotNetNuke Staff
Post Count:7672
|
| 15 Feb 2011 07:40 AM |
|
and again |
|
Will Morgenweck
Director of Product Management
DotNetNuke Corp.
|
|
|
Will Morgenweck
Forum Admin
DotNetNuke Staff
Post Count:7672
|
| 15 Feb 2011 07:43 AM |
|
Here is the official response.
1) The behavior change that was introduced in 4.3 was not a bug and was only intended to be temporary.
2) In 4.3.4, we changed the behavior so that regardless of the type of URLs you are using you would be redirected to your post.
3) There does appear to be a bug in 4.3.4 which prevents you from jumping to your post if your post is the last past for that page. I just reproduced it here. However, in all other situations it does redirect to your post. |
|
Will Morgenweck
Director of Product Management
DotNetNuke Corp.
|
|
|
drew curry
Customers
Post Count:338
|
| 15 Feb 2011 08:00 AM |
|
thanks Will, i am sure many of us will be very happy to see this issue put to rest ;) |
|
|
|
|
NFXBeats
Customers
Post Count:299
|
| 15 Feb 2011 11:33 AM |
|
Testing... change my settings to 5 posts per page. I'm quick replying from Page 3 of a 4 page thread. |
|
| Status: I'm no longer moderated. |
|
|
NFXBeats
Customers
Post Count:299
|
| 15 Feb 2011 11:34 AM |
|
Testing reply on page 4 of 4 page thread... |
|
| Status: I'm no longer moderated. |
|
|
NFXBeats
Customers
Post Count:299
|
| 15 Feb 2011 11:54 AM |
|
Results of test here at Active Modules.. works as described by Will, only fails on last page. Results of test at my site.. fails every time. You can see this in action in this video: http://nfurl.us/pageissue I'm using 4.3.4 at my site are your running a different version here? You should have my host login from previous support calls to verify this. Also those of you who I have previously given access to my site via PMs can test in the same topic thread as the video if you like. |
|
| Status: I'm no longer moderated. |
|
|
NFXBeats
Customers
Post Count:299
|
| 15 Feb 2011 07:23 PM |
|
One more thing in case it wasn't clear.. I do not use vanity urls. Perhaps Will's test is only indicative of sites using the vanity urls? |
|
| Status: I'm no longer moderated. |
|
|
NFXBeats
Customers
Post Count:299
|
| 18 Feb 2011 01:24 PM |
|
I'm just following up. Has this been tested and verified on a site that is NOT running vanity urls? |
|
| Status: I'm no longer moderated. |
|
|
Will Morgenweck
Forum Admin
DotNetNuke Staff
Post Count:7672
|
| 23 Feb 2011 01:03 PM |
|
The last post issue has been corrected in AF 4.3.5. This has been tested with standard DotNetNuke Friendly URLs and Active Forums Vanity URLs. It should work with other url providers. However, if you are using extensionless URLs, you must make sure that URL ends with a "/". |
|
Will Morgenweck
Director of Product Management
DotNetNuke Corp.
|
|
|
drew curry
Customers
Post Count:338
|
| 14 Mar 2011 11:11 AM |
|
Posted By NFXBeats on 11 Feb 2011 02:04 PM
Setup:
According to Will this issue is "Intended Design" but was going to be "looked at". It was originally reported in October 2010.
Issue:
After replying to a post on page 2 or greater, AF will always return the user to the top of Page 1.
Scenario:
User sees a 5 page post that has some great discussion. User is on page 2 and replies to a post. User get tossed back to page 1. User is a little annoyed, but navigates back to page 2 and continues reading. On Page 4 is another post user wants to reply to. User replies and is taken back to page 1 again. User is now very annoyed and can't recall if he was on page 3 or 4 so he goes to page 3 and then 4 to find his place to continue reading. User finds yet another post to reply to in this great discussion. User looks at reply button and thinks "aw screw it. It's not worth it" and leaves thread. User sees another popular topic with many pages. User stops participating because it's just too annoying.
Thoughts:
This has to be changed. FWIW AF did not function like this until vanity urls went it. I am NOT using vanity urls. I get complaints daily about this.
I am losing users who just get so annoyed at this they would rather go elsewhere to have discussions.
I consider this a SERIOUS FLAW in the product and more important than any new feature that might prevent a speedy fix.
Please give me an official stance on whether this is an issue that is going to be fixed.
Will the basic ability be fixed? I just clicked a link on your main community summary page to a 4-page thread And land at the top of the first page. I of course do not know how many pages or posts there are. So i start to read.. after a while, i start to remember this thread, then look down and realize i am waaay back in time and pages and have wasted yet another few minutes on yet another incorrect link from an AS summary view. Anchors please? Perhaps study fb's implementation for hints. My average everyday users just walk away, without even telling me how frustrated they are trying to find posts and info. NFX was absolutely right, this is a terrible situation and needs correcting in all use-case. Give us usable links and transfers. |
|
|
|
|