same comments on all pages of one-page app

[n8m]

I suspect that this is not issue of your directive, but anyway each comment on my app rendering on each page with comment section.
I'm passing the unique identifier as an attribute and use ng-bind-ready, cause I'm using async data loading. Also I've checked that directive see my identifier.
I'm using angular routes without HTML5 mode and without any hash prefix (only # sign).
Do you have any ideas how to solve it?

[michaelbromley]

Hi, if I understand your issue correctly, you are getting all the Disqus comments for your whole site showing up on every page?
One thing I noticed was that you mention a ng-bind-ready attribute. This is not part of my directive, perhaps you are referring to the ready-to-bind attribute?
If you can post your code - both the directive declaration and the corresponsing part of your controller, I might be able to help a bit more.

[n8m]

I misunderstood about name of the "ready-to-bind" attribute and you understand my issue correctly. View:


Controller:
$scope.contentLoaded = false;

if ($routeParams.urlTitle) {
    var urlTitle = $routeParams.urlTitle;
    $scope.post = PostResource.get({urlTitle: urlTitle}, function () {
        $scope.contentLoaded = true;
    });
}
else {
    $scope.is404 = true;
}

Nothing special here.
PS I've sent message to you via your blog feedback form to share the link to website with issue

[michaelbromley]

Does the post object definitely contain a urlTitle property? I notice that the controller has a urlTitle variable which is not on the $scope, so I can only assume that, in order for the directive to work, the object returned by the PostResource service contains a urlTitle property?

If the post object doesn't contain a urlTitle property, then I would guess that the disqus-identifier="{{ post.urlTitle }}" attribute would be an empty string for every page. Perhaps that's the source of the problem? You could check this by echoing out {{ post.urlTitle }} somewhere on the page and see if it contains what you expect.

Another possibility (this is a wild guess) is that there could be a problem if your PostResource service returns a promise. Angular no longer automatically unrolls promises like it used to, so you have to explicitly call the .then() method to get the results.

Let me know if any of that helps point you in the right direction.

[n8m]

I've already checked the urlTitle property and console.log it in your directive. It has value. I'm sure that I have values in my data array when 'ready-to-bind' turns to 'true'

[michaelbromley]

Hi, I took a long, hard look at your test code, and I can see that you seem to be doing everything correctly. I went a bit deeper and analyzed the requests to and from Disqus with Fiddler2. It looks like each page is being associated with the same Disqus thread ID (an internal ID they use to match a Disqus thread to a page).

Here is some more information which may be useful in fixing the problem:

• http://help.disqus.com/customer/portal/articles/472099-what-is-a-disqus-identifier-
• http://help.disqus.com/customer/portal/articles/662547-why-are-the-same-comments-showing-up-on-multiple-pages-

Did you, for example, create your test blog posts before you had implemented my directive? If so, and no unique disqus_identifier was specified at that time, then they might have all been interpreted by Disqus as the same page, since it is a SPA with only a single URL. This is discussed in the second link above.

If so, try making new blog posts and see if the problem remains on the new posts.

[n8m]

So i tried a lot of things to find a solution but finally I changed my application to html5mode routes and your directive got work. The issue is in hashbang, but I dont know where exactly is. Thanks

[michaelbromley]

Hi, thanks. Yeah it seems there might be a problem when using it with the hashbang url mode of $locationProvider. I'll look into that.

[michaelbromley]

Got it working with hashbang URLs now.