Same thing for you too Rufus, your subscription to the above thread was also an edge case that I’ve never tested before. Should work now. Please let me know.
Hi there how2, the checkboxes under “Subscriptions” in your account settings for disabling notifications needed to be checked, so I did it for you. You shouldn’t receive any more notifications now. Please don’t mark them as Spam, that will only cause problems for all our users. If you mark a mail as Spam, that could the e-mail service to mark all messages from BLF as Spam and cause problems for all of our users who do want to receive notifications. Thanks in advance.
Identified and fixed another bug. The system was mistakenly sending a notification for every comment in a poll thread, instead of checking to see if the user already received a notification.
That has been normal behavior of the notifications. You'll get a correct link to the correct post only if it falls on the first page of the thread. A notification for a post on another page simply does as you found out - only directs to the original post. (Can't remember how the "posts per page" affects this.)
I really appreciate you offering to take a look. But basically a lot of people have tried, and failed to come up with a good solution. https://drupal.org/node/26966
The good news is that it is supposedly fixed in Drupal 7. I just need to find a LOT of time to upgrade BLF to Drupal 7 and test and fix the inevitable issues that arise with the new platform.
True. But at this point an upgrade to the next major version of Drupal is inevitable, so fixing it in our current version would probably be wasted effort, if indeed it was possible to fix it.
Then we need just temporary hack until upgrade to drupal 7 happens.
Please hardcode (if possible in the code) high page number (for example 99999999999) like:
Drupal will always put you in last page available (and I don’t think there is more pages than such number) thus making
“better” behaviour in most cases.
Yeah, it is just a hack not a elegant solution. Personally I would prefer to end up on last page with bad post number than on first (bad) thread page with correct number.
I would assume one other problem with landing on the last page as a default is that the new post may be an updated post, not so much new. It could therefore be on the first, or a middle, or the end page. When you edit a post it appears as a new post too. Having the right post number, you can find the relevant post easy enough, getting a borked post number would be less useful.