March 2nd - March 21st (2 of 4)

[musyc]

Morning all! (For values of morning that apply to your current time - make any substitutions or exchanges as necessary. Me, I exchanged a coconut-filled chocolate for raspberry today. Om nom nom.)

This installment of the code tour has a FAQload of FAQbugs. And I apologize in advance if any typos slip in, as my cat decided to "help" by falling asleep on my number keypad. I'm sure many of you can sympathize.



Bug 4757: For the Bold: new themes
Category: Style System
Patch by: ninetyd
Description: New themes! Lots of shiny new themes to frolic with.

Bug 4790: Need FAQ about JournalFen crossposting issues
Category: User documentation
Patch by: Naomi Hemsley
Description: Crossposting to JournalFen has some issues due to code differences. Explanations are good, and now they exist.

Bug 4776: New FAQ : Why are people who comment on my journal being shown CAPTCHAs?
Category: User documentation
Patch by: swaldman
Description: Why CAPTCHAs? And what are CAPTCHAs? And how many of them fit in a liferaft? This FAQ explains the first question. The rest are left to keep me awake at night.

Bug 4774: FAQ #241 (invalid pswd error): mention secure login page?
Category: User documentation
Patch by: denise
Description: Another wild FAQ appears! With some explanations on why your login might not be working as expected. (It was on a coffee break with me, whoops.)

Bug 4762: tags documentation does not mention case-smashing
Category: User documentation
Patch by: denise
Description: Denise smash tags! ... Wait, wrong movie. Tags can only be lower-case on Dreamwidth. Now the docs tell you that instead of letting you guess.

Bug 3461: Improve filter error message
Category: Misc UI/Frontend
Suggested by: msilverstar
Patch by: denise
Description: o/~ Valderi, Valdera, four-oh-fouuuuuuuuur o/~ Non-existent reading filters now come with a handy 404 explanation!

Bug 4754: FAQ for Markdown support
Category: User documentation
Patch by: denise
Description: Markdown is a kicky little formatting method. And now you can write your posts in it! Let this FAQ teach you how.

Bug 4621: FAQ #178 on converting personal to community could be a little clearer
Category: User documentation
Patch by: isabeau
Description: Decided that awesome new journal you just registered could be even more awesome as a community? Let this FAQ explain how to do that!

Bug 4617: Sticky entry FAQ should give community instructions
Category: User documentation
Patch by: denise
Description: Users can have sticky entries, and so can communities. Sticky, sticky, sticky entries.

Bug 4791: FAQ #4 : features missing from the list
Category: User documentation
Patch by: denise
Description: o/~ What's this? What's this? There's features everywhere! What's this? What's this? There's details in the air! o/~ Or on this FAQ page, to tell you about those shiny features.

Bug 4792: FAQ #227 don't mention paid-only module(s)
Category: User documentation
Patch by: denise
Description: Loads of modules exist on DW, but a couple of them are only available if your account is paid. FAQliciousness to explain those modules.

Bug 4462: Edit journal privacy doesn't touch community entries or comments
Category: User documentation
Patch by: denise
Description: There's a lovely tool for paid users that lets you edit the privacy level of all your journal entries at once, buuuuuuuuut it doesn't work on community posts you may have made. Now this FAQ tells you so.

Bug 3758: FAQ #99/FAQ#185 unclear on security levels
Category: User documentation
Patch by: chemicallace
Description: Information about security levels was unclear. The information got a good scrubbing up and talking to, and now it's better.

Bug 3898: new faq and/or expand faq61 to give info on privacy-related concerns re: ip addresses
Category: User documentation
Patch by: denise
Description: FAQs on how IP addresses get logged, right this way!

Bug 4348: need faq for "view entries by security level"
Category: User documentation
Patch by: denise
Description: FANCY. Learn something new every day. Paid accounts can view their entries by security level (public, private, access list, custom filter). This might save me a lot of time with tagging my private note-to-self entries. The more you know!

Bug 4909: new faqcats slow to show on /support/faq
Category: Frontend
Patch by: fu
Description: Configs, bmls, and strings, oh my! Stuff about support boards, inserted here.

Bug 4354: streamline faq155 (what html is allowed in entries) and split in two for commonly used / not-commonly used tags
Category: User documentation
Patch by: rb
Description: HTML. There's all kinds of things there. It can be misused in glorious ways. Now there's better explanations on just what HTML you can use in your entries.

Bug 4916: new faqcat for import/xpost
Category: User documentation
Patch by: denise
Description: New faqcats to love and stroke and squeeze and name George.

Bug 4903: comment thread expansion not working on nested expands
Category: Journal contents
Patch by: fu
Description: When you have a really long comment thread, you can expand it. And sometimes little subthreads in there don't expand, so you try to expand them. Before, the goggles the threads did nothing. Now they expand like they're supposed to.

Bug 4904: poll view answers not working
Category: Misc UI/Frontend
Patch by: fu
Description: Sometimes you want to look at the answers on a poll. There was a problem that meant you couldn't. Now you can. It's like magic!

Bug 1175: crossposted entries can't be edited by a client
Category: Crossposter
Patch by: exor674
Description: Clients. Wonderful little things, when they work as you expect. When they don't, like with crossposted entries, the behind-scenes coding team, superheroes that they are, put some code together and make clients dance.

Bug 125: Viewing protected content while logged out should redirect to login.bml
Category: Misc UI/Frontend
Patch by: allen
Description: If you try to look at a locked/filtered entry and you don't have access to it, you should get sent to a page that lets you log in.

Bug 4470: install test-related CPAN modules on hack.dreamwidth.net
Category: Testing
Patch by: sophie
Description: I have no idea what any of this means. I flailed in utter confusion took five or six breaks asked IRC. IRC sayeth:
*ok, so, 4470 is a request to install some Perl packages that are useful for testing on the dreamhack server
*it's not really a code change at all
*Devel::Cover is a tool that helps you measure how well your code is covered by tests
*Devel::NYTProf is a profiler -- it's a tool that helps you measure how fast your code runs
*and Test::Deep is a testing tool that makes it easy to test/examine complicated data structures

.......... So there you go. That's what it does. *wise nod*

Bug 4655: Add a CONTRIBUTING file
Category: Unknown
Patch by: denise
Description: There's now a contributing file! It's ... well. Basically a file that gives you information on how to contribute. Fancy, wot?

Bug 4886: FAQ#139 needs to be updated
Category: User documentation
Patch by: denise
Description: Another FAQ update! They're everywhere. Like dandelions in spring.

Bug 4915: Missing /UL in account links block
Category: Site Layout/Navigation
Patch by: ninetyd
Description: One teeny tiny bit of code went missing. It was found and shepherded back to where it belongs.

Bug 4680: (update page beta) label settings gear icon
Category: Misc UI/Frontend
Patch by: fu
Description: On the shiny new Iloveitsomuch update page, there is a little gear icon that lets you muck around with the settings. Loads of people had trouble figuring out what that little gear icon was. (Looks kind of like a flower, doesn't it?) So a label got smooshed onto the icon to tell you what it did.

Bug 4534: investigate "training missions" for dev work
Category: Wiki documentation
Patch by: denise
Description: Your mission, should you choose to--OH LIKE YOU DIDN'T KNOW THAT WOULD HAPPEN. Anyhow. Information on training/practice missions got added to the DW wiki for people who'd like to learn code.

Bug 820: conform to WAI-ARIA accessibility guidelines throughout the site
Category: Misc UI/Frontend
Patch by: deborah
Description: Accessibility! There's so much of it here on DW. Fantastic, darlings, just fantastic. And this bug was all about adding more of it. Look at that tiiiiiiiiiiny low number. One of the very early bugs, finally closed. Dance of joy!

Bug 1798: Add one-column options to official styles
Category: Style System
Patch by: cesy
Description: One column? Two column? Threeeeeeeee columns? (Three columns! *lightning flash* AH HA HA HA.) All official styles need to have the ability to have any of those column options, but some were lacking in the one-column field. They've been poked and prodded and mostly fixed.

Please exit the vehicle and retrieve your belongings at the gate. This installment of the Great Big Code Tour is complete. My first, all done. XD

Comments

[cesy]

Haha, a bug I worked on back in 2009 finally closed. Hooray for breaking bugs into smaller bits so different newbies can pick up smaller chunks.

[momijizukamori]

CODE TOUR \o/

and mmmm look at all those docs

[boundbooks]

HEY, I know the person making this post!

/waves from the crowd

:P

[msilverstar]

I love it when my suggestions are useful!

[azurelunatic]

Hooray!

[jewelfox]

Skittlish Dreams still doesn't have a one-column option. >_>;

[ninetydegrees]

Yep! There's a separate bug for it now. If that's doable someone'll get to it eventually. :)

[jewelfox]

Where is this bug at, and how would one go about "getting to it?"

[ninetydegrees]

Here's the bug: http://bugs.dwscoalition.org/show_bug.cgi?id=4920

I'm not sure what you're asking but if you meant getting started as a dev here's a wiki article which might help you: http://wiki.dwscoalition.org/wiki/index.php/Dev_Getting_Started. Depending on which OS you're on and how experienced you are, there might be other useful guides in the Getting Started category. The bug itself probably involves S2 and CSS editing.

I found a weird thing

[torrilin]

Well, several really.

I did not know about post by email. Got it set up and have done some experimental posts. I seem to get different results when my PIN is in the subject line vs the first line of the email post's body. Both will post. But the subject line PIN will follow my post-security: private setting, and a body PIN won't. I'm not sure if this difference is intended or not. From the documentation email it looks like not?

Since I was doing test email posts anyway, I tried to use the new !markdown trick. PIN in the body of the post means no Markdown posting. PIN in the subject meant it worked. Sort of. The FAQ doesn't make it clear exactly which Markdown to HTML script is being used and I'm seeing possibly odd stuff with strong and em tags. Maybe other stuff too, I haven't gone nuts trying to feed the poor thing edge cases. Yet.

Even with the weird I found these are really cool changes. It makes posting from my iThing really doable.

Re: I found a weird thing

[denise]

Huh. Those are weird. The post-by-email (not comment-by-email) feature was inherited from LJ, and it's entirely possible there's some bug that was never reported, or that the changes we made introduced some new bugs. Open up a support request with the steps you take to reproduce that so the bug can be filed?