karzilla: a green fist above the word SMASH! (Default)
[staff profile] karzilla2016-09-30 11:02 pm

Code push tomorrow!

We are planning to do a code push around 21 hours from now, at approximately 6pm Pacific time on Saturday, Oct 1.

Here's a partial list of changes that will go live with this push, apart from the usual minor tweaks and bugfixes:


  • Selective Screening, a new feature that lets you screen comments from a particular user.

  • Two new journal layouts with one theme each: Gold Leaf/Elegant Notebook and Venture/Radiant Aqua.

  • Six new themes for Heads Up, and seven new themes for Corinthian.

  • The minimal spacing between line elements in the list of success links on Foundation pages has been restored.

  • Punctuation marks in message subjects will no longer be overescaped.

  • The admin pages for the translation system are now hidden from anonymous viewers, to avoid scaring unsuspecting search engine users away from the site.

  • The text messaging feature has been removed from user profiles.

  • The email notification worker is now less likely to misbehave.


We'll update again to let you know when the code push is in progress!
karzilla: a green fist above the word SMASH! (Default)
[staff profile] karzilla2016-08-07 02:24 pm

Resolved problem with emailed notifications

Sorry for the delayed response on the issue with emailed comment and support notifications not being delivered. We weren't receiving our emailed comment and support notifications saying that there was a problem...

We restarted the relevant software services around 10AM EDT, and the backlog of delayed notifications should have all been sent by now. Thanks for your patience, and extra thanks to everyone who tried to let us know about the problem!
karzilla: a green fist above the word SMASH! (Default)
[staff profile] karzilla2016-06-18 06:51 pm

Code push imminent!

Reminder that I'm going to start working on tonight's code push in the next 30-45 minutes or so. I know you just CAN'T WAIT to use the larger icon filesize for your animated gif talents, so I'm going to start a bit earlier than originally planned, closer to 5:30pm PDT. I'll update this post when we're done!

Update: All done! Comment here if you notice any issues that need our attention.
karzilla: a green fist above the word SMASH! (Default)
[staff profile] karzilla2016-06-17 11:06 am

Code push tomorrow!

We are planning to do a code push around 32[*] hours from now, at approximately 6pm Pacific time on Saturday.

Here's a partial list of changes that will go live with this push, apart from the usual minor tweaks and bugfixes:

  • Icon size limit raised from 40kb to 60kb.

  • Fixed the "hook: enddata returned false" error when uploading multiple icons.

  • Posting DW links on Facebook will now use the "Swirly D" logo for the link image.

  • Added seven new color variants on the popular "Teeny Tinies" mood theme.

  • The user profile page now lists "Other Services" in responsive columns.

  • The user icons page no longer uses "(Default)" in the alt text for every icon.

  • Improved non-ASCII character support in plain text email notifications.


We'll update again to let you know when the code push is in progress!

[*] I had a computer check my math this time, because it was almost wrong again. YAY COMPUTERS.
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
[staff profile] denise2016-04-15 07:11 pm

(no subject)

People getting mail at Gmail are reporting email delays of about an hour. As far as I can figure out, it's because some of our recent changes to our network have wiped out our existing sending reputation with them and made us start building reputation again, and they're refusing all mail on first delivery and making us re-send it. (It's a common spam reduction technique, because spammers don't bother retrying if the first attempt fails.)

There isn't much we can do about it but wait it out until Gmail decides that we're legit senders again, but we'll poke at it and see if there's anything we can do to make the process go faster. (I doubt there will be, though; Gmail is persnickety.) In the meantime, to get comment notification email faster, you can switch your confirmed email to a different provider, or just refresh your on-DW inbox.

EDIT: And people are now letting me know that mail's delayed to other providers, too, which is probably follow-on effects from having to send everything to Gmail at least twice. There isn't a lot we can do about it; I'm sorry about the hassle, folks.
karzilla: a green fist above the word SMASH! (Default)
[staff profile] karzilla2016-04-12 07:20 am

status update 2: electric boogaloo

Some DNS changes were made yesterday that manifested themselves in two troublesome ways:

1. Emailed replies to comments were not being delivered correctly for several hours, but I believe they started showing up again about 8 hours ago. If you have an emailed comment reply that still hasn't been delivered this morning, you may want to try sending it again, and let us know if you are still seeing delays.

2. Some users have been seeing DNS resolution errors when visiting pages on our site. As we come up on 24 hours since the changes were made, these should fade away, but if you do run into this problem, I'm told that refreshing the page while holding down the shift key is a thing to try that might help.

Thanks for hanging in there with us! I am hoping for a quieter day today. :)
karzilla: a green fist above the word SMASH! (Default)
[staff profile] karzilla2016-04-10 05:08 pm

status update

The problem we were having earlier today with failed crossposts was due to a merge conflict in one of the code modules that the crosspost worker uses. I thought the merge conflict was fixed before the changed module was pushed live, but apparently it was not. Alas! Woe! But [personal profile] alierak fixed it a few hours after we were informed of the problem, and crossposts should now be back to normal.

A short while ago, a few of you started reporting a new issue with loading Dreamwidth pages via https. This was not related to the code push, but rather an update to the SSL certificates that we use, which were going to expire soon. One of the intermediate certificates was not in the correct format, and that problem is also now fixed.

If there is anything ELSE not working, do let us know, either by commenting here or opening a support request. Thanks everyone!
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
[staff profile] denise2016-04-09 11:09 pm

(no subject)

We'll be beginning our code push in a few minutes. We're not expecting any downtime. I'll update this entry once we're done for you to report any problems!

EDIT: Code push is complete! Please let us know if you notice any issues.
karzilla: a green fist above the word SMASH! (Default)
[staff profile] karzilla2016-04-08 10:59 am

Code push!

We are planning to do a code push around 35 hours from now, at 8pm Pacific time on Saturday.

Here's a partial list of changes that will go live with this push, apart from the usual minor tweaks and bugfixes:

  • Markdown formatting support for crossposted entries.

  • Embedded content support for Google ngrams, Google calendar, vid.me, and codepen.io.

  • Additional space on the user profile page to list your DeviantArt username.

  • Improved support for browsing the site with HTTPS (fewer mixed content warnings).

  • The legacy mobile reading page has been updated to support filter selection.

  • The suggestions generator has been updated to use Github Issues.

  • Dreamwidth-based sites will now be able to disable anonymous support requests.


We'll update again to let you know when the code push is in progress!
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
[staff profile] denise2016-04-02 06:58 pm

beta Create Entries page having JavaScript load problems for adblock users

The name of one of the JavaScript modules we use on the beta Create Entries page is being flagged by some adblock software and blocked, due to a recent filter update. If your adblock extension uses the EasyList filter subscription, you may notice that the select tags and select filters modules aren't working.

While we figure out the best way to handle this, you can temporarily work around the problem by whitelisting Dreamwidth in your adblock software. (Dreamwidth does not have ads and you will not see ads if you whitelist us -- it's purely to work around the overbroad matching.)

EDIT: The Adblock filter ruleset has been updated to no longer block the thing it was blocking. You now can update your filters and then remove the exception for Dreamwidth if you want!
karzilla: a green fist above the word SMASH! (Default)
[staff profile] karzilla2015-11-22 07:32 pm

code push done!

We're updating the site momentarily! Once the dust settles, please let us know if anything isn't working as expected. I'll edit the entry here if we confirm any issues.

Update, 21:45: All done!
karzilla: a green fist above the word SMASH! (Default)
[staff profile] karzilla2015-11-22 01:03 pm

Code push!

We are planning to do a code push in about six hours, around 5pm Pacific time.

Most of the changes with this push are cleanup and small backend fixes, but we also have a new journal style called "Pattern" with 24 themes for you to choose from, and most excitingly, QuickReply has now been enabled for journal, day, and network views.

We'll update again to let you know when the code push is in progress!
alierak: (Default)
[personal profile] alierak2015-09-23 10:35 am

Whoops!

Please accept our apologies if the site was down or responding slowly while you were trying to use it earlier. Several of our servers rebooted unexpectedly, and I've opened a ticket with the hosting company to ask what's going on. As best I can tell everything's working normally now.
karzilla: a green fist above the word SMASH! (Default)
[staff profile] karzilla2015-08-29 10:00 pm

Code push done!

We're updating the site momentarily! Once the dust settles, please let us know if anything isn't working as expected. I'll edit the entry here if we confirm any issues.

Update, 22:30: We've been done for about 30 minutes and haven't seen any issues, so please go ahead and let us know if you notice any problems!
karzilla: a green fist above the word SMASH! (Default)
[staff profile] karzilla2015-08-29 01:12 pm

Code push!

[staff profile] mark and I are planning to do a code push tonight! We will start working around 7pm Pacific time but since it's my first time, the actual push to the site probably won't happen until closer to 8pm Pacific time.

Here's a partial list of changes that will go live with this push:

  • Rename swaps will accept rename tokens purchased on either account.

  • OpenID community maintainers will be able to edit tags on community entries.

  • Adorable new mood theme called "angelikitten's Big Eyes".

  • Username tag support for lj.rossia.org.

  • Embedded content support for screen.yahoo.com and zippcast.com.

  • Additional space on the user profile page to list your Github username.


And as usual, many tweaks, small bugfixes, and the occasional page source rewrite.

We'll update again to let you know when the code push is in progress!
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
[staff profile] denise2015-06-25 09:20 pm

Code push!

We will be performing tonight's code push in a few minutes. There'll be a brief downtime, but not longer than a few minutes. (Ideally, that is.)

I'll update this entry when we're back, and people can report issues here.

EDIT: New code is live! Please report any issues here.

We're currently having an issue with the image proxy for accessing the site via HTTPS -- images are currently failing to load. We'll have that fixed as soon as we can.
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
[staff profile] denise2015-06-25 01:48 am

Code push Thursday

We are currently planning a code push for about 18 hours from now (the night of Thursday 25 June). We'll probably begin around 9PM Pacific time, although it might be a bit later. As always, we'll update here and our Twitter offsite status when we begin.
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
[staff profile] denise2015-03-16 12:27 am

(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!
fu: Close-up of Fu, bringing a scoop of water to her mouth (Default)
[personal profile] fu2015-03-14 06:12 pm

Code push scheduled in ~24 hours (Sunday/Monday)

FYI -- We're scheduling a code push for Sunday 9PM PDT / Monday 12AM EDT / 4AM GMT.

Should be fun! We'll have another post up when we're about to start.
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
[staff profile] denise2015-02-27 11:30 pm

(no subject)

If you're seeing slow page load times, pages not fully loading, missing icons, 'naked' pages (the text of the page only, without any styling, etc): please shift-refresh your browser, clear your browser cache, and then just hang tight. We're switching CDN providers, so your browser may have cached the wrong copy of things.

If the problem hasn't cleared up by tomorrow, then let us know and we'll look into it further!