![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png){kind=small}
Entry tags:
Weekly Update: 12 January
This week's update comes to you a day late courtesy of me sleeping through all of Monday. Literally. Oops?
Big bunch of stuff this week behind the cut!
Sunday night's code push brought us a whole whackload (that's a scientific term) of new features and bugfixes. You can see the whole list of last week's development efforts at the weekly code tour!
Meanwhile, some of the new stuff includes:
A frequently-requested change: we've updated the comment screening process so that a). an account owner's or community maintainer's comments will obey the screening setting for the entry itself (so no more of your comments being posted unscreened when you've chosen to screen all comments) and b). replying to a comment will no longer automatically unscreen it. This is one of our more frequently requested changes, so have fun!
Paid accounts can now use the Popular Subscriptions page, to see who's most read by the people you read. Go forth and find new content! (And thank![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
yvi for coding it.)
We've added two new filters to the Inbox: poll responses (for those who subscribe to notifications of poll answers) and unread items (to find those notifications lurking in the depths of your inbox that you can't find anywhere else).
We've added an option for the crossposter to re-enter your password every time you want to crosspost, rather than saving the password with us. To use this, set your crosspost settings. When you edit your defined crosspost account or create a new one, you'll have an option to save your password; leaving it unchecked will prompt you for your password every time you crosspost.
* The Gradation Vertical sitescheme has had a bunch of tweaks for usability, so things that were displaying improperly should now be fixed. If you notice anything that still doesn't look right, report it to Support or drop a comment to the developer who's working on it, and we'll get it fixed right up.
* The problem with custom crosspost footers over 256 characters being truncated after a certain amount of time is fixed now. (And was totally my fault. Mea culpa.)
* The problem with crossposts failing when there were certain HTML entities in cut text has been fixed.
* The problem with RSS feeds displaying certain characters incorrectly is now fixed.
Support would like us to let people know that if you're having problems seeing long entries in the Tropospherical site schemes, you should add ?usescheme=celerity or ?style=light to the end of the URL and see if that fixes it. If you still have problems after that, contact Support and they'll do what they can to help you! (It's a problem with how Firefox displays certain CSS, and the Firefox people say that they should have it fixed in the next major release.)
In general, if you spot anything that isn't working right, or that you think might be a bug, we want to hear about it! Unless it's listed in the Current Issues FAQ category, don't assume we know about it. If there's something that doesn't work for you, please please please report it to Support so we can look into it and fix it as soon as possible.
![[staff profile]](https://www.dreamwidth.org/img/silk/identity/user_staff.png)
mark will be in Sydney, Australia for a few days later on in the week, and then both of us will be in Wellington, NZ next week for a conference, so if anybody wants to get together for a Dreamwidth meetup, keep an eye on mark.
*
Hm, I still feel like I'm missing something ... ah well, there's plenty to announce anyway! As always, if you're having problems with Dreamwidth, Support can help you; for notices of site problems and downtime, check the Twitter status page; if you've got an idea to make the site better, you can make a suggestion; if you just want to come and hang out, join us in irc at irc.dwscoalition.org, channel #dw. (#dw: it's not an irc channel, it's an adventure.)
See you next week for our next update! (It may be delayed even more than it has been the past few weeks due to travel.)
Big bunch of stuff this week behind the cut!
1. Development
Sunday night's code push brought us a whole whackload (that's a scientific term) of new features and bugfixes. You can see the whole list of last week's development efforts at the weekly code tour!
Meanwhile, some of the new stuff includes:
2. Comment screening
A frequently-requested change: we've updated the comment screening process so that a). an account owner's or community maintainer's comments will obey the screening setting for the entry itself (so no more of your comments being posted unscreened when you've chosen to screen all comments) and b). replying to a comment will no longer automatically unscreen it. This is one of our more frequently requested changes, so have fun!
3. Popular Subscriptions
Paid accounts can now use the Popular Subscriptions page, to see who's most read by the people you read. Go forth and find new content! (And thank
yvi for coding it.)4. Inbox changes
We've added two new filters to the Inbox: poll responses (for those who subscribe to notifications of poll answers) and unread items (to find those notifications lurking in the depths of your inbox that you can't find anywhere else).
5. Crossposting
We've added an option for the crossposter to re-enter your password every time you want to crosspost, rather than saving the password with us. To use this, set your crosspost settings. When you edit your defined crosspost account or create a new one, you'll have an option to save your password; leaving it unchecked will prompt you for your password every time you crosspost.
5. Other bugfixes
* The Gradation Vertical sitescheme has had a bunch of tweaks for usability, so things that were displaying improperly should now be fixed. If you notice anything that still doesn't look right, report it to Support or drop a comment to the developer who's working on it, and we'll get it fixed right up.
* The problem with custom crosspost footers over 256 characters being truncated after a certain amount of time is fixed now. (And was totally my fault. Mea culpa.)
* The problem with crossposts failing when there were certain HTML entities in cut text has been fixed.
* The problem with RSS feeds displaying certain characters incorrectly is now fixed.
6. Known Problems
Support would like us to let people know that if you're having problems seeing long entries in the Tropospherical site schemes, you should add ?usescheme=celerity or ?style=light to the end of the URL and see if that fixes it. If you still have problems after that, contact Support and they'll do what they can to help you! (It's a problem with how Firefox displays certain CSS, and the Firefox people say that they should have it fixed in the next major release.)
In general, if you spot anything that isn't working right, or that you think might be a bug, we want to hear about it! Unless it's listed in the Current Issues FAQ category, don't assume we know about it. If there's something that doesn't work for you, please please please report it to Support so we can look into it and fix it as soon as possible.
7. Us in Person
mark will be in Sydney, Australia for a few days later on in the week, and then both of us will be in Wellington, NZ next week for a conference, so if anybody wants to get together for a Dreamwidth meetup, keep an eye on mark.*
Hm, I still feel like I'm missing something ... ah well, there's plenty to announce anyway! As always, if you're having problems with Dreamwidth, Support can help you; for notices of site problems and downtime, check the Twitter status page; if you've got an idea to make the site better, you can make a suggestion; if you just want to come and hang out, join us in irc at irc.dwscoalition.org, channel #dw. (#dw: it's not an irc channel, it's an adventure.)
See you next week for our next update! (It may be delayed even more than it has been the past few weeks due to travel.)