Difference between revisions of "Support FAQ"
m (→Who can do Support?) |
(→Answers that refer to a Bugzilla bug: replaced Bugzilla with GHI) |
||
| (7 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
This page contains frequently identified issues, questions, and so forth with regards to support, relevant to you, the support volunteer. | This page contains frequently identified issues, questions, and so forth with regards to support, relevant to you, the support volunteer. | ||
| + | |||
| + | == What is Support? == | ||
| + | |||
| + | Technical support for users of the Dreamwidth.org site is partially crowdsourced. This includes general questions, and some technical support and customer service. (Some technical support and customer service is done by Dreamwidth staff.) Any registered Dreamwidth user can contribute answers on the Support board. All answers are subject to the approval of a trained senior volunteer before they are sent to the user. You can read more about the full [[Support process]]. | ||
== Who can do Support? == | == Who can do Support? == | ||
| Line 5: | Line 9: | ||
Anyone who feels like it can volunteer their time and expertise to Support. See the [[Support guide]] and [[Support process]]. | Anyone who feels like it can volunteer their time and expertise to Support. See the [[Support guide]] and [[Support process]]. | ||
| − | == Feed rename requests == | + | == Things needing special powers== |
| + | A lot of requests are informational, and anyone who knows the answer can give an answer, but some support requests need special powers to actually carry out. (See also: [[What Goes Where]]). | ||
| + | |||
| + | === Feed rename requests === | ||
Example: "Could you rename the sample_feed feed to samples_feed?" | Example: "Could you rename the sample_feed feed to samples_feed?" | ||
| Line 11: | Line 18: | ||
Typically, you can just ignore these requests. Someone with the appropriate [[Privileges|privileges]] will handle it. | Typically, you can just ignore these requests. Someone with the appropriate [[Privileges|privileges]] will handle it. | ||
| − | If | + | If the user is complaining about the feed not working, take a look and see if the feed URL is still valid. If it is not valid, please look up the new one and leave is as an IC to the request. |
| − | As an aside, please do not create a new feed | + | As an aside, please do not create a new feed. |
-- [http://dw-support-training.dreamwidth.org/13100.html Source]. | -- [http://dw-support-training.dreamwidth.org/13100.html Source]. | ||
| − | == Feed source changes == | + | === Feed source changes === |
Example: "The source feed's URL has changed. Could you change the DW feed's URL, too?" | Example: "The source feed's URL has changed. Could you change the DW feed's URL, too?" | ||
| Line 23: | Line 30: | ||
You should treat these the same as rename requests. | You should treat these the same as rename requests. | ||
| − | + | If the user is complaining about the feed not working, take a look and see if the feed URL is still valid. If it is not valid, please look up the new one and leave is as an IC to the request. | |
| − | Requests are typically closed when someone with request-closing privs has the time to close them. (Currently, this is <dwstaff>denise</dwstaff>.) | + | === Closing a support request === |
| + | |||
| + | Requests are typically closed when someone with request-closing privs has the time to close them. (Currently, this is <dwstaff>denise</dwstaff>, Kat, Dom, and Chemla.) | ||
Answered requests may remain open for a brief period of time for two reasons: | Answered requests may remain open for a brief period of time for two reasons: | ||
| − | # | + | # D, Kat, Dom or Chemla hasn't had the time to go 'round and close them. |
# We want to give the user ample time to respond, in case they're still having an issue. | # We want to give the user ample time to respond, in case they're still having an issue. | ||
-- [http://dw-support-training.dreamwidth.org/17216.html Source]. | -- [http://dw-support-training.dreamwidth.org/17216.html Source]. | ||
| − | = | + | === Spaaaaam! In the dungeon! === |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | == Spaaaaam! In the dungeon! == | + | |
Thought you should know! | Thought you should know! | ||
| Line 46: | Line 49: | ||
If you see spam on the board, just leave it. It will be handled by someone with the appropriate privs. | 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 | + | If you have the '''movetouch''' priv, you must move the "request" to Peterstein. If you're unsure as to whether the request is actually spam, just move it to Peterstein. Someone will suss it out. |
-- [http://dw-support-training.dreamwidth.org/12489.html Source]. | -- [http://dw-support-training.dreamwidth.org/12489.html Source]. | ||
| + | |||
| + | === Changing the Birthdate Entered at Registration === | ||
| + | |||
| + | Whether or not an account has access to posts and communities flagged as "adult content" is determined by ''the initial birthdate entered at registration time'', and not any value the user's birthdate is subsequently changed to. | ||
| + | |||
| + | Requests to change the initial birthdate require special privs. If you have the movetouch priv, dump the request into Accounts. | ||
| + | |||
| + | == Answers that refer to a bug == | ||
| + | |||
| + | If your answer refers to a bug, please add an internal comment that links to the issue in [[Github Issues]]. | ||
| + | |||
| + | -- [http://dw-support-training.dreamwidth.org/12885.html Source]. | ||
== Mass-deletion of entries == | == Mass-deletion of entries == | ||
| Line 64: | Line 79: | ||
-- [http://www.dreamwidth.org/support/faqbrowse?faqid=210 Source]. | -- [http://www.dreamwidth.org/support/faqbrowse?faqid=210 Source]. | ||
| + | |||
| + | == Deleted Users == | ||
| + | |||
| + | Support requests from deleted accounts should still be answered as any other request. The user can still undelete their account; in fact, they may be waiting on the outcome of the request to decide whether or not they'd like to do so. | ||
[[Category: Support]] | [[Category: Support]] | ||
Latest revision as of 13:10, 1 August 2014
This page contains frequently identified issues, questions, and so forth with regards to support, relevant to you, the support volunteer.
Contents
What is Support?
Technical support for users of the Dreamwidth.org site is partially crowdsourced. This includes general questions, and some technical support and customer service. (Some technical support and customer service is done by Dreamwidth staff.) Any registered Dreamwidth user can contribute answers on the Support board. All answers are subject to the approval of a trained senior volunteer before they are sent to the user. You can read more about the full Support process.
Who can do Support?
Anyone who feels like it can volunteer their time and expertise to Support. See the Support guide and Support process.
Things needing special powers
A lot of requests are informational, and anyone who knows the answer can give an answer, but some support requests need special powers to actually carry out. (See also: What Goes Where).
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 the user is complaining about the feed not working, take a look and see if the feed URL is still valid. If it is not valid, please look up the new one and leave is as an IC to the request.
As an aside, please do not create a new feed.
-- 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.
If the user is complaining about the feed not working, take a look and see if the feed URL is still valid. If it is not valid, please look up the new one and leave is as an IC to the request.
Closing a support request
Requests are typically closed when someone with request-closing privs has the time to close them. (Currently, this is ![[info]](http://wiki.dreamwidth.net/wiki/extensions/LJ/images//dw/staff.png){kind=small}
denise, Kat, Dom, and Chemla.)
Answered requests may remain open for a brief period of time for two reasons:
- D, Kat, Dom or Chemla hasn't had the time to go 'round and close them.
- We want to give the user ample time to respond, in case they're still having an issue.
-- 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 Peterstein. If you're unsure as to whether the request is actually spam, just move it to Peterstein. Someone will suss it out.
-- Source.
Changing the Birthdate Entered at Registration
Whether or not an account has access to posts and communities flagged as "adult content" is determined by the initial birthdate entered at registration time, and not any value the user's birthdate is subsequently changed to.
Requests to change the initial birthdate require special privs. If you have the movetouch priv, dump the request into Accounts.
Answers that refer to a bug
If your answer refers to a bug, please add an internal comment that links to the issue in Github Issues.
-- 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:
- It is way too easy to slip and delete more than one intended to.
- 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.
Deleted Users
Support requests from deleted accounts should still be answered as any other request. The user can still undelete their account; in fact, they may be waiting on the outcome of the request to decide whether or not they'd like to do so.
