dw_support_training | Recent Entries

Hai everybody:

In order to better keep track of issues for which we have multiple requests, we've been tagging them in the request summary. Kat has cleared anyone with the ability to tag requests, and modify the summaries as needed to make them closer match the actual issue.

Currently, we have a few tags defined.
[PBE] - Post By Email issues
[CNI-LJ] - Comments not importing from Livejournal.
[CNI-IJ] - Comments not importing from InsaneJournal.
[IJ] - Issues with importing from InsaneJournal which are not limited to just comments.
[Fix In Progress] - This is an Identified Bug and has made its way to someone who is working on a patch. This tag is admin-only at this point.
[CRI] - Cannot Rename Icons. For the record, this is being investigated by

purplecat

Tag are created on an ad-hoc basis to deal with issues as they crop up. These are just the ones in active use right now.

~~Drew

pauamma

So there's a bunch of requests, going back to at least December 2018 and maybe at least September 2018, all reporting that some buttons on the DW inbox have no effect when clicked. The buttons concerned are "Delete Selected", "Mark Read", "Mark Unread", and perhaps "Delete All". The requests themselves are:

https://www.dreamwidth.org/support/see_request?id=40012
https://www.dreamwidth.org/support/see_request?id=39872
https://www.dreamwidth.org/support/see_request?id=39869
https://www.dreamwidth.org/support/see_request?id=39827
https://www.dreamwidth.org/support/see_request?id=39796
https://www.dreamwidth.org/support/see_request?id=39626 (which has a copypasta of the Chrome console error log that may be a clue)
https://www.dreamwidth.org/support/see_request?id=39566
https://www.dreamwidth.org/support/see_request?id=39201
https://www.dreamwidth.org/support/see_request?id=38992 (but it is unclear to me whether this is the same problem)

However, the "Delete Selected" button works for me. Any opinion? Could it be add-ons interfering with Javascript? (The copypasta seems to me to be hinting at a code error in some Javascript library inherited from 6Apart instead, but I'm not a Javascript kinda crab.)

ninetydegrees

We have two requests which mention specific error messages. Could a dev or experienced volunteer have a look at them?

*https://www.dreamwidth.org/support/see_request?id=36083

Failure running job: no element found at line 1968, column 0, byte 178954 at /home/dw/current/extlib/lib/perl5/x86_64-linux-gnu-thread-multi/XML/Parser.pm line 187.

*https://www.dreamwidth.org/support/see_request?id=36145

Unable to load FOAF data

highlander_ii

We have 4 requests related to not being able to post via Chrome:

http://www.dreamwidth.org/support/see_request?id=29562
http://www.dreamwidth.org/support/see_request?id=29621
http://www.dreamwidth.org/support/see_request?id=29589
http://www.dreamwidth.org/support/see_request?id=29574

I've tested both the beta entry form and the default form and have had no issues posting. My add-ons are LJJuggler, Adblock Plus, Too Many Tabs and SexyUndo Closed Tabs. (There might be others, but those are the ones I can see right now. *g*)

ninetydegrees

There are two requests related to entries not being posted out of order:

http://www.dreamwidth.org/support/see_request?id=29183
http://www.dreamwidth.org/support/see_request?id=29129 (this one is a week old)

How to solve this?

Also http://www.dreamwidth.org/support/see_request?id=29134, which might be related as well.

(Note: edited bc of new info)

ninetydegrees

Hi! Can someone explain what's going with LJ comment imports? I see Support answers refer to a 4-year-old maintenance post and I don't understand if the issue has reoccurred or has been going on for years, and really what this means for users.

(Sorry for the IRC duplicate but I'm trying to get better at posting here too.)

jennifer

Kat asked me to post an FYI here about a support request I just answered about blogspot.com OpenID issues, in case anyone else writes in asking about it. The short version is that it's Google's problem, not ours.

The support request is here: http://www.dreamwidth.org/support/see_request?id=26619

The Google result that came up when I searched on "Whoops, that's an error" is here: https://productforums.google.com/forum/#!topic/blogger/nySh9Dp0qI4

misskat

Mark has posted something in dw-dev that I recommend you read.

Since it sounds like it'll be a bit before we are able to start using the new tracking system (likely Github Issues or GHI), I'm looking into a temporary solution for Support that doesn't involve keywords in ICs (messy and unreliable) or lists in personal journals (not a good common resource). One of the other volunteers suggested creating an entry in this community, and then tracking bugs in comments. That way, nothing will get lost, and we'll have a common resource. I'm going to think on it tonight, and I'll post here once I've made a final decision. I welcome any commentary!

Thanks, folks!

misskat

Bugzilla is going to be down for a while due to some extenuating circumstances. The team is working on getting things back up and running, but it's going to take some time.

Until further notice, please use the following checklist for recording and documenting a bug which is reported/discovered via Support:

In an internal comment:
- SUBJECT
  - Descriptive but concise title
- DESCRIPTION
  - This should contain a slightly longer description of the bug, as well as a paraphrased version of any troubleshooting. If you suspect you know why the bug is doing the thing, put that in here too. Steps to reproduce are also appreciated.
- BUGREPORT
  - Include those words (capitalized or not) somewhere in the bug report. This will provide an easy keyword to search for when it's time to move these from internal comments into the bug tracking system.

The purpose of this special, dedicated internal comment is to generate an email notification of the IC which can be used as a temporary bug storage place until we have our real bug tracking system in place again. If you have any additional comments to make on these temp bug reports, go ahead and just comment on the request. Include the phrase BUGREPORT in your IC so it'll get picked up in a search.

Does that all make sense? I am welcome to suggestions for a different process if you think of something better/more efficient. I haven't had enough coffee yet this morning. :)

Thanks for all you do, folks.

misskat

Everything should be working fine now, per Squeaky.

misskat

Some users are getting xpost and import errors with InsaneJournal. I'm working with Squeaky to resolve the issue. We've already provided them with a patch, but it didn't fix the issue entirely. I updated the BBB to reflect this information (well, not the bit about the patch), so hopefully we won't get many reqs about it.

On an unrelated note: I am going to be out of the country for apprx 2 weeks. Internet may be spotty during this time, but I WILL be checking on things!

You all are amazing, and I appreciate all the hard work you've done this year. Without you, this machine would be less oiled! Merry Christmas, Happy (belated) Hanukkah, Glorious Festivus, and all my best to you and yours for a blessed New Year. :)

Dreamwidth Support Training

Bringing spr0tlings up right since 2009

Recent Entries

Sticky: Support request summaries and tagging.

RFD: DW inbox buttons inactive for a number of people?

Importer Issues

Chrome entry-posting issues

Trouble w/ Entries

Problem with comment imports?

blogspot OpenID problems

Update on Bugzilla

Bugzilla

InsaneJournal errors (importing and xposting) redux

InsaneJournal errors (importing and xposting)

Profile

June 2019

Links

Syndicate

Most Popular Tags

Page Summary

Active Entries

Style Credit

Expand Cut Tags