Cream Puff with Teeth (![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
zarhooie) wrote in ![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png)
dw_support2012-11-07 10:52 pm
zarhooie) wrote in dw_support2012-11-07 10:52 pm
What is going on
Hello again, Support!
Very short version: Mark has diagnosed the comment import issue and is working on a tool to fix it.
Slightly longer version: Stuff broke importing entries from LiveJournal. LiveJournal made a change which confused the importer. During the time between when LiveJournal made their change and when Mark fixed the importer, some users ran imports. [These users now have a problem.] In order to do a successful import, the affected users will need to remove all imported content from their journals to prevent duplication. Mark is building a user-facing tool for this so the users won't need to do it manually or wait for Mark to remove the imported content from Dreamwidth's end.
What Happened: Previously, when the Dreamwidth importer contacted another site to get content (comments, entries, and so on), it would use the entry's URL on the other site. LiveJournal's recent code changes have changed the way they output the URL. This prevented the duplication detector from, well, detecting duplicates. It also prevented comments from being imported because there was no URL to latch on to.
What We're Doing to Fix It: The importer has been changed to generate an entry identification string, and will use that to detect duplicates and grab comments going forward.
Part of fixing it means clearing stuff that was previously imported. There's a tool to do this from the site administrator side. Mark is working on making this a self-service tool, so users who need to use it won't have to go through Support to make it happen anymore.
What This Means for Support: There are a lot of requests about the importer right now. We are going to let them know what happened, and that we are waiting for the duplicate removal tool to be ready for them to use. Mark is working on making a tool available to users, but it is taking a little longer than expected. When something is going to remove
content, he doesn't want to take any chances.
What this means for Users: If you have tried to import since LiveJournal changed their code, you will need to delete all imported comment from your journal and start fresh. We will announce the coming of the tool indw_maintenance (probably here in dw_support also), as well as in any open support requests on the topic.
The tool will delete any comments left on imported entries in addition to the entries themselves. [It will delete ALL imported entries, not just entries imported when the importer was broken.] In short, if you imported an entry, and someone commented on that entry in Dreamwidth, that comment will be lost. This is an edge case, so it's unlikely you'll run into this issue. Comments should be imported from LiveJournal without any issues.
Once your imported content has been removed, you can try to import again. If you see any duplicates after this, please let Support know. Please be patient while importing-- wait times may be longer than normal due to volume.
Thank you for much for your patience through this Exciting Adventure!
Best,
Kat
Dreamwidth Support Admin
(x-posted todw_support_training
Very short version: Mark has diagnosed the comment import issue and is working on a tool to fix it.
Slightly longer version: Stuff broke importing entries from LiveJournal. LiveJournal made a change which confused the importer. During the time between when LiveJournal made their change and when Mark fixed the importer, some users ran imports. [These users now have a problem.] In order to do a successful import, the affected users will need to remove all imported content from their journals to prevent duplication. Mark is building a user-facing tool for this so the users won't need to do it manually or wait for Mark to remove the imported content from Dreamwidth's end.
What Happened: Previously, when the Dreamwidth importer contacted another site to get content (comments, entries, and so on), it would use the entry's URL on the other site. LiveJournal's recent code changes have changed the way they output the URL. This prevented the duplication detector from, well, detecting duplicates. It also prevented comments from being imported because there was no URL to latch on to.
What We're Doing to Fix It: The importer has been changed to generate an entry identification string, and will use that to detect duplicates and grab comments going forward.
Part of fixing it means clearing stuff that was previously imported. There's a tool to do this from the site administrator side. Mark is working on making this a self-service tool, so users who need to use it won't have to go through Support to make it happen anymore.
What This Means for Support: There are a lot of requests about the importer right now. We are going to let them know what happened, and that we are waiting for the duplicate removal tool to be ready for them to use. Mark is working on making a tool available to users, but it is taking a little longer than expected. When something is going to remove
content, he doesn't want to take any chances.
What this means for Users: If you have tried to import since LiveJournal changed their code, you will need to delete all imported comment from your journal and start fresh. We will announce the coming of the tool in
dw_maintenance (probably here in dw_support also), as well as in any open support requests on the topic. The tool will delete any comments left on imported entries in addition to the entries themselves. [It will delete ALL imported entries, not just entries imported when the importer was broken.] In short, if you imported an entry, and someone commented on that entry in Dreamwidth, that comment will be lost. This is an edge case, so it's unlikely you'll run into this issue. Comments should be imported from LiveJournal without any issues.
Once your imported content has been removed, you can try to import again. If you see any duplicates after this, please let Support know. Please be patient while importing-- wait times may be longer than normal due to volume.
Thank you for much for your patience through this Exciting Adventure!
Best,
Kat
Dreamwidth Support Admin
(x-posted to
dw_support_training
no subject