Posted by background_guy on September 21, 2010 at 8:07pm
2 followers
Jump to:
| Project: | Stumble |
| Version: | 6.x-1.1 |
| Component: | User interface |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
Hi,
I have been using stumble for months, and all of the pages that I have added since May are not showing up when you try to stumble onto it. Check out any page on http://www.backgroundguy.com or click on any of the pictures to see what i mean. From the Home page you can navigate to all the new content by clicking the page number below the pictures, but stumble wont automatically include anymore. Any suggestions on how to get the new content to show would be very much appreciated.
Thanks
Comments
#1
Yes, I am also seeing this. Clicking the stumble button simply takes me to pages that I've already viewed many times, even though the "prefer unread" button is checked in the settings. I'm not stumbling (at all) to new nodes that other users have created and which I've never viewed.
Changing priority to "critical", as this would appear to break core functionality of this module.
#2
After further testing, I've determined the following:
- If the "Stumble to unread nodes first" button is checked, then the module actually PREVENTS unread nodes from being stumbled to, instead of preferring them. You will NEVER stumble to the unread nodes.
- If this button is unchecked, then you will eventually stumble onto the unread nodes, but they (of course) aren't given preference.
- The problem is probably somewhere in lines 70-80 of stumble.module.
Dave, I realize this module is probably not your highest priority right now, but... how hard would it be to fix this? I'm slowly learning PHP, but I don't have the first bit of knowledge about MySQL queries, and it appears that's where the problem lies. I'm building my site around this module (a photo-rating site a la hotornot that needs to "stumble" to the next unread photo) and I hadn't realized this functionality was broken until just now....
#3
This appears to be fixed in 6x-1.x-dev, so that's what I'll be using, at least for now.