Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disqus import not keeping the thread IDs #563

Open
fluffy-critter opened this issue Aug 5, 2019 · 3 comments

Comments

@fluffy-critter
Copy link

commented Aug 5, 2019

Hi, I'm trying to migrate my site from Disqus to isso, and while I was able to import my comments and the importer showed the specified thread IDs during the import, the actual database is still using the page URI as the thread identifier. For example:

sqlite> select uri,title from threads limit 5;
/comics/journal/400-Shoes|Journal: Shoes
/comics/journal/278-Things-that-go-splat-in-the-night|Journal: Things that go splat in the night
/comics/journal/322-Explosion|Journal: Explosion
/comics/journal/353-Rejection|Journal: Rejection
/comics/journal/469-Scary-pizza|Journal: Scary pizza

IN the above example, the thread with a thread ID of /comics/journal/400-Shoes should actually have a thread ID of mt_1949. When my site is configured to pull the comments with e.g.

<div id="isso-thread" data-thread-id="mt_1949">

the script correctly tries to retrieve the data with OPTIONS /?uri=mt_1949 but that doesn't return any results, as expected.

So, is there any way to tell the Disqus importer to use the specified thread ID rather than the URI?

@fluffy-critter

This comment has been minimized.

Copy link
Author

commented Aug 5, 2019

As a workaround I made a local modification to the import script over in this branch. When I can get the unit tests working (and possibly figure out how to make this an option) I'll open a PR.

@fluffy-critter

This comment has been minimized.

Copy link
Author

commented Aug 5, 2019

Ah, and now I see that the thread IDs are also used as the page link when a reply is sent. So this is much more complicated to implement than I thought.

I’ll work on this over the next few days though, as this is an important feature to me.

@fluffy-critter

This comment has been minimized.

Copy link
Author

commented Aug 7, 2019

I ended up using an alternate approach and just migrated my thread IDs. Feel free to backburner/close this feature request as appropriate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.