DOCUMENTATION: Reposting entries to another journal

Reposting entries to another journal

Occasionally, you may find it useful to transfer posts from one journal over to another journal, or even another Livejournal-compatible server to another.

LJ-Sec will now allow you to perform this task, with the following limitations:

  • User comments cannot be transferred
  • Custom security groups *probably* will not transfer properly. (You can try, but it probably won't work well.)

    Doing this requires you to perform the following steps.

    1. Login to LJ-Sec using the source Livejournal account and server. (Please see how to login if you cannot remember the steps to do this.)
    2. Check all the posts you want to transfer over.
    3. From the "Journal" entry, select "Repost checked entries to another journal"

      You can also select the repost button on the side of the main screen:

    4. You will be presented with the following popup:

      Enter in the information as follows:
      • USER NAME: The login name of the journal.
      • PASSWORD: The password for the journal.
      • COMMUNITY: If you are subscribed a community and have filled in a login, hit "Get a list of subscribed communities". This will grab a list of communities you have access to. You can then select a community that you manage. Note that if your user name and password is invalid, you cannot grab a community list. You are not allowed to process communities that you are not subscribed to.
      • SERVER URL: The address of the Livejournal-compatible Server URL. By default, the URL is what you use to login (which is probably Livejournal), but you can utilize other Livejournal-compatible blogs if you wish. For more information on server URLs, take a look here.
      • ATTEMPT TO TRANSFER CUSTOM SECURITY SETTINGS: By default, any journal entry that uses a custom security group is transfered over to the receiving account as a friends-only post. You can *try* and transfer your security groups with this setting, but it will only work properly if the security groups were created in the same *numeric* (not alphabetic) order on both accounts. (Maybe not even then.) Use this setting with caution.
      • ATTEMPT TO TRANSFER KNOWN COMMON METADATA: By default, this is checked. This will transfer metadata that is believed to be compatible with most of the Livejournal-type clients out there: current mood, current music, your icon, and tags.
      • ATTEMPT TO TRANSFER *ALL* METADATA: Checking this setting will attempt to transfer *all* metadata. If incompatible metadata is present, you may not be able to repost. So by default this is disabled.
      • BACKDATE ITEMS: By default, items will be posted as back-dated. This is standard practice for posting historical journal entries, see this FAQ for reference. You can turn off this option, but Livejournal *will not allow* a post to be made if there is one dated in front of it. Turn off this option only if the receiving journal is blank, or all posts in the receiving journal are behind the journal entries you are transferring!
      • SAME SERVER DUPLICATE POST PREVENTION: By default, LJ-Sec will prevent you from reposting journal entries on the server you are logged into. For instance, you can't by default post your Livejournal entries back into a Livejournal account. Accidentially double-posting on your own journal therefore is discouraged. There may be times that you wish to do this (for instance, if you are duplicating posts in another journal on the same server, or if you are restoring a deleted post). If so, turn this option off and you will be allowed to post on the same server that you are logged into.
    5. Click "Begin reposting". LJ-Sec will confirm that you want to transfer entries.
    6. Wait.

    Your journal posts should be transferred over to the second account.

    NOTE: If reposting from a community, be aware that all entries will appear under your account name! By default all entries from a community are grabbed... entries *not* posted by someone other than yourself will have a message appended to the top describing the original poster. Please see the warnings in this section for more detail on issues managing communities.

  • Copyright © 2006 Chad Gould