Code push complete

[mark]

The code push has been completed. Please comment here and let us know of any problems! We will be standing by!

Comments

[sara]

...to take our orders?

[mark]

I suppose, I'm flexible!

[sara]

...now I'm trying to remember the hand signs from charades. But that's mostly because the idea of you charadesing "back-end upgrade" at Dee is cracking me up. Two words, one of them hyphenated, vulgar hand gestures....

("What did your users expect you to do at the conference?" "They wanted system upgrades and interpretive dance.")

[mark]

When Denise and I get together... SHENANIGANS. Dun dun DUUUUUN!

[denise]

But only when nobody's watching.

[xion]

I think that you and Mark charadesing would be hilarity too, just FYI. I, as a DW user want system upgrades and interpretive dance.

Also, it's my belief that the Internet is always watching...Like Cthulhu, only less crazy-making.

Also, wow. Firefox recognized Cthulhu as a word.

[darksilverhawk]

I think the next post should be done entirely through interpretive dance now. Just sayin'.

[arethinn]

THAT'S WHAT YOU THINK.

[sara]

...like I was saying, system upgrades and interpretive dance. *G*

[darkicedragon]

Just wondering, I'm using the Caramel style and it's changed since the push? It normally looks like this, where the headers and the headers of comments are highlighted, but now comments don't have the highlight, like this.

[mark]

Thanks for the heads up! Our styles people will take a look. :)

[darkicedragon]

Thanks! :)

After a bit of poking around, I've found out that comments do have headers if the comment has a subject, if that helps.

[doldonius]

Have you changed the <h?> headers on pages? Entry headers used to be bigger IRRC. Also, they're very hard to click now when viewed with SeaMonkey 2.10 or Firefox 13.0. Their clickable area has become a strip a few pixels high above the text—unless there is no user picture in the entry, then they work normally—as may be seen here.

(As always, sorry for the non-English letters found there. I'm doing my best to force those pathetic 6/7 of the world's population to toe the DW line, but the stubborn bastards still insist on using their ugly parley-voos. Dorks.)

[denise]

Which style and theme is that? (I'm not very good at ID'ing them at a glance!)

[doldonius]

High Contrast White

by zvi for EasyRead

I hope this answers the question. If not, please assist in extracting the required data.

[ninetydegrees]

Hi doldonius,

I'm still trying to see what's causing the clicking issue but here's how you can restore entry headers to their original size: enter the number 2 in the field for 'Size of entry title font' at http://www.dreamwidth.org/customize/options?group=fonts.

I would explain to you why this happened but it's a bit complicated and I'm afraid my explanations wouldn't be clear at all. However I can tell you this is the result of a rare set of circumstances created by the changes I've made to implement a new option and the customizations you've made. I did file a bug about it so that our dev team can see if it's something they might be able to fix, though. My sincere apologies for the inconvenience.

Best,
90d

Edit: I figured out why the link became unclickable and I'm trying to fix it. In the meantime, restoring the size to 2em should make it partially clickable again, as it used to be.

[doldonius]

Thanks a lot, it worked!

[moontothetide]

Whenever I click on an entry with cut text (specifically this entry) the text is merged and smushed together with the comment I'd posted on that entry. It works find if I just expand the cut from the read page, but not if I'm on that post's page. Is there a reason for this?

[momijizukamori]

Try adding or removing tags - the entry doesn't have them in matched pairs, which is making them eat into the page's divs, which makes things get all wonky.

Is it all entries with cuts, or just that one? I'm not seeing it on some cut entries on my reading list, but... low sample size *g*

[moontothetide]

Just this one - all my other entries seem to be reading fine. I've tried adding to four and cutting down to two, but neither is working. Granted, this entry does have a lot more in the way of divs than my others.

[momijizukamori]

Yeah, I'll poke at the code some for you. You're the second person to report this problem (the other was a very div-heavy RP reserve page) so I'm trying to figure out where things went wonky *g*

[moontothetide]

Div heavy RP reserve page and a div heavy CR page. Yeah, sounds like a trend.

♥ Much obliged for the help :-) .

[citymusings]

DW cares about all it's users, including it's RPers. This is awesome. It's not new information, but it's still so fabulous!

[blackmeadows]

No problems here, but thank you for all the hard work you put into keeping this site up and running!

[foxfirefey]

Looks like the new style Wide Open is missing an image that it thinks is here:

http://www.dreamwidth.org/stc/wideopen/koi_page_background.jpg

[ninetydegrees]

Now that you mention it I think none of the theme images have been committed because they're all missing.

[boundbooks]

Yup, was going to comment with this issue! :)

None of the images for Koi on Wide Open are showing up in the preview:

http://www.dreamwidth.org/customize/?layoutid=385364&show=all

[momijizukamori]

Yeah, I think they got missed somehow - I know we had to manually add the preview last night, but I think the rest got missed because it was late and we were tired (I say 'we' but I was mostly an observer)

[mark]

Where is this file from? Or the files. They don't seem to be on the bug.

[exor674]

Yep they are. The zip file at the top never got committed. Reopened and re-flagged commit: http://bugs.dwscoalition.org/show_bug.cgi?id=3669

[mark]

I was never given that bug, heh. I was only pointed at 4429 or something, which is what I commit from. Not sure what 3669 is!

[exor674]

4429 is for a totally different style ( Strata ). The report is for Wide Open. <3

[citymusings]

This is by no means a problem, but you guys are awesome!!!

[kellzilla]

Good to see some life around here after two months of radio silence!

[yvi]

I think I found one issue with the Database style - I use the Green version and on the filters drop-down on my nav-strip, the text colour is the same as the drop-down background colour.

[ninetydegrees]

Yvi, you do mean the "Filter: All Subscriptions" menu, right? Which browser is this in? I'm not seeing it in FF 13.

[yvi]

Yes, that's what I mean. I'm on Chromium 16, and now I suppose it somehow overrides that background color - it's light grey and i think the text is set to a tad darker grey. What color should the background be?

(This is something i can totally live with if it's just my browser being stupid)

[ninetydegrees]

It's supposed to be off-white on black like the rest of the nav strip and the journal:

#lj_controlstrip select {
background-color: #000000;
color: #fefefe;
}

Do you think adding !important could make it apply?

[yvi]

That was still overwritten by

select:not([size]):not([multiple]) option, select[size="0"] option, select[size="1"] option {
background-color: #F7F7F7;
}

Upgrading to version 20 also didn't make it stop doing that.

BUT: I found http://code.google.com/p/chromium-os/issues/detail?id=18865 and it looks like "Workaround is to set the background color for the options within the select" works. So now I have


#lj_controlstrip option {
background-color: #000000 !important;
color: #fefefe !important;
}

and that works :)

[museiclver]

s'cuse my ignorence but what on earth is a code push? Also great job with the new site :)

[denise]

When our developers make changes and they're added to the code that runs the site, this isn't done on dreamwidth itself -- the code is checked into our code repository, but the site itself stays running a "known good" version of the code while development happens and people test the changes, see if there are any problems, etc. At certain points, when we think the development version is at a stable point and (most of) the bugs are out of it, we "push" that code out onto dreamwidth (hence the process known as a "code push") and the live site is updated to the most recent version of the development version. Which is why after every code push, you get shiny new toys to play with. :)

[museiclver]

I see, thanks for that :) I guess you do learn something every day!