preparing for the next code push

[kareila]

Hello people of Dreamwidth! We're expecting to do a code push in a couple of weeks, but there are a few open issues I'd like to see resolved before then. If you think you can assist with any of these, now would be a good time to get involved!

Issue #2304: Make the email spellcheck test a soft reject/hint instead of the hard reject it is currently. - This came up in the comments of the most recent code tour, where a change was made to catch more possible email domain typos, but it was pointed out that the resulting page didn't give the user a way to opt out of the correction. - Thanks to the UK hackathon participants for getting this fixed!

Issue #2014: Membership option won't save in Account Settings - The support board has seen several complaints about this, and the most recent comments on the issue suggest the nature of the needed fix. - This has been fixed, thanks!

Issue #2264: Error messages in cgi-bin/DW/Setting/ShortcutsKeypress.pm - This is a minor problem with the new module for keyboard shortcuts for Previous/Next Entry: there are some obvious syntax errors that need to be fixed before deployment. - This has been fixed, thanks!

Issue #2262: Enforce new "no commas in trust group names" rule - As a result of the upcoming new feature to allow a comma-separated list of access groups to be specified when posting by email, going forward we want to prevent new trust groups from containing commas. - Thanks to the UK hackathon participants for getting this fixed!

Issue #2308: user names in markdown now fail to convert if they happen at the beginning of a line - Following the fix to escape @usernames preceded by a backslash, now there is an edge case where @usernames at the very beginning of a line of input text are failing to convert. - This has been fixed!

These are the issues I consider to be most urgent, but any and all contributions are appreciated!

Comments

[denise]

Requests that haven't been answered yet aren't being ignored, I promise -- if something doesn't get an immediate response, it's because there isn't an immediately obvious answer. Stuff like "this thing isn't working for me" can often fall into that category when only a few people are reporting problems, because if we can't reproduce a problem, we can't even start trying to figure out a root cause and fix it. That doesn't mean that nobody's trying to fix it, though; it just means we can't give you any updates or estimates on a fix because we don't know what the problem is yet. Things that happen irregularly, only to a very small subset of accounts, or with no identifiable pattern will usually take a long time to get fixed -- we have very limited resources and we have to prioritize troubleshooting/discovery time by how many accounts an issue affects and how seriously it interferes with the use of the site -- but by leaving your support request open, it will stay on the list of things that need to get that troubleshooting time.

[filialucis]

Ah, OK -- that makes sense of course! I was a bit puzzled because I didn't receive any acknowledgment at all that my request had been received, and of course I have no way of knowing whether the issue is one of those things that affects only a small number of accounts, all I know is that it affects mine on every device and browser I've tried. As long as I know it's on the list, I'm happy to sit tight.