Note for Dreamhackers and sites using Dreamwidth code

[foxfirefey]

We've just checked in a code change that moves to a new data version. You can read instructions on how to update your database.

This change has been made to make icon renaming more efficient, so we can keep that feature.

MogilFS changes

[fu]

Hmm, it looks like there's been a lot of changes going on in the mogile repository right now -- after running an update, I get a warning that I can't start mogilefsd because I'm on the wrong database schema.

Heads-up in case anyone runs into the same thing -- I've rolled back to r1459 of mogile for now.

Styles and "standouts" (and bears, oh my...)

[tyggerjai]

I'm working on a bug in the preview code, and trying to add a "standout" box to preview/entry.bml, which I presume is a markup-vs-content approach to "This information is important and should standout, and we'll let the client decide whether that's bold or flashing red". For most pages, it looks like that would be trivial - there's a lot of "$ret .= <?standout", etc. However, preview/entry.bml seems to have 2 different methods of building pages depending on the styles. One uses the "$ret .= ", and that's fine. The other, however, seems to be a lot more dependent on LJ::S2 code, and that's the bit I'm stuck on.

I have the core2.s2 file now checking whether it's a preview page (thanks to exor674 :), and adding the text I need, but I'm not sure what the appropriate way is to make it "standout" at that level. Clearly for the $ret method, some kind of parsing happens before the final rendering, whereas the s2 in a sense is the final rendering (as far as I can tell :). So can anyone give me a clue as to whether core2.s2 is even the right place to be building the standout, or whether I should add it to $p in preview/entry.bml somewhere, so I can use the ?standout syntax, maybe.

And for the rest of you, hi, I'm Jai :)

jai.
.