Code tour, Mar 2 - Mar 8, 2010

[jd]

This week we had 28 bugs resolved.

Here they are!

Bug 2316: JS missing from /update and /editjournal
Category: Frontend
Patch by: afuna
Description: This fixed an error that was causing the JavaScript drop-down menus on Tropo not to load on certain pages.

Bug 2384: Routing/TT uses headextra ( invalid section ) instead of head.
Category: Backend
Patch by: afuna
Description: Fixed a problem with the way pages using the new templating system generated headers.

Bug 2403: Inaccurate title for the FAQ admin page
Category: Backend tools
Patch by: afuna
Description: Cosmetic tweak to a page used to edit the FAQs.

Bug 2433: Make print_userpic() functions unfixed
Category: Styles
Patch by: afuna
Description: This allows layout authors to override the print_userpic() function.

Bug 2435: Module positioning *too* flexible
Category: Styles
Patch by: afuna
Description: Allows layout authors to restrict modules from appearing in certain places in the customization wizard.

Bug 2232: multilevel tags need span around unlinked terms
Category: Styles
Patch by: branchandroot
Description: Fixed a display issue with nested tags.

Bug 2318: Template Toolkit Plugin for DW stuff
Category: Backend
Patch by: exor674
Description: Added a plugin for more work on the templating system.

Bug 2411: Create POD for DW::Request
Category: Backend
Patch by: exor674
Description: Documentation for a perl module.

Bug 2416: Theme: Marble III (Tranquility III)
Category: Styles
Theme by: dancing_serpent
Patch and Preview by: ninetydegrees
Description: New theme for Tranquility III.

Bug 2417: Inconsistent organization of customize wizard
Category: Styles
Patch by: ninetydegrees
Description: Moved some font options around to be more consistent across all styles.

Bug 2421: Theme: New Ocean (Transmogrified)
Category: Styles
Theme by: dancing_serpent
Patch and Preview by: ninetydegrees
Description: New theme for Transmogrified.

Bug 2142: Date of posts submitted by email
Category: Frontend
Patch by: noodles
Description: From dw_suggestions - this makes email posts use the email's header information for the date, rather than the user's time zone settings as applied to server time.

Bug 680: screenshots for layouts
Category: Styles
Patch by: piranha
Description: This bug has been open since April, since more layouts kept needing more screenshots. It was mostly a catchall for layouts that needed preview images. Nothing's been done on it since November because we've transitioned to requesting preview images on the bug for each particular theme. Thanks to piranha for doing many, many preview screenshots.

Bug 1768: Layout: EasyRead
Category: Styles
Patch by: zvi
Description: This is a new layout that is designed for optimum readability. To quote dreamscapes, it is a one-column style with a wide reading area.

Bug 976: multiple icon uploader doesn't work in IE
Category: Frontend
Patch by: allen
Description: Bug fix for more cross-browser compatibility. It works in IE 7 and 8 now.

Bug 2328: "Don't email comments" setting for suggestions
Category: Frontend
Patch by: yvi
Description: This extends the suggestions form so that suggesters can choose not to be emailed comments to their suggestions at posting time.

Bug 2343: Regular interface for leaving deleted communities/journals
Category: Communities
Patch by: denise
Description: It used to be that the only way to leave a community that had been deleted was by going to the Admin Console. This adds an interface to facilitate the process.

Bug 2348: Spam Reports: mode=view should have link to journal of suspected spammer
Category: Backend tools
Patch by: denise
Description: This fix makes the jobs of the antispam team easier.

Bug 2364: Manage Comments: add edit icon/link
Category: Journal contents
Patch by: denise
Description: You can now edit your comments directly from the manage comments page.

Bug 2379: Show date used on invite codes
Category: Invite codes
Patch by: kareila
Description: When an invite code is used directly (not sent through the site), it will now add the date used to the manage invite codes page.

Bug 2357: Show screening status of collapsed comments
Category: Journal contents
Patch by: ninetydegrees
Description: Once there are over 50 comments to an entry, the comment threads collapse. Previously, you would have to expand the thread to see whether any of its comments were screened; this patch adds an indicator to the comment subject.

Bug 2360: Styles: add CSS class when calendar is horizontal
Category: Styles
Patch by: ninetydegrees
Description: A div has been added so that the calendar can be better styled with CSS when it's horizontal in a layout.

Bug 2398: Move editpics to editicons
Category: Frontend
Patch by: ninetydegrees
Description: A name change from some leftover LJ terminology. On LJ, editpics is where you edit your userpics; and on DW, editicons is where you edit your icons.

Bug 2418: Tranquility III themes.s2: Night Sea theme in the wrong place
Category: Styles
Patch by: ninetydegrees
Description: Properly alphabetizes the Tranquility III themes.

Bug 2426: Funky Circles themes.s2: extra lines
Category: Styles
Patch by: ninetydegrees
Description: Removed the line that makes the layer public, since system styles are always public, and added some blank lines for spacing and readability.

Bug 2125: NNWM styles need screenshots
Category: Styles
Patch by: zarhooie and ninetydegrees
Description: Some of the layouts that were created for NaNoWriMo were never given preview images; they've now been added.

Bug 2051: Five Tabula Rasa color themes
Category: Styles
Patch by: zvi
Description: Like the bug title says, five new themes for Tabula Rasa.

Bug 2422: Fix all POD errors.
Category: Server documentation
Patch by: exor674
Description: Fixes some formatting errors in the system documentation.

Comments

[swaldman]

It was a suggestion I submitted to Blogger back in... oh, about 2002. *they* never implemented it :-)

Maybe one day I'll have the time to actually get involved myself...

[denise]

This is one of the major advantages of our being open source! People can scratch their own itches, whether by suggesting things or by patching them, and it makes things better for everybody. (And it's a major benefit to our "if it doesn't hurt anybody and it doesn't detract from our ideas for the site, why not do it?" philosophy when it comes to moving suggestions over to the bug queue -- one never knows when something that's incidential to us is somebody else's killer app!)

I heard someone say once that a major reason to move to DW wasn't any of our huge major features, but the sheer weight of all the associated little cleanup work and improvement we've been doing. I really had to smile at that, because it's one of the things I enjoy most: doing those little finishing touches that just show attention to detail. My father's a carpenter, and he taught me to pay attention to everything, not just things people will notice first, and I like to think it spills over :)

(Don't mind me, I'm just full of Dreamwidth love today. *g*)

Oh, and I should also add, if you do get a chance to come play with us, we'd love to have you. dw_dev_training is a great place to get help and guidance, and so is the the wiki. And we offer hosted development environments, too, so you don't have to figure out how to install the code yourself!