Paginated toplists get a job done: they allow your users to page through very long lists in their entirity. For a full page list which is the primary page content, this is fine. When the list people are paging is just a little box in a corner of the page, particularly if the box is below the scroll line, it's irritating that the entire page reloads to show the next toplist page. What we'd like to do is have a refeshless pager that just updates the toplist content quickly without affecting the rest of the page. That's what I've been working on this week.
Not too long ago, I added a twitter field for members to specify their twitter account. Given that WSN has had the facility to display twitter feeds for a long time (scripts.webmastersite.net/...tes/twitter-feeds-634.html) I decided today to make use of it by putting a twitter feed onto the view profile page. Surprisingly, using the dynamic {MEMBERTWITTER} in the feed construct opener worked fine. I did discover that feeds were always displaying 5 items regardless of how many were requested, fixed that.
On the submit and edit listing pages, WSN has javascript that automatically adds http:// to the start of the URL if someone forgets to type a scheme. Submit/edit also has backend logic that attempts to fix URL inputs. Despite this, I came across a client site with all sorts of junk data in that field. Some of it may be very old data from before WSN automatically prepended the scheme. Some of it probably comes from old imported data. To address these scenarios, I've made the 10.4.4 Beta 3 and later upgrades seek out and fix botched listing urls.
10.4.2 brings some improvements to WSN's link checkers, especially the dead link checker. It now records and displays the time a listing was last found to be down, along with the number of times it has been dead. Should make it easier for you to see whether a link is definitely beyond hope or just experiencing some temporary downtime. There's a new 're-check' option so you can re-check selected links (re-check works for dead, reciprocal and content checks alike). Also fixed some errors that were displaying when checking a site that has a bad SSL certificate.
I decided to start the 10.4 series today. Continuing the recent development strategy, 10.4.0 is identical to 10.3.36 and they will begin to diverge with 10.4.1. This means we can finally stablize 10.3 so that no new bugs are introduced to it from now on. If you've been running 10.3 with automatic updates turned off, this would be a good time to turn the updates on as they're safer now. If you've been running 10.2 or earier, this is the time to upgrade.