By default, the option for visitors to reassign a listing has been showing up for members on both the submit listing and edit listing pages. I feel this can be confusing on the submit listing page and people may end up generating new accounts and assigning listings to them when they don't read carefully. I can't think of any reason by a non-admin would want to reassign a listing during the submission process -- an admin would want to, and a member might want to reassign later when they sell a site but not during submit.
In the last few days: Changed WSN Forum's category names to use tags for better SEO. Converted the registration defaults to use a serialized array instead of the previous custom format, and added a helper function for changing a registration default. Did a lot of code refactoring for 9.2. Improved the details of parameters in backtraces in bug reports. Made a lot of progress on the ability for the upgrader to update templates and styles from a theme instead of from the standard. Hopefully this will be finished for 9.2.1.
Found a nice tool called browsera for detecting javascript errors and layout problems that are specific to Internet Explorer. Most of the time, WSN's template conditionals make things easy. There's a long-standing annoying case where they're buggy, though: checking whether a complex HTML field contains a term. Suppose you want to do This listing mentions a widget. If the description has HTML tags, the conditional can error because the closing tags in the HTML are taken as closing the conditional.
The biggest issue with using a custom theme is that it gets out of date. The bootstrap theme modifies the majority of the templates, so it's especially succeptible to this. I'm thinking about how to allow people to use themes without that drawback. Here's the plan so far. Each theme can include a special file that specifies a URL to get a theme-specific template schema. WSN's manage templates page and upgrade.php can then check that URL, which will return an array of standard uniqueness hashes for theme-customed templates.
Just released 9.2.0 non-beta, though as the experimental series it's always kind of beta. Most people will probably hold off on upgrading to 9.2 until there's a specific feature you want in it. Note that the 7.1 series is now expired, so the active series are 8.0, 9.0, 9.1 and 9.2. Really there's no reason to use 9.0 though, because the upgrade to 9.1 is easy and 9.1 is now the stable series. Discovered that the 'last post' link for threads in WSN Forum was getting cached to older pages of the thread when using Firefox.
Came upon an annoying little bug that only affects WSNs which were originally installed more than a decade ago and upgraded to 9.1. The category parent field was originally a tinyint instead of an int field, and this caused it to be treated as a boolean by the fairly recently added field normalization code, resulting in categories becoming subcategories of category #1 when editing them. Fortunately I'm probably the only one who was affected, but I've added a field type fix to the upgrade script.
Today's first task was a long time coming. Using localStorage, I've finally got WSN 9.2 remembering the open or closed states of all the named boxes. When you click on a box title bar to minimize it, it now remembers that and stays minimized on future views. I'd previously considered doing this with cookies, but it risked running up against the maximum cookie length limit so I never implemented it. The other major envevour of the day was to add automatic error reporting to the autosetup.php installer.
Fixed some issues with the helper queue system which were causing updates to not get applied when a robot was the one triggering the helper call for it. That's the main change in today's 9.1.29 release. Just released 9.2.0 Beta 1. Most of the work in it is bootstrapification. I've made it so that when various images aren't present in the style images directory an appropriate bootstrap glyphicon is shown instead. This process entailed creating a new template function {FUNC_SHOWICON[iconname label cssclass]} which is now used to display a variety of icon-like images.
Started work on the 9.2 series. Immediate plans include integrating the HTML 5 audio tag for WSN Gallery (will backport that to 9.1 too) and an HTML 5 video player. If the video player requires a custom component I may add a components subdirectory and move all of the external component scripts (including ckeditor and the bulk uploader) into that for easier tracking and less top level clutter. In minor 9.1 work today:
Noticed today just how huge the difference in memory use is between PHP versions. A WSN page that uses 5 megabytes of memory in PHP 5.6 can use 40 megabytes in PHP 5.3. If you're still on PHP 5.3, time to upgrade! Your overall server and database performance will improve a lot as there's more free memory. I don't have any immediate plans to discontinue PHP 5.3 support, but the memory profile makes it more likely that I will. Memory is often capped at 32 M in php.ini so running PHP 5.3 can lead to a lot of out of memory errors.