Denise (
denise) wrote in
dw_maintenance2015-03-16 12:27 am
![[staff profile]](https://www.dreamwidth.org/img/silk/identity/user_staff.png)
![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png)
(no subject)
Tonight's code push is now complete! As always, please report any issues here.
(We're particularly interested in issues with HTTPS browsing; we're getting closer to ironing out all the bugs, but we know it's still not perfect.)
EDIT: If you're not getting the inline reply form -- if you're getting redirected to another page to comment -- please clear your cache and then restart your browser.
PLEASE NOTE: If you're coming to report an entry in your journal not displaying properly, and there's a <table> in the entry (or you're reporting a problem with your journal displaying properly and there's an entry with a <table> somewhere visible on the page): please check the entry's source and make sure the HTML of the table is constructed properly. We've made a change to our HTML cleaner to be more strict about missing tags and tags that were closed in a different order than they were opened. Most of the display problems people have reported have been because a table in an entry was missing closing </td>/</tr>tags!
(We're particularly interested in issues with HTTPS browsing; we're getting closer to ironing out all the bugs, but we know it's still not perfect.)
EDIT: If you're not getting the inline reply form -- if you're getting redirected to another page to comment -- please clear your cache and then restart your browser.
PLEASE NOTE: If you're coming to report an entry in your journal not displaying properly, and there's a <table> in the entry (or you're reporting a problem with your journal displaying properly and there's an entry with a <table> somewhere visible on the page): please check the entry's source and make sure the HTML of the table is constructed properly. We've made a change to our HTML cleaner to be more strict about missing tags and tags that were closed in a different order than they were opened. Most of the display problems people have reported have been because a table in an entry was missing closing </td>/</tr>tags!
no subject
Try adding that </center> where it belongs and see if that fixes it? If that doesn't work, let us know your browser/device/device OS/browser version.
no subject
I cleared my browser cache, then restarted Chrome, and the post is still not showing up, and even without the sticky, the sidebar on the Reading page hasn't come back yet.
... So basically I think I broke it more than when I started, THIS IS WHY YOU'RE IN CODE DEV AND I'M NOT ;)
Oh right specs. Desktop is Win7/Chrome 41.0 and mobile is iPhone6/Safari w/e comes updated with Apple.
no subject
Okay, since it's not happening on other journal views, that points to it being a problem with the content of a particular entry. Do you have the problem on this page? Alternately, a) do you have any custom CSS added to your journal, and b) do you see a sidebar on, eg, http://wintershepherd.dreamwidth.org/?s2id=255 ?
no subject
The first link you gave me shows fine, sidebar normal. Viewing the journal in the alternate layout style also has the sidebar missing on the reading page, and the sticky is still missing completely.
No additional CSS on this journal, I just tossed a background into the Images tab, didn't bother to code it through the custom CSS box.
eta: let me try setting a different entry as my sticky and see what happens.
eta2: AHA okay, so the Sticky problem is because you guys have implemented the ability to have 5 stickies, and it doesn't remember if you already had one set. I reset it through Account Settings and it's showing up properly now.
Bad news, still no sidebar on the reading page, and when I changed the sticky to another entry without a table, it didn't make any difference.
no subject
...facepalm
OKAY. SORRY, totally my fuckup here: I missed that you were talking about the reading page, not your Recent Entries page. (I am SO SORRY. I've been completely out of it with massive pain issues all week and I'm on my fifth day of double/triple the usual dose of heavy painkillers.)
Looking at the right page: I'm reproducing the problem now, and it's because of this entry: it's missing the closing </td></tr></table>. The poster will have to edit it. In the meantime, you can remove that comm from your reading list or create a reading filter called "Default View" that doesn't have the comm in it, so you can at least see everything else on the reading page.
no subject
Goods news: I am the poster for that entry, that's the mod journal for the game. Lemme go fix that and I'll let you know.
eta: HEY LOOK AT THAT, IT WORKS. I love that I managed to break one of my journals with another of my journals, that's some kind of gold star, right??
no, no it's notThanks for the help, Denise! On a side note, thanks for streamlining the tag arrows thing! It looks great, and still works on mobile, that's awesome.
no subject
I would rather be unconscious, honestly, it would be better than being 70% fine and 30% cognitively impaired and not necessarily being able to tell which part is the 30%. :P I'm just really freaking slow right now. Doesn't help I was supposed to go to sleep a few hours back but the pain's keeping me awake.
Anyway, yeah, people are going to have to be a lot more vigilant about making sure that a) all the tags you open get a corresponding closing tag b) that are closed in the (reverse) order they were opened. Like, if you have a <center<table><tr><td>, you need to close them in the exact order of </td></tr></table></center>. Previously we were more lenient about that and the HTML cleaner would try to detect mismatched tags and close them as necessary, but a few display bugs and pagebreaking tricks were exploiting that, so we had to tighten up the leeway. I know people got used to the cleaner being very permissive about what it would accept without breaking the view, so it'll be a bit of an adjustment, but the change was necessary.
no subject
Try and get some unconscious time as soon as you're able ♥
no subject
And I'm glad we cleared that up! Phew.