Conversation
Notices
-
@widget - Looks like #rdnrefresh is breaking every so often. I'm getting an error with the function toLowerCase - which looking at the current version seems to be caused by a lack of a username prior to the conversion? The username is defaulting to administrator only sometimes though even though it's wrapped in a try. I'm guessing it's just the cookie call failing from time to time (and it seems to be only on profiles and groups). ~ Just a thought. It's also breaking on the mainpage (only the mainpage apparently) on a toLowerCase as well; which seems to be either in hideSpoilers or hideUsers because the error references a '.each' as the container.
Monday, 28-May-12 03:12:20 UTC from web- RDN's Lucifer likes this.
-
@haganbmj oh look, it's hagan
-
@haganbmj It's more due to the recently implemented scripts on the page by Cerulean than by RDNrefresh itself. Though strangely, 1.6 works fine.
-
@abigpony Where? O.o
-
@nerthos I was on an older version of refresh up until today and that was still running fine. I'm not familiar with the JSON cookie calls that have recently been implemented - though they seem to not be the main problem them.
-
@haganbmj I don't know /exactly/ what was implemented, but it really annoys me. It broke the way I used RDN. It might cause a lower stress on the servers, but it's really bad as far as client-side performance.
-
@haganbmj this busta
-
@nerthos When I was originally writing the script the fear was overloading the server with too many requests. As long as the refresh interval isn't too quick though it's not doing much. ~ I haven't touched #rdnrefresh in months. As a result I have no idea what the current status of it is. :/
