How to migrate from django-comments-xtd?

[jdbit]

Hi, could you please tell me how to migrate from 2.x to 3.x? As far as I understand, I'll lose likes/dislikes from the xtd, but it's not a problem. Should I just dump the data from django-comments-xtd, rename the table names in the json file, and load the data to django-comments-ink?

[danirus]

Hi, That could be better done using a management command. The DB schema of django-comments-ink is different from the schema of django-comments-xtd. The likes/dislikes have to be converted into CommentReactions, and XtdComment's into InkComment's referring to CommentThread's.

[jdbit]

Thank you for your reply. I replaced django_comments_xtd.xtdcomment to django_comments_ink.inkcomment in the json file I dumped by ./manage.py dumpdata django_comments_xtd > comments.json command and than loaded the json file. Looks like it works. I don't care about likes/dislikes so I didn't convert them into ComentReaction.

Everything works, except nothing happens when I click the React button. I included the javascript, no errors in the js console, but no reactions modal either.

[danirus]

The current schema for InkComment, implemented in migration 0000 will change and it won't be covered in a new migration but rather change in the migration 0000 itself. That's why I added the "Don't use it yet" in the readme. Be aware of it because you won't be able to update via migrations.

When the app is ready I will update the docs. Meanwhile you could look at the dci-project-stories repo to see the templates and how they work with the plugin. The reason why you don't see the reactions panel most probably has to do with that. You need to provide the reactions panel template via the use of a template-tag.

[jdbit]

Fixed reactions modal by adding modal.css and reacitons.css, looks like everything works now. Okay, I'll wait at least until this migration will be applied. Nice app by the way! Thank you for your help.

[Hopiu]

The current schema for InkComment, implemented in migration 0000 will change and it won't be covered in a new migration but rather change in the migration 0000 itself. That's why I added the "Don't use it yet" in the readme. Be aware of it because you won't be able to update via migrations.

When the app is ready I will update the docs. Meanwhile you could look at the dci-project-stories repo to see the templates and how they work with the plugin. The reason why you don't see the reactions panel most probably has to do with that. You need to provide the reactions panel template via the use of a template-tag.

Do you have a rough plan on when a first usable release will be ready? We'd like to use django-comments-ink in a project and are willing to help you getting the most important changes done. (If you are open for help)

[rollue]

The current schema for InkComment, implemented in migration 0000 will change and it won't be covered in a new migration but rather change in the migration 0000 itself. That's why I added the "Don't use it yet" in the readme. Be aware of it because you won't be able to update via migrations.
When the app is ready I will update the docs. Meanwhile you could look at the dci-project-stories repo to see the templates and how they work with the plugin. The reason why you don't see the reactions panel most probably has to do with that. You need to provide the reactions panel template via the use of a template-tag.

Do you have a rough plan on when a first usable release will be ready? We'd like to use django-comments-ink in a project and are willing to help you getting the most important changes done. (If you are open for help)

Wondering the same, too - planning to implement comments for our service. Still deciding whether we should use django-comments-xtd, django-comments-ink(which seems like django-comments-xtd 3.x release version), or even try to write from scratch with postgres ltree.

[rollue]

Out of curiosity - what is the point of a separate CommentThread model like below?

django-comments-ink/django_comments_ink/models.py

Line 71 in 5a202e1

class CommentThread(models.Model):

Django-comment-xtd had the thread id as a field in the XtdComment model.
https://github.com/danirus/django-comments-xtd/blob/557c771b595e2a4ac6dcfba2ab2b237572720d6d/django_comments_xtd/models.py#L63

It looks like field/model is used to save a reference to the "post" instance that the comments belong too. But the Comment model from Django's original contrib comment already has a generic FK to the "post" or the "thread" object. Am I understanding this correctly?

@danirus