Difference between revisions of "Support FAQ"

Revision as of 10:10, 27 March 2011

This page contains frequently identified issues, questions, and so forth with regards to support, relevant to you, the support volunteer.

Who can do Support?

Anyone who feels like it can volunteer their time and expertise to Support. See the Support guide and Support process.

Feed rename requests

Example: "Could you rename the sample_feed feed to samples_feed?"

Typically, you can just ignore these requests. Someone with the appropriate privileges will handle it.

If you'd like, you can look up what the new feed name should be, if the user didn't provide it. If the new feed name is already in use, you should let the user know that the new feed name is in use, and they should supply a new name.

As an aside, please do not create a new feed. MrsJ can edit a feed URL/name, but cannot merge two feeds into one at this time.

-- Source.

Feed source changes

Example: "The source feed's URL has changed. Could you change the DW feed's URL, too?"

You should treat these the same as rename requests.

Closing a support request

Requests are typically closed when someone with request-closing privs has the time to close them. (Currently, this is denise.)

Answered requests may remain open for a brief period of time for two reasons:

1. denise hasn't had the time to go 'round and close them.
2. We want to give the user ample time to respond, in case they're still having an issue.

-- Source.

Answers that refer to a Bugzilla bug

If your answer refers to a bug, please add an internal comment that links to the bug in Bugzilla.

-- Source.

Spaaaaam! In the dungeon!

Thought you should know!

If you see spam on the board, just leave it. It will be handled by someone with the appropriate privs.

If you have the movetouch priv, you must move the "request" to Webmaster, and dequeue it. If you're unsure as to whether the request is actually spam, just move it to Peterstein. Someone will suss it out.

-- Source.

Mass-deletion of entries

This is covered in the Dreamwidth FAQ, actually.

Dreamwidth does not support mass-entry deletion within itself. There are third-party tools that might be able to do this, but it's not recommended.

DW doesn't have or want the functionality for two main reasons:

1. It is way too easy to slip and delete more than one intended to.
2. Not having that is one more obstacle, in case one's journal is hijacked.

If you recommend that they seek out a third-party client, you must make sure to note that DW takes no responsibility for third-party clients.

-- Source.