You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there a way to completely disable the comments?
After faffing for hours I have given up for various reasons that I'll not get into much detail on besides noting I cannot use Disqus and don't want to have to have sites (required by both django-contrib-comments & django-comments-xtd), given I only run the 1 site.
I'd also like guidance on removing any noise left in my DB by django-comments-xtd and related, if possible. I have tried migrate django-comments-xtd zero and migrate django-comments zero and same for sites which apparently removed everything relating to those two specifically, but I am still seeing the post's comments icon reading as still having 1 comment (which I posted through xtd as a test earlier on):
I can't see my comment in Django's built in admin, nor can I see comments inside Wagtail's admin pages at all, so unless I do database surgery I can't see how to remove it, and I'd also like to not give the impression that comments are an option.
The more basic comments package does expose itself to Django Admin, which is nice, and comments left using it show up there, but I don't like the UX of the app, nor its forced reliance on sites.
Seems like any variation on setting PUPUT_COMMENTS_PRODIVER to None, empty string, etc. produces various errors where the template expects some sort of comment provider but doesn't find it, generating long errors. Obviously just omitting it defaults to Disqus which just shows the below with a blank space (and still shows the 1 as per above):
The text was updated successfully, but these errors were encountered:
Is there a way to completely disable the comments?
After faffing for hours I have given up for various reasons that I'll not get into much detail on besides noting I cannot use Disqus and don't want to have to have
sites
(required by bothdjango-contrib-comments
&django-comments-xtd
), given I only run the 1 site.I'd also like guidance on removing any noise left in my DB by
django-comments-xtd
and related, if possible. I have triedmigrate django-comments-xtd zero
andmigrate django-comments zero
and same forsites
which apparently removed everything relating to those two specifically, but I am still seeing the post's comments icon reading as still having 1 comment (which I posted throughxtd
as a test earlier on):I can't see my comment in Django's built in admin, nor can I see comments inside Wagtail's admin pages at all, so unless I do database surgery I can't see how to remove it, and I'd also like to not give the impression that comments are an option.
The more basic comments package does expose itself to Django Admin, which is nice, and comments left using it show up there, but I don't like the UX of the app, nor its forced reliance on
sites
.Seems like any variation on setting
PUPUT_COMMENTS_PRODIVER
toNone
, empty string, etc. produces various errors where the template expects some sort of comment provider but doesn't find it, generating long errors. Obviously just omitting it defaults to Disqus which just shows the below with a blank space (and still shows the 1 as per above):The text was updated successfully, but these errors were encountered: