Code tour, 11/10-11/16

[denise]

We're overdue for a commit run (there are a bunch of patches waiting for review & commit), so it looks like we had a slow week even though there was tons of work being done. Most of what people were working on this week involved major ongoing projects, which is another reason why there are only a few resolved bugs (the people who would be reviewing/committing/hacking on the little bugs were working on bigger things for most of the week).

Still, we resolved 12 bugs FIXED this week, including two new themes and an assortment of bugfixes we hope you'll find useful.



Bug 2103: new default layout
Category: User defaults
Config change by: mark
Description: This changes the default theme for new accounts to Skittlish Blue, chosen by poll last week in News.

Bug 2097: Paid communities should not have a Network link
Category: Bugfix
Patch by: ninetydegrees
Description: The Network link, which shows for paid users, doesn't function for communities. This patch removes it from the links for paid communities.

Bug 2091: Community importer fails to import certain entries
Category: Bugfix
Patch by: mark
Description: We actually do have a community importer, but it's only for use in certain cases (mass-migration of a community that's talked to us about importing their data), because of the amount of work we have to do to map usernames. There was a bug where entries weren't being imported properly; this fixes it.

Bug 2088: htdocs/latest.bml doesn't respect preformatted option
Category: Bugfix
Patch by: wyntarvox
Description: The Latest Posts feed wasn't properly recognizing when a post was preformatted; this fixes that.

Bug 2081: fix t/console-suspend.t
Category: Bugfix
Patch by: yvi
Description: This fixes one of our unit tests, which was failing due to some of the changes we'd made to how usernames are formatted. (I think.)

Bug 2078: Themes: Dark Forest and Forest Green (Transmogrified)
Category: Styles
Patch by: ninetydegrees, layout by dancing_serpent
Description: Two new themes for Transmogrified, one green-and-black, one green-and-tan.

Bug 2053: some views ignore "site" attributes on <user> tags in entry subjects
Category: Bugfix
Patch by: yvi
Description: This fixes a bug where all views except the Entry view weren't properly displaying the site attribute of the <user> tag (thus making things like <user name=xb95 site=livejournal.com> appear as zorkian, not xb95).

Bug 2024: Display number of comments on reply pages that use site schemes
Category: Codemerge
Patch by: LiveJournal
Description: This merges in LJ's new code that will show the number of comments on site-schemed entry pages.

Bug 1970: Negatives: add two-column-left option
Category: Styles
Patch by: ninetydegrees
Description: This adds a two-columns-left option for the Negatives style. (You can select it by going to the Select Style page and picking it down in the bottom area.)

Bug 1781: Add clearing element to Tabula Rasa
Category: Styles
Patch by: afuna with help from branchandroot
Description: This adds a clearing element to the #content-footer block in Tabula Rasa-derived themes for easier CSS wrangling.

Bug 1690: Support for <dc:creator>
Category: RSS
Patch by: afuna
Description: This adds support for the <dc:creator> field many group blogs use to identify the author of an entry, meaning that the syndicated feed account on DW will properly attribute the entry to its poster.

Bug 1450: make ItemRange accept an optional anchor for printing
Category: Styles
Patch by: exor674
Description: This is hardcore backend styles stuff, changing S2 (our style programming language) so that something that was hardcoded is now being passed to the language instead when it's called programmatically. (It's being changed as part of our longterm efforts to get more and more pages into user space so they look like part of your journal.)

Comments

[yvi]

This fixes one of our unit tests, which was failing due to some of the changes we'd made to how usernames are formatted. (I think.)

Nah, not remotely that complicated :) It was just that the success message used to be "info: [user] suspended" and it was changed to "success: [user] suspended".

It wasn't half as difficult to fix a test as I thought ;)