*facepalm*

[denise]

We've just realized that thanks to a recent code change, if you have your account set up to crosspost to another site by default, and you then import journal entries from another service, those imported entries will be crossposted according to your default crosspost settings ... even if that means they're crossposted back to the site they originally came from, as new entries.

Oops. (We are really, really sorry about that.)

We'll have a fix for that done and pushed live as soon as possible (and will let you know when we do), but in the meantime, the workaround is to either a). postpone importing until we get the fix pushed, or b). remove any saved crosspost accounts before you import your journal, then re-add them once you're done.

If you were affected by this, please open up a Support request and let us know; we'll do everything we can to help you clean up our mess.

EDIT: This has been fixed, and is now live.

Comments

[princessofgeeks]

it's always something!

[sineala]

Hi! I'm sorry I broke everything! I had entirely forgotten I'd set up a crossposting account when I went to do this.

I went back and readded the LJ account just now, though as I only took it away after I noticed my inbox filling up with crosspost messages, it didn't do much good. (Sadly, it didn't occur to me to change my password elsewhere until many, many entries in.) My DW inbox is, um, very full now.

Thanks for the prompt acknowledgment. (If you delete the entries here, the duplicates will vanish off LJ, right? Maybe? I would very much like that.)

[foxfirefey]

You did not break anything. This was our fault. We should be thanking you for bringing it to our attention.

[zarhooie]

We ARE thanking you!

[sineala]

You're welcome... I think.

I'm glad I could find you this bug. Of course, mostly I wish it hadn't existed.

[zarhooie]

We are working hard to find a way to fix this for you so you don't need to do anything. Just hold tight for another little bit and we'll take care of it.

[kfk2]

So did it then try to import the entries it just cross posted? which were then cross posted.. which were then imported.. which were then cross posted.... and on and on and on?????

Cause if so I think you deserve an award for coolest infinite recursion.

[zarhooie]

Nope, not an infinite recursion error (thank goodness!). We made the crossposter and the importer talk all nice-like back in August, so that it won't import crossposted entries. If we *hadn't* then yes, best IRE ever!

[oona]

Love that userpic!

It's nice of DW to apologise and offer to help rather than blame someone else and say screw it, like some sites do. :)

[diarmi]

Hee, that happened to me! But I just created an account and I'm completely new here so I just thought it was me being silly and my mistake. Generally not big deal since I didn't have many entries at LJ so I just could delete doubled entries manually. My biggest worry was if someone who could have turned on notifications for my entries got inbox cluttered... THAT would be awkward...:)

[erilyn525600]

This is why I love you guys. You make a mistake, you apologize and fix it. Thank you so much for that.

[azurelunatic]

And just commenting here to say that yes, word has been passed to LJ support (support manager etc.), so LJ support will know what went down and why, and not be completely mystified and will know to send people to DW support.

[vampwillow]

Ah, wonderful! It's always what happens when you try to make things even better than they already are ;-p

[alierak]

I guess we should tell people we got the fix pushed last night?

[yvi]

Strange, it's marked as not pushed on this page: http://www.dreamwidth.org/misc/code-status.html ?

[alierak]

That's because that page is checking the dw user's cvs dir, assuming all updates are pushed by updating there first, then copying over to the production tree. To push one change by itself, mark patched the production tree directly, just as I would've done.