Errors and missing digg ??
By babylon on Tuesday, 29 July 2014
Posted in General Issues
Replies 7
Likes 0
Views 1.5K
Votes 0
Hello,

I see the following errors on my site when viewing and inspecting elements with chrome.

Failed to load resource: the server responded with a status of 404 (Not Found) http://widgets.digg.com/buttons.js

In media query expression: (-webkit-min-device-pixel-ratio: 1.5), not all, not all, (min-resolution: 144dpi)

'Attr.nodeValue' is deprecated. Please use 'value' instead.

Consider using 'dppx' units, as in CSS 'dpi' means dots-per-CSS-inch, not dots-per-physical-inch, so does not correspond to the actual 'dpi' of a screen.

In media query expression: (-webkit-min-device-pixel-ratio: 1.5), (min-resolution: 144dpi) tweet_button.1404859412.html:1

Invalid App Id: Must be a number or numeric string representing the application id.
FB.getLoginStatus() called before calling FB.init().

So where does the digg error comes from (link doesnt excist)
And the app id ?
Hello Babylon,

It looks like Digg is no longer offering these share buttons You should turn these integrations off.
Mark
·
Tuesday, 29 July 2014 21:09
·
0 Likes
·
0 Votes
·
0 Comments
·
Ok....and the other things in my topic ?
babylon
·
Tuesday, 29 July 2014 21:16
·
0 Likes
·
0 Votes
·
0 Comments
·
Sorry, missed your other question earlier. Which pages are you getting these errors? If it is EasyDiscuss, ensure that the app id is set correctly in the settings for Social Integrations.
Mark
·
Tuesday, 29 July 2014 21:24
·
0 Likes
·
0 Votes
·
0 Comments
·
Well its called FB loginstatus..?
Does it mean Facebook?
babylon
·
Tuesday, 29 July 2014 21:31
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello babylon,

Yes, these errors are being generated by facebook's javascript library but it's complaining about an invalid application id provided.
Mark
·
Tuesday, 29 July 2014 21:49
·
0 Likes
·
0 Votes
·
0 Comments
·
Invalid? Its still the same facebook connection i use since beginning..
Where to start for solving this?
I hoped you were gonna tell with your reply...
babylon
·
Tuesday, 29 July 2014 22:21
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello,

I cannot really tell where the error is unless I can inspect and investigate this on your site. Is it possible for you to provide us with the back end and FTP access to your site to check on this issue?

Also, where are you getting this error? Can you provide us with the link to the page.
Mark
·
Wednesday, 30 July 2014 01:21
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post