We have had an alert in Google webmaster tools saying there was a malware issue on our site, however it didn't provide any example urls and has since been reviewed and cleared. Trying to do some digging as to why this occurred using an online scanner (http://scanner.pcrisk.com/) it has flagged jquery-2.1.4.min.js as being potentially suspicious.
The details I got from the scanner were as follows:
/styleassets/javascript/jquery-2.1.4.min.js
Reason:
Detected potentially suspicious content.
Details:
Detected potentially suspicious initialization of function pointer to JavaScript
method eval <code> = eval; <code/>
I can't be sure if this was causing the issue but want to try and find out more. I've had a search and haven't found anything directly related to why it would be flagged.
Does any know if this is an issue or has anyone found similar with a version of jQuery?
Related
I'm getting the following Javascript error appearing in the Google Chrome debugger.
This doesn't appear on a regular, consistent, basis and it doesn't appear to impact the normal operation of the page. I've never seen this before and am curious if anyone knows what this is referring to? This is not coming from any of my code, or any library I'm using, as far as I know.
A Google search on this returns nothing that I could find.
#SimonNigro is correct. In my case it was extension "Video DownloadHelper"
https://chrome.google.com/webstore/detail/video-downloadhelper/lmjnegcaeklhafolokijcfjliaokphfk. An error disappeared after I disabled the extension.
I'm using the Google docs viewer:
<div class="embed-r embed-responsive-a">
<iframe class="embed-responsive-it" src="https://docs.google.com/viewer?embedded=true&url=http://LINK.PDF"></iframe>
</div>
Many times, though, when I load the page, I just see a big blank space, instead of the file. You need to refresh the page one or more times in order to see it.
Any help?
I'm having exactly the same problem, but I stumbled across this whilst researching this particular issue.
https://productforums.google.com/forum/#!topic/drive/tLVhGbITFMk
It suggests that there is a 'partial sign out issue' with a Google Account. Having read the doc above and tested being signed in and signed out of my google account, it seems to have solved the problem.
It's an imperfect solution I grant, but as no definitive error code is thrown due to the security constraints of clickjacking, I get it.
It may continue to present problems to your end users, but as mine are local and limited to a maximum of 3, it isn't a huge issue to overcome with a little polite coercion.
-- FURTHER Information --
It looks like the 'solution' was a fluke and it has since been confirmed by Google that this feature is actively being discontinued. (thanks to: #omniasoft (twitter) for posing the question to Google.
Google Docs viewer returning 204 responses, no longer working, alternatives?
https://productforums.google.com/forum/#!msg/docs/hmj39HMDP1M/X6a8xJwLBQAJ
Sorry for any false hope!
I'm debugging a WebGL application, and the following error message pops up in my console, right after a call to compileShader() and getShaderInfoLog():
GL_INVALID_OPERATION : glGenSyncTokenCHROMIUM: fence sync must be flushed before generating sync token
I've searched teh interwebs for glGenSyncTokenCHROMIUM, with no avail.
(This error seems to be hardware-specific, as I can only reproduce it on a GT-I9505 when running Chrome)
What does this error mean, and/or how can I get more detailed information of what's going on?
It seems to be indeed device/GPU/driver problem. There's bug in Chromium bug tracker (by the way, you can provide your case to it).
There're several ways to get information and help on WebGL bugs. Besides StackOverflow, there is WebGL google group (browser developers also active in it). Bugtrackers may be helpful (you always can and should report bugs to developers). And, if you feel like it, Chrome and Firefox have excellent code search engines (ff, cr), more than once I've found answers to my questions there.
I'm new to developing and started with a ruby on rails tutorial.
There i came to an error and after redoing it and googling it for days i can't figure it out. I was told to learn how to debug but i have no clue how to. i read that it actually is not possible to debug css. Maybe i used the wrong expression and i don't want to make it about my error which i already asked about here: CSS is not working after push to heroku but works on localhost
and here endless scrolling does not work
but i was wondering how to debug in general. i found various code snippets but not a really good tutorial where it explains everything from the beginning. i found things about breakpoints which i have no clue about what it is and where to set and how to read or where to get the logfile. do you know any good tutorials about that topic which i weren't able to find yet. something like a debugging for dummies.
Thanks a lot.
The Rails Guides site is an excellent resource for learning Rails.
Here's a great one on your subject: http://guides.rubyonrails.org/debugging_rails_applications.html -- section 3 goes into the debugger itself. Should really be all you need, but let me know if you've any specific questions after reading this.
Debugging CSS is different, though. Generally, the best way to debug CSS is to play with it in real time in a web page. You can do this with the Firebug addon for FireFox, or the web inspector which is built in to Chrome and Safari.
Debugging means finding and fixing problems with your code. You can start by checking your code for syntax errors (such as typos in function names or missing punctuation). Then use print statements (such as document.write in JavaScript) to check that your variables have the correct values. Also check for mistakes in logic, such as off-by-ones and infinite loops. Based on the unexpected results (and error message, if any), try to figure out which part of your code is faulty. You can debug without a debugger program, but they offer useful features. Your code can run slowly (line-by-line or pausing at the breakpoint), so after each line/breakpoint, you can check its status.
I'm using YUI,
and sometimes I'll see this "Permission denied to call method Location.toString" error,
It's reported in connection.js,
I didn't find any clue why this error occur yet.
Very strange
If you are dealing with any Flash through a cross-domain iframe, then it is quite possible that you are seeing a bug in Adobe's Flash Player that occurs with FF2 and FF3.
The bug is in Adobe's public JIRA here: http://bugs.adobe.com/jira/browse/FP-561
There seems to be no motivation to get it fixed, unfortunately.
If the script is executed from a different domain, or you are trying to access the contents of a frame/window/iframe of a different domain, you will see this error. Safari's behavior was a little different, at least in the v1-2 era (iirc), so you will probably want to test in that as well.
If you are including scripts via a different domain, you need to make sure your actual triggers/events are tied in and executed from inline scripts, or from a script file loaded from the same domain as your html for best results.
Hi I've answered a similar question
why/where the error “Permission denied for to call method Location.toString”.
This is caused by firebug showing errors from other windows in your console. In short, these errors will probably be nothing to do with your code at all.
If you want to test this theory, you can close all other windows in firebug, clear your console and test just your site.
Are you seeing this in Firebug, by any chance?
I'm getting the same thing in Firefox, off-and-on, after adding jQuery to my site. I'm calling the jQuery js from another site (different domain completely), which I figure isn't much different than calling it from Google's servers.
I have no code using jQuery at all as of the moment. And, while Firebug reports this as an error, it doesn't do so all the time. While I have it turned on, I'm seeing no errors in IE.
While there are different libraries involved, my guess is that Firebug is generating a false-positive.
Now if you're not using Firebug when you see this ... are you using YUI hosted on your own server? What browser are you using? Etcetera.
~James