+dogbreathcanada Posted August 29, 2005 Share Posted August 29, 2005 Am I missing some aspect of the functionality of the site here? I keep having to set my popularity filter back to 100%, because every day or so, it keeps drifting to downwards. A few days ago it was at 90%. I set it back to 100%. Today it was at 80%. I've set it back to 100% again. Link to comment
+Tsegi Mike and Desert Viking Posted August 29, 2005 Share Posted August 29, 2005 I have to change mine twice as well, but I assumed it was because of the reboots of the site that has to be done with each bug correction. Link to comment
+dogbreathcanada Posted August 29, 2005 Author Share Posted August 29, 2005 I have to change mine twice as well, but I assumed it was because of the reboots of the site that has to be done with each bug correction. If our popularity filter settings are stored in the database (along with the rest of our user info), I don't see how a reboot would affect that. Now if our popularity filter settings are stored in our session data, then yes, I can see how a reboot would affect that info. Link to comment
+dogbreathcanada Posted September 1, 2005 Author Share Posted September 1, 2005 Again ... I login and my popularity filter is set to 80% again. (I always leave it at 100%). Is this drift a bug? Or is it by design? Or is it related to the server reboots? Curious so I don't have to bring it up again. Thanks. Link to comment
bootron Posted September 1, 2005 Share Posted September 1, 2005 Again ... I login and my popularity filter is set to 80% again. (I always leave it at 100%). Is this drift a bug? Or is it by design? Or is it related to the server reboots? Curious so I don't have to bring it up again. Thanks. I believe it has to do with the server reboots, as the default setting for premium members is 80%. I will soon program it so the session cookie is retained in the database for the popularity filter so it won't continue to happen. Sorry for the inconvenience. Link to comment
+dogbreathcanada Posted September 2, 2005 Author Share Posted September 2, 2005 (edited) Again ... I login and my popularity filter is set to 80% again. (I always leave it at 100%). Is this drift a bug? Or is it by design? Or is it related to the server reboots? Curious so I don't have to bring it up again. Thanks. I believe it has to do with the server reboots, as the default setting for premium members is 80%. I will soon program it so the session cookie is retained in the database for the popularity filter so it won't continue to happen. Sorry for the inconvenience. No rush. Easier to live with the hiccup now that I know what the problem is. Thanks for the answer, Boo. Edited September 2, 2005 by dogbreathcanada Link to comment
+The Blue Quasar Posted September 8, 2005 Share Posted September 8, 2005 Sorry Bootron... but it is happening again. I have had my Filters set to 100% so I can see everything... today, the filter drift started moving around again. It stated at 70% I put it back to 100% Then within 5minutes it was at 80% Then suddenly back to 70% I have put it back to 100% again (I think maybe I did that 3 times in the last hour) Sorry to have to bring it up again. The Blue Quasar Link to comment
+Tsegi Mike and Desert Viking Posted September 8, 2005 Share Posted September 8, 2005 Mine is acting up too. Cant seem to keep it at 100% Link to comment
+cache_test_dummies Posted September 8, 2005 Share Posted September 8, 2005 At the moment, for the most part my poularity filters are showing as 70% (down from the 100% value I usually have them set to). When I attempt to change the popularity filter to something other than 70% by clicking on the little red down arrow, I seem to always get sent back to the main Waymark Category Search page. Link to comment
+Tsegi Mike and Desert Viking Posted September 8, 2005 Share Posted September 8, 2005 I just click on the bar that is 100%. It will go to 100%, but then default right back to 70% when I click over to any other page. Link to comment
Jeremy Posted September 8, 2005 Share Posted September 8, 2005 I logged the bug here. Since it is a change in the code I'll lock this one and move it to the new thread. Link to comment
Recommended Posts