As the title says, my browser console is really full of errors some of which are as follows:
Error: ReferenceError: css_ims is not defined
Error: TypeError: br.log is undefined
Error: TypeError: window.ice.onLoad is not a function
Error: TypeError: ice.captureSubmit is not a function
Error: TypeError: ice.setupBridge is not a function
Error: TypeError: ice.push is undefined
Error: TypeError: ice.captureSubmit is not a function
Error: TypeError: ice.onBeforeSubmit is not a function
And guys let me also tell you about the Icefaces version I used:
1. icefaces-3.3.0.jar
2. icefaces-ace-3.3.0.jar
3. icefaces-compat-3.3.0.jar
4. icefaces-mobi-1.2.0.jar
5. icepush-3.3.0.jar
Prior to the use of these 3.3.0 versions and icefaces-mobi-1.2.0.jar I was using 3.0.1 versions and no use of icefaces-mobi-1.2.0.jar in which the browser console was having none of the above mentioned errors. So I was thinking this might be the compatibility issue.
(Note:Here the icefaces mobi jar is used for Mobile related things.)
Thanks in advance. Any help would greatly be appreciated! :)
I'm not sure if adding ICEmobile is causing these JavaScript errors, but ICEmobile 1.2.0 is designed to be used with ICEfaces 3.2.0. For ICEfaces 3.3.0 you should use ICEmobile 1.3.0. Also be sure to clear your browser cache before retrying.
Those errors occurs because all/some icefaces javascript files are not downloaded to the client.
I faced this problem: I investigated this issue using firebug(firefox plug-in) and I found that all resources URL which includes (javax.faces.resource) are giving 302 response error which means that the request is redirected.
I double check and found that I have (javax.servlet.Filter) called AuthenticationFilter which filters all the requests, and if the user doesn't login all requests are redirected to the login page.
To solve this issue: in AuthenticationFilter.doFilter(ServletRequest request, ServletResponse response,FilterChain chain)
I added the if statement:
if (path.contains("javax.faces.resource") || path.contains("/css") || path.contains("/images") || path.contains("/js")) {
chain.doFilter(request, response); // Just continue chain.
return;
}
Related
In relation to this post:
After upgrading from revit 21 to 22 in my company, we can no longer view anything else than the default 3D model in our forge viewer. Initially, i thought the issue arose due to this warning:
"Deprecated API usage: No "GlobalWorkerOptions.workerSrc" specified.".
However, i got that same message in the console of a working implementation i made today, leading me to believe that it has nothing to do with this warning at all.
However, i also see another warning:
"Warning: getOperatorList - ignoring errors during "GetOperatorList: page 0" task: "r: Cannot read properties of undefined (reading 'X')"."
I have tried creating a new nuxt app on Node version 14.9.0, implemented a forge viewer in accordance with the official v7 documentation, and the bug is no longer present.
I then tried to mimic that in my actual production app where the problem exists, by running it on Node version 14.9.0 instead of 10.0.0, getting rid of my entire forge implementation and implemented a simple viewer like above. That did not solve the problem, and i still see above warnings in the console.
The warning is thrown in pdf.worker.jss, which is loaded in via "webpack://adsk/node_modules/#adsk/pdfjs-dist/legacy/build/pdf.worker.jss".
I hope someone has a suggestion.
I'm getting the following error after running stencil start and accessing the localhost url in my browser:
Uncaught Error: Module parse failed: Unexpected token (10:9)
You may need an appropriate loader to handle this file type.
|
| var getAccount = function getAccount() {
> return import('./theme/account');
| };
|
at Object../assets/js/app.js (bootstrap:83)
at __webpack_require__ (bootstrap:19)
at bootstrap:83
at bootstrap:83
(index):1064 Uncaught TypeError: window.stencilBootstrap is not a function
at (index):1064
This just started happening this morning, I was able to run stencil yesterday without any problems.
I've followed the steps here exactly:
https://developer.bigcommerce.com/stencil-docs/getting-started/installing-stencil
I've tried uninstalling stencil and reinstalling multiple times. I've also tried using a fresh clone of cornerstone multiple times in multiple different directories. I can't get rid of this error and have tried all of the troubleshooting suggestions from the docs. There are no errors in the terminal.
I'm on macOS High Sierra 10.13.6
Node Version: v.6.4.0
Any ideas on why I'm getting this error?
This is an issue on our end with the Cornerstone 3.1 release, which can be downloaded through GitHub but hasn't rolled out to production yet. We've got an engineering ticket in to address it, but in the meantime, you can roll back to the Cornerstone 3.0 release to bypass the error. Sorry for the trouble!
New to TestCafe.
Expected
Given .js below, expected behavior when running testcafe chrome this.js is to click on the header logo.
Actual
Uncaught ReferenceError: pagespeed is not defined (at the click below).
On our prod site, this error doesn't happen so most likely some configuration (possibly my version of Apache?) but I wanted to make sure there weren't any TestCafe specific issues. Followed installation using the standard docs (npm)
Thanks in advance!
import { Selector } from 'testcafe';
fixture `A set of examples that illustrate how to use Little Passports`
.page `https://xxx.xxdev.us/`;
test('My Company', async t => {
await t.
click('.header-logo');
});
I think I'll currently get around this by adding -e, but I'll keep this open just in case there's something else to consider...
By default, a test fails when there is a JavaScript error on page. The "-e (--skip-js-errors)" parameter allows running tests by skipping this JS error.
To check if there are any errors on your page, open your browser console. If there are any, you can either fix the errors at the application level (a preferable approach) or skip them during test run using the "-e" parameter.
My web application started to error out yesterday when calling gapi.auth.authorize, and there is no code change. Below is the error stack:
Error: .Uu is not a function
mk#/scs/apps-static/_/js/k=oz.gapi.en.1gq98XyFUlU.O/m=client/rt=j/sv=1/d=1/ed=1/am=IQ/rs=AItRSTPj42_xcRHRghwn4h4H79TdCPg3pw/cb=gapi.loaded_0:234">https://apis.google.com//scs/apps-static//js/k=oz.gapi.en.1gq98XyFUlU.O/m=client/rt=j/sv=1/d=1/ed=1/am=IQ/rs=AItRSTPj42_xcRHRghwn4h4H79TdCPg3pw/cb=gapi.loaded_0:234
qA#/scs/apps-static//js/k=oz.gapi.en.1gq98XyFUlU.O/m=client/rt=j/sv=1/d=1/ed=1/am=IQ/rs=AItRSTPj42_xcRHRghwn4h4H79TdCPg3pw/cb=gapi.loaded_0:236">https://apis.google.com//scs/apps-static//js/k=oz.gapi.en.1gq98XyFUlU.O/m=client/rt=j/sv=1/d=1/ed=1/am=IQ/rs=AItRSTPj42_xcRHRghwn4h4H79TdCPg3pw/cb=gapi.loaded_0:236
.sk#/scs/apps-static/_/js/k=oz.gapi.en.1gq98XyFUlU.O/m=client/rt=j/sv=1/d=1/ed=1/am=IQ/rs=AItRSTPj42_xcRHRghwn4h4H79TdCPg3pw/cb=gapi.loaded_0:238">https://apis.google.com//scs/apps-static//js/k=oz.gapi.en.1gq98XyFUlU.O/m=client/rt=j/sv=1/d=1/ed=1/am=IQ/rs=AItRSTPj42_xcRHRghwn4h4H79TdCPg3pw/cb=gapi.loaded_0:238
Is anyone seeing the same problem? Not sure if Google is making any changes.
Google broke the JS client yesterday. It's being tracked here https://code.google.com/p/google-api-javascript-client/issues/detail?id=103
i have upgraded my worklight with 5.0.5 to 5.0.6 .when i have worked on 5.0.5 it worked fine but the same code when i am using in updated version worklight 5.0.6 it gives me this error
TypeError: WLJSX.Ajax.WLRequest.setConnected is not a function
WLJSX.Ajax.WLRequest.setConnected(false);
when i have build for the first time after upgrading to worklight 5.0.6 it gave this in the console
FWLST1061W: RMLight.java has changed, onCreate() was renamed to onWLCreate(), please check your code for changes. Refer to the IBM Worklight Information Center for details.
can some one help please
am also getting this error
ReferenceError: wlInitOptions is not defined
[Break On This Error]
if (!isIOSEnv() && wlInitOptions.connectOnStartup) {
As the error message states: wlInitOptions is not defined. Could this indee be case? Please see this Stackoverflow question.
Look inside your application's js folder (yourProject\apps\yourApp\common\js). Make sure it contains an initOptions.js
Make sure this file is also referenced in the HTML.