How can this error be rectified? What's the cause of this error?
Warning 1 Error updating JScript IntelliSense: Object doesn't support this property:#--
I found this via Google - have you tried it?
http://patrickyong.net/2009/05/08/error-updating-jscript-intellisense-object-doesnt-support-this-property-or-method-21391/
Related
Suddenly I am having javascript error and cannot edit any cms page (cms/page/edit/page_id/45) or block. I have been trying to solve this for the past week with no success. I have also tried removing the modules that I have installed recently.
I did not touch any core files and I have updated file permissions but still get this error below in chrome console from the core static files
VM6148:68 Uncaught SyntaxError: Invalid or unexpected token
at template (template.js:79:36)
at render (template.js:140:24)
at iterate (template.js:236:33)
at Function._.each._.forEach (underscore.js:150:9)
at Object.template (template.js:206:15)
at UiClass.initConfig (class.js:89:28)
at UiClass._super (wrapper.js:106:35)
at UiClass.initConfig (abstract.js:123:18)
at UiClass.initConfig (wrapper.js:109:34)
at UiClass._super (wrapper.js:106:35)
Image showing spinner and javascript error
In my case, it was a database issue due to js injection. Patching a 3rd party extension fixed the issue.
I'm getting the old 'directory is not a file' error with Node, and the output does not make it clear what exactly it's trying to parse. I've tried putting logging in and everything to find the issue, and even created a brand new project but the issue persists. Can anyone shed any light on this?
Error: EISDIR: illegal operation on a directory, read
at Object.readSync (fs.js:592:3)
at tryReadSync (fs.js:366:20)
at Object.readFileSync (fs.js:403:19)
at UnableToResolveError.buildCodeFrameMessage (C:\Users\thepo\Applications\WakeMyPC\node_modules\metro\src\node-haste\DependencyGraph\ModuleResolution.js:304:17)
at new UnableToResolveError (C:\Users\thepo\Applications\WakeMyPC\node_modules\metro\src\node-haste\DependencyGraph\ModuleResolution.js:290:35)
at ModuleResolver.resolveDependency (C:\Users\thepo\Applications\WakeMyPC\node_modules\metro\src\node-haste\DependencyGraph\ModuleResolution.js:168:15)
at DependencyGraph.resolveDependency (C:\Users\thepo\Applications\WakeMyPC\node_modules\metro\src\node-haste\DependencyGraph.js:353:43)
at C:\Users\thepo\Applications\WakeMyPC\node_modules\metro\src\lib\transformHelpers.js:271:42
at C:\Users\thepo\Applications\WakeMyPC\node_modules\metro\src\Server.js:1098:37
at Generator.next (<anonymous>)
The problem turned out to be that some of the versions of modules that I installed using npm were not compatible with expo. These were indicated earlier than the error in the output for the 'expo start' command. Because these were info logs, I didn't pay enough attention to them. However, after several hours I decided to fix them and it fixed my problem.
The fix was to follow each individual package named in the output and run 'expo install '.
Make sure the entryPoint key in your app.config.js or app.json file is correctly set.
I had an intermittent error very similar to this and it was related to a bug with remote debugging.
Turning off "Debug Remote JS" in the Expo Go app shake-to-show developer menu avoided this issue for me (logs and errors still show in the Metro console).
Here's the exact error message I was getting (and sometimes the app would just fail silently without any error). It's almost identical to the error in the question with a few different line numbers (maybe from different versions).
Error: EISDIR: illegal operation on a directory, read
at Object.readSync (node:fs:721:3)
at tryReadSync (node:fs:431:20)
at Object.readFileSync (node:fs:477:19)
at UnableToResolveError.buildCodeFrameMessage
As for "why", there's some related discussion on this expo forum thread which in turn links to this React Native bug (claimed to be fixed in Expo CLI 4.13.1 but many users reporting similar issues in recent versions).
It might be related to the reported issues with Reanimated 2 and Expo's remote debugging (see this reanimated issue and the warning note in Expo's documentation) for Reanimated.
I have a Polymer web component that works stand-alone. However, upon bringing it into my app, I am getting a TypeError about dispatchEvent:
Uncaught TypeError: Failed to execute 'dispatchEvent' on 'EventTarget': parameter 1 is not of type 'Event'
I am debugging this now but wanted to post this, as there isn't currently another single result that I can find about this error specifically related to Polymer.
The problem was that an earlier version of JayData is not compatible with webcomponents.
I was using JayData and was on version 1.3.6.
I've downloaded and updated to the latest version (1.5.6) and this has fixed the problem.
I am writing automation test for a Rail app using Selenium, Capybara and Cucumber running on Jenkins. Recently, lots of my tests failed due to error:
unknown error: Cannot read property 'ownerDocument' of undefined
(Session info: chrome=47.0.2526.106)
(Driver info: chromedriver=2.20.353124 (035346203162d32c80f1dce587c8154a1efa0c3b),platform=Linux 4.0.5 x86_64) (Selenium::WebDriver::Error::UnknownError)
./features/step_definitions/advanced_search.rb:81:in `/^user can see search buttons and links$/'
and in Chrome inspect, I can see a javascript error:
Uncaught TypeError: Cannot read property 'ownerDocument' of undefined
So, I want to know if this javascript error can make my tests failed? This error only appears after clicking on an element. Have anyone experienced this error? How to solve this?
Thanks.
Yes a JS error can cause tests to fail since it means things in the page aren't doing what you'd expect. The Chrome inspect should show you the source of the JS with the error, if it's in your JS you'll need to fix it, if not it may be a bug in chromedriver.
I have built an asp.net application. Every time I am running it, I am getting an error saying:
Unhandled exception at line 1, column 1 in script block
0x800a1391 - JavaScript runtime error: 'fidoCallback' is undefined
I have tried adding
function fidoCallback(status) { }
but it is not helping. Any help would be appreciated.
Got the actual reason behind the error. It is because of the Nok Nok Labs installed. Uninstall that from your extensions and then you can see that the error does not repeat. No need to add fidocallback after this.
Actually, the name of the Nok Nok Labs package is "Multifactor Authentication Client". Just uninstall this package from "control panel/programs and features".