Skip to content
New issue

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

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

Already on GitHub? # to your account

override thread discovery with custom data-attributes #27

Closed
posativ opened this issue Nov 5, 2013 · 10 comments
Closed

override thread discovery with custom data-attributes #27

posativ opened this issue Nov 5, 2013 · 10 comments
Labels
needs-more-info Please provide more detailed info so this issue can be verified and fixed server (Python) server code

Comments

@posativ
Copy link
Collaborator

posativ commented Nov 5, 2013

No description provided.

@posativ
Copy link
Collaborator Author

posativ commented Dec 16, 2013

Broken when using the same comment thread on multiple URLs.

@Zimmi48
Copy link
Contributor

Zimmi48 commented Nov 21, 2014

Hi,

I have two problems:

  • the same page is accessible via example.tld and example.tld/index but Isso thinks the two pages are different because the URL is not the same
  • if, in the future, I move a page URL, I am afraid I would lose the comments.

Making this feature work again would solve these two problems I think.
Is there a lot to do about it? If you tell me where to look and what does not work I may cast a look and see if I can fix that...

Thanks!

@posativ
Copy link
Collaborator Author

posativ commented Nov 21, 2014

The issue is basically a missing one-to-many (id to urls, it is id -> url currently) relation in the database. It requires some work (you need to do the migrations, too).

@dashohoxha
Copy link

This is a big problem for me, because I want to use comments in a mobile app, where url almost never changes, but the content changes (through ajax). So, I need to be able to reference the comments by id, not by url.

Without knowing the structure of the DB and without looking at the code, I would suggest to just get rid of URLs everywhere. We don't need them, we need just IDs in order to identify comment threads. By ID I mean a unique string, not a number. In special cases it can be set to be the url itself, in special cases it can be a number (converted to string), but let the website decide what the ID of the comment thread should be.

ArthurHoaro added a commit to ArthurHoaro/Shaarli that referenced this issue Aug 22, 2015
Done: won't work because of isso-comments/isso#27
Waiting for an eventual fix.
@gllmhyt
Copy link

gllmhyt commented Feb 7, 2016

It was working with 0.9.10, but since 0.10.1 it seems not, too bad!

@posativ
Copy link
Collaborator Author

posativ commented Feb 7, 2016

This issue is still open, what do you mean exactly?

blatinier pushed a commit to blatinier/isso that referenced this issue Jun 1, 2016
blatinier added a commit to blatinier/isso that referenced this issue Jun 1, 2016
blatinier added a commit to blatinier/isso that referenced this issue Jul 5, 2016
posativ added a commit that referenced this issue Jul 13, 2016
Fix issue #27 on override thread discovery with custom data-attributes
@blatinier
Copy link
Collaborator

This should be closed since you merged #252 right?

@rawsh
Copy link

rawsh commented Jan 23, 2018

Can this be used now? AMP pages are a usecase

@ix5 ix5 added the needs-more-info Please provide more detailed info so this issue can be verified and fixed label Feb 10, 2022
@ix5
Copy link
Member

ix5 commented Feb 10, 2022

Is this still current?

@ix5
Copy link
Member

ix5 commented Feb 17, 2022

Should be fixed by #252

@ix5 ix5 closed this as completed Feb 17, 2022
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
needs-more-info Please provide more detailed info so this issue can be verified and fixed server (Python) server code
Projects
None yet
Development

No branches or pull requests

7 participants