suzie cheesecake // sarah? (sarah_mascara) wrote in lj_userdoc,
suzie cheesecake // sarah?
sarah_mascara
lj_userdoc

  • Mood:
  • Music:
This FAQ explains how to edit or delete a post in a community. However, it does not explain that if you are a maintainer of a community, wishing to delete a post from the said community, you must be logged in as the maintainer. Seems obvious to many of us because we're community maintainers ourselves, but some people don't catch on to that. ;)

Also, the following paragraph is a little confusing:

While editing entries, if you receive an error message that states "Client error: Invalid text encoding: Cannot display non-Unicode posts unless default encoding has been selected", see http://www.livejournal.com/support/faqbrowse.bml?faqid=133. This process will need to be done by the community maintainer, while logged in as the community journal.

Since the FAQ is about editing and deleting posts from a community, the last line about having to be logged in as the community journal may make people think that any editing or deleting may have to be done while logged in as the community.

Or, it might be a good idea to just add a new FAQ to the community management category that explains how to delete posts if you're the maintainer. Okee, that is all.
Subscribe

  • FAQ232

    There is a typo (or two) in FAQ232. I'm talking about the following sentence: Ddd them to your Friends list them with the Add Friend button at…

  • New FAQ: How do I deal with spam?

    This FAQ is meant to tie together all of our spam-related information, currently spread over several different categories. Ideally, I'd like to have…

  • Identity Account FAQs

    As LiveJournal Support regularly uses the term identity accounts both in answers to users and amongst themselves, and some system pages refer to…

  • Post a new comment

    Error

    Comments allowed for members only

    Anonymous comments are disabled in this journal

    default userpic

    Your reply will be screened

    Your IP address will be recorded 

  • 5 comments