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

Post "comment_id" lost when migrating content to new instance #8963

Closed
triestpa opened this issue Sep 1, 2017 · 2 comments · Fixed by #8967
Closed

Post "comment_id" lost when migrating content to new instance #8963

triestpa opened this issue Sep 1, 2017 · 2 comments · Fixed by #8967
Assignees
Labels
bug [triage] something behaving unexpectedly import / upgrade life-cycle stuff: Importing, exporting, upgrading and migrating server / core Issues relating to the server or core of Ghost

Comments

@triestpa
Copy link

triestpa commented Sep 1, 2017

Issue Summary

As a workaround for a breaking issue with the Ghost-CLI (TryGhost/Ghost-CLI#461), I recently attempted to migrate my blog to a new server.

Importing the JSON content from the old instance to the new one resulted in the comment_id property for each post changing. The themes on both instances are identical; both are initializing the Disqus config with -

this.page.identifier = 'ghost-{{comment_id}}';

The resulting comment ID, however, is different in each instance. For example, the post which has a comment_id of 15 in the old instance has a comment_id of 59a935ae0718612fce6740b0 on the new instance.

This is a major issue since it results in the Disqus comment threads becoming dissociated from their corresponding posts. I still have access to the old instance, is there any way to transfer the blog content without losing the comment ids?

Technical details:

  • Ghost Version: v1.8
  • Node Version: v6.11.2
  • Browser/OS: Ubuntu 16.04
  • Database: SQLite
@acburdine
Copy link
Member

@triestpa based on how the importer is currently configured, I can see why this would occur. Definitely still a bug, but your issue makes sense 👍

In the meantime though, you can workaround this issue by manually copying the sqlite database file from one server to the other - this should retain the same data without exporting/importing.

@acburdine acburdine added bug [triage] something behaving unexpectedly import / upgrade life-cycle stuff: Importing, exporting, upgrading and migrating server / core Issues relating to the server or core of Ghost labels Sep 1, 2017
@acburdine acburdine self-assigned this Sep 1, 2017
@triestpa
Copy link
Author

triestpa commented Sep 1, 2017

@acburdine Thanks for the quick reply! And thanks for the workaround suggestion, copying the sqlite file to the new instance allowed for a successful migration.

acburdine added a commit to acburdine/Ghost that referenced this issue Sep 2, 2017
closes TryGhost#8963
- if an LTS export is imported into a 1.0 blog, then the 1.0 blog is
exported and re-imported into another 1.0 blog, any post ids from the
lts import were getting clobbered. This only saves the post id if the
amp field does not already exist
- add failing test that passes w/change
kirrg001 pushed a commit that referenced this issue Sep 4, 2017
closes #8963

- if an LTS export is imported into a 1.0 blog, then the 1.0 blog is
exported and re-imported into another 1.0 blog, any post ids from the
lts import were getting clobbered. This only saves the post id if the
amp field does not already exist
- add failing test that passes w/change
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug [triage] something behaving unexpectedly import / upgrade life-cycle stuff: Importing, exporting, upgrading and migrating server / core Issues relating to the server or core of Ghost
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants