If this is any help:
Uncaught Error: Attempting to use a disconnected port object
2VM16566 extensions::messaging:70
Uncaught Error: Attempting to use a disconnected port objectVM16566 extensions::messaging:70 PortImpl.postMessageextensions::SafeBuiltins:19 target.(anonymous function)VM16563 extensions::utils:94 publicClass.(anonymous function)page-state-tracker.js:1 b
In your Google Analytics account check how your pages are tracked (the exact URI); on a busy site you can also check that using the real-time feature from your dashboard.
Post that URI along with the full URL of the corresponding page from your blog.
-21 is thrown when there’s no data or when an empty response is returned.
For example this page(http://eugenedailynews.com):
/2015/02/bookings-for-the-lane-county-jail-february-25-2015/index.php
Live shows 65 people currently reading that page and it’s been viewed more than 7900 times today according to the GA Dashboard Analytics report.
WordPress obviously doesn’t tack the index.php onto the URL’s for the pages: http://eugenedailynews.com/2015/02/bookings-for-the-lane-county-jail-february-25-2015/
This appears to be a bug no?
No, I think the issues is generated by a tracking code duplicate.
In your page source search for “UA-“. At the end of the page you have the tracking code inserted again. I wonder how your bounce rate looks like. I can bet is quite low, because every visit gets tracked twice.
You should remove the second code ASAP!
Hello,
Is this a confirmed issue/solution? One change of note in my instance of this issue, is that the only report that doesn’t show up is social media referral traffic.
In that quarter where the report would typically be (on other WP sites where I have your awesome plugin installed), the message, “This report is unavailable (-21)” appears. The remaining three quarters are displaying data correctly.
If there was a tracking code duplicate, I would not have access to any data, correct? Hence my query, curious as what else it could be/how I can fix.
Thanks!
Read the documentation, it’s all there, including FAQ and errors.
@dirty-bill: There are some improvements in 4.8.1.3 regarding this issue, you should:
1. Update to latest version
2. Clear the authorization and authorize again.
3. Clear cache
check if there are any changes on the problematic reports.
If the issue remains, open a new support topic.
