Crossposting to LiveJournal

[mark]

Hi all,

Due to some recent availability problems with accessing the LiveJournal service, crossposts may be slow. The system does automatically retry, but if it's a slow spot it could be minutes or even an hour or two before we can get the entry posted.

Thank you for your patience!

Comments

[girlfmkitty]

Thank you for keeping us posted on things like this. =)

[firstsuperman]

Yes, I noticed that LJ has had trouble being available the last couple of weeks. Glad you're letting everyone know the cross-post problems aren't your fault (although I never thought they were).

[dil]

LJ has been being in trouble since it was acquired by SUP. And it's getting worse and worse..

[zarhooie]

We try not to badmouth other sites in official communities. It is not in the spirit of the Dreamwidth community. I understand your frustration, but LiveJournal was once the online home for many of Dreamwidth's users and volunteers.

[dil]

Right, it was home for me as well. Anyhow it's getting worse and worse, it's the sad truth.

[malurette]

Thank you for the explanation.

With LJ accessing being touch-and-go, does this mean the importer may experience troubleshooting again, too, like duplicate posts or missing comments, or is this another problem?

[denise]

That's another problem -- at most the import will fail because it can't contact LJ.

[malurette]

OK, thank you for the clarification!

[lil_m_moses]

Thanks for the clarification on the automatic retry - I didn't realize it would do that.

[zarhooie]

It is an awesome feature! It tries several times, but only sends a failure message once.

[got_swagger]

Thanks for the update!

[abyssinia]

Thanks for the update.

Also, just fyi, yesterday I had a crosspost successfully post to LJ but my dreamwidth inbox received a note that the crosspost had failed (and, near as I can tell, the entry still thinks it failed to crosspost).

[runpunkrun]

This just happened to me, too. How do we get the DW entry to acknowledge the crosspost? Just wait until the trouble dies down and go into the DW entry and check the crosspost ticky and hope that saving it won't result in a duplicate post?

[denise]

Sadly, there's no way to connect them up again, because LJ returned a failure ("this didn't post") when we made the call to their interface to post the entry rather than a success (with the URL of the LJ version of the entry). The only way to fix it is to delete the entry on LJ, then edit the DW entry and re-check the crosspost box to post it on LJ from scratch.

[runpunkrun]

Oh, sad orphaned post! I'll delete the LJ version and wait until things are better to try crossposting again. Thank you!

[dragondancer5150]

Ugh, yeah, LJ's been having issues for at least the past few days, so I'm not at all surprised to hear this.

Thanks for the head's up! I have my account marked to crosspost automatically, but I don't often check to see if it actually does.

[ardath_rekha]

Thank you for the heads-up! I'd noticed the downtime issues when I visited LJ the other day, but hadn't even thought about how it might affect crossposts and imports. As always, it's lovely to see just how on top of everything you already are. :)

[bluebellanon]

Hello! I'm essentially hoping for help with a problem I first commented about here.

I hope this is the right place to ask - I'll copy my comment here too:

Do you happen to know if anyone else has been having a problem where not all entries are imported over when you run an import?

Because when I repeated the sherlock_bbc import from sherlockbbc to get the comments (which failed to import before) it looks like an entry hasn't transferred. I don't know if there's more than that one, but that's one I've noticed straight away.

The entry in question is this: http://sherlockbbc.livejournal.com/5120925.html if that helps at all!

I also noticed I also have a lot of duplicate entries. Did I need to run the removal tool first? I though DW took already existing entries into account when running new imports? Sorry to be such a pain!

And one last question, do I need to wait until these recent availability problems have passed before trying the import again?

[denise]

That's very much more complex than can be handled with simple troubleshooting in comments here!

For the duplicates, run the imported content removal and then try importing again. (You should wait until the LJ troubles ease up, yes.) For the entry missing, you should open a support request. Please do be aware that import problems are very complex and can only be handled by certain people, all of whom are very busy, and so it might take a long time before someone can help you troubleshoot.

[bluebellanon]

Thanks so much for your reply! :)

I'll try the import again as you say, once the trouble eases then if the entry still doesn't import across I'll open a support request.

Thanks again.

[ironed_orchid]

That you for letting us know.

[feng_shui_house]

Thanks for the information! I had noticed my cross-posts in the last few days failed entirely. I assumed it was because LJ had recently rolled out a new release on the 20th. I do hope it can be fixed, but I suspect the fix isn't under DWs control.

Thoughtul

[babysprite]

It's very thoughtful of the DW crew to keep us informed.

There's a good number of people here still maintaining ties with LJ.

What you do does not go unappreciated.

/\__/\
(='.'=)
(")_(")

MUSIC: Grizzly Bear - Gun-Shy

[doomspark]

I assume this is why I'm unable to set up crossposting to LJ at all? I get an error message 'Failed to connect to http://livejournal.com/interface/xmlrpc'

[azurelunatic]

It's still going on, and would cause that error.

[wytchcroft]

Simon, hi; i just closed my request as your reply was helpful.
But i thought it might be useful to add that the main problem i'm having in copying or pasting text (rather than cross posting) is that although it looks right in the editor - when the save function is used and the post is then read, it comes out as word salad and minus all the formatting.
this has also started happening at my blogspot (which recently changed some functionality as well).
i have the option of entering either HTML or small amounts of pasted text and editing piecemeal.

notepad is a help (thanks) i'd forgotten i had it!

hope you don't mind commenting on this, didn't seem worth blocking the maintenance channel but it's a new and slightly odd development.

feel free to ignore what is probably some obvious mistake of mine and best wishes to all the DW crew for the new year.

stay well :)

[denise]

The support team doesn't read comments on dw-maintenance posts! (This is more for big problems or things affecting everyone.) If you're still having issues, you can feel free to reopen the support request. :)

[wytchcroft]

ah hell, i just stick with 'best wishes' and hide if that's ok... *oh the shame*

[denise]

Oh, it's fine! I just didn't want you to wonder why nobody was helping you troubleshoot ;) The support board is where you go for in-depth troubleshooting that needs to take a bunch of time; comments here is for "hey, this is broken for me, is that something everybody's having happen?" after a code push, or "this particular thing is happening to me, is that related to the problem you guys just posted about?" (Which will often get "nope, so open a support request for further troubleshooting!")

[zarhooie]

I hereby personally invite you to bother me with your problem! <3

[wytchcroft]

gratefully noted.
but not on this thread (i've caused enough traffic for one night) and not on new years eve - it's a little distracting :)))

[zarhooie]

If you reopen your request, I'll poke at it. :)

[wytchcroft]

done! :)