Mark Smith (
mark) wrote in
dw_maintenance2013-07-18 09:11 pm
![[staff profile]](https://www.dreamwidth.org/img/silk/identity/user_staff.png)
![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png)
Code push complete!
...and we're back!
Please let me know of any problems you see. We've got hands on deck ready to pounce any issues and take care of them as quickly as we can.
Thanks for your patience!
Please let me know of any problems you see. We've got hands on deck ready to pounce any issues and take care of them as quickly as we can.
Thanks for your patience!
no subject
no subject
no subject
no subject
Bravo, in any case!
no subject
Glad to hear that things are super speedy lemon squeezy!
no subject
That'll certainly make some things faster, although I wasn't really planning on a noticeable difference. I'll take it, though. Glad it's working nicely for you!
no subject
no subject
And yeah, it's the very worst with livejournals.
no subject
Other than that, looks good for me. You all rock. :D
no subject
Email reply test!
If you get this, it seems to be working (for me anyway).
Edit: Actually, it was broken. But I fixed it, and then all the queued mails went through, so anything you sent should have posted now. Sorry for the trouble, and thanks for letting me know!
no subject
no subject
Standard issue Dreamwidth brainslugs!
no subject
no subject
Testing, testing, one two three!
no subject
no subject
no subject
no subject
That usually means that your internet crapped out while you were trying to load something, yes! If you notice it happening when your internet connection isn't being wonky, or happening regularly, let us know again, though.
no subject
no subject
no subject
no subject
no subject
Huh. I don't think we did anything that chould have affected that; can you ask her to try rebooting her phone and see if the problem clears up? (If not, we'll see if we can find somebody with the same setup and see if they can reproduce.)
Also, is that in site skinned comment pages or journal-styled comment pages, and if journal-styled, a) does it happen in all styles and b) if not, which ones does it happen in?
no subject
no subject
So it's not just you.
no subject
Thank you for any help offered.
no subject
When you say that you're not getting notifications, do you mean that you're not receiving emails but the notification does appear in your inbox, or that the notifications don't appear in your inbox at all?
Unfortunately, if you're not receiving emails but the notification does appear in your inbox, it's probably your mail provider blocking email from us or routing them into your spam folder. Check your spam folder, and make sure the notifications aren't there!
no subject
I can take a screenshot if it would help or link the threads in which I am not receiving notifications from.
no subject
Replies to your entries in communities or your comments in other peoples' journals don't go through the inbox right now (I'm sorry, I forgot to specify that in my first response!) -- that's due to a lot of very boring details about the backend system that runs notifications. (Fortunately, our summer intern is working on changing that.)
I've had a look through our logs and it doesn't look like there are any failures right now -- notifications and emails are being sent out properly. Again, check your spam folder and see if anything's in there, and if there isn't, contact your mail provider and let them know you're missing email that's being sent to you. It's entirely possible that email notifications of replies to entries in communities or comments in other peoples' journals are being spam-filtered while others aren't; the two are generated through two separate systems and the emails they produce are subtly different in ways that can definitely cause mail providers to filter or spam-flag them differently.
Your email provider, unfortunately, is pretty notorious for unilaterally declaring stuff spam and blocking it even before it gets to your account to be put in the spam folder. If they aren't able to help you, you might want to try creating an alternate account for email somewhere else temporarily.
Like I said, our summer intern is working on fixing up a lot of things about the notification and email system that should hopefully make the issue less of a problem, and at the very least will make sure that notifications of replies to community entries and your comments in others' journals will go through the on-site inbox, which will mean you can at least check the on-site inbox for stuff that your email provider ate. Ultimately, though, the problem is that email is a crappy and unreliable protocol sometimes :(
no subject
I'm not getting any notifs in my DW inbox either. I'm in a roleplay community and I just started tagging a thread, and I've got it set to notify me. I am getting my e-mail notifs from Yahoo, though. This only started today. Thanks for any help!
no subject
You won't get notifications in the inbox of replies to your community entries or comments you make in other people's journals -- that notification path doesn't use the inbox. (Unless you explicitly track that particular entry or thread, in which case you will. I know it's confusing -- we have somebody working on clearing that up this summer.)
If that's not what you mean, can you give a bit more detail about what you were expecting?
no subject
no subject
Try this:
1) Go to http://www.dreamwidth.org/manage/settings/?cat=notifications
2) Uncheck the box next to the particular entry you aren't receiving notifications for (on the left-hand side next to the trash can icon, not the right-hand side under the 'email' column)
3) Save
4) Reload page
5) Recheck box
6) Save
See if that fixes the problem?
no subject
Sorry this is such a hassle.
no subject
Can you open a support request? This will need some more research work!
no subject
no subject
no subject
We've had some intermittent issues connecting to LiveJournal today. The xpost worker will retry a few times, but if it still doesn't go through after an hour or two you can always edit the entry, turn off xposting, save, then edit and turn it on again. That will force it to retry the xpost.
no subject