October 15th, 2004

  • timwi

Phone post FAQ error

From the phone post FAQ (183):
Press pound (#) when you are done. Do not simply hang up; that will cancel your post.
This is incorrect. If you hang up, what you have recorded will be posted private.

Update: While we're at it:
The users authorized to transcribe your posts [...]
Before starting talking about this, the FAQ should probably mention who these people are, and how to grant or revoke this permission to people. Also, "authorized" needs to be fixed ("authorised") in en_GB.

Update 2: Another thing!
It is not possible to edit a transcript once it has been posted.
This is not true either; It is possible to edit a transcript, it's just not possible for the same user. I know what you meant when you wrote this, but to unversed users it sounds like the first transcription is final and unalterable. :)
  • timwi

Something that always bugged me about the BYB

Hi. I just looked at the BYB and it has something that has been there for years now. It always bugged me; now's my chance to mention this here so you can change it. The sentence in question is:
If you are opening a Support request regarding your journal or friends page not appearing to update properly, please clear your browser cache before opening a request and see if that resolves the problem.
This sounds like you're supposed to clear the browser cache, then open a support request, and then see if that resolves the problem. I propose the following change of wording:
If you are opening a Support request regarding your journal or friends page not appearing to update properly, please clear your browser cache and see if that resolves the problem before opening a request.
animated bunneh icon
  • burr86

FAQ171 (https://www.livejournal.com/support/faq/171.html) | major update

"Which options are currently supported by each public S2 layout?" has been pretty much gutted out and replaced with links to the new s2howto guide, which took about FOUR HOURS to finish.

It's, of course, a living document, and will continue to change as layouts and features are added or altered. While it is located in s2howto, any errors or corrections that need to be made should still come here, rather than howto_userdoc.