Home › Forums › Classic DFFS › SP Online Form Load Error
Tagged: js functions
- This topic has 6 replies, 3 voices, and was last updated 6 years ago by Alexander Bautz.
-
AuthorPosts
-
-
November 2, 2018 at 09:29 #22671
Hi Alexander,
I’m using the newest version of DFFS (4.4.3.57) on a list in SP Online.
In Chrome the form works like a charm, but in IE I get the error message shown in the Screenshot. (error1.png, error2.png)When using the debugger in Chrome I get the notification that undefined.js could not be loaded – but only when using the debugger.
Do you have any idea what can be done here ?
Thank you very much in advance.
BR,
ChrisAttachments:
-
November 2, 2018 at 12:06 #22675
Ensure the function toggleCreateButton1 is defined in your Custom JS or in external js files you load above Custom JS.
Alexander
-
November 2, 2018 at 12:52 #22677
If you have already made sure you have a function called toggleCreateButton1, try copying that function and pasting it into jshint.com to see if there is a syntax or typing error in the function that is causing it to break.
-
November 5, 2018 at 08:26 #22681
Hi,
Thank you for your input.
As stated above, the function works correctly in Chrome, it does not work in Internet Explorer. It seems like there is a loading problem in IE that does not affect the Chrome Browser.Do you have some other suggestions ?
Thank you very much in advance.
BR,
Chris -
November 5, 2018 at 19:40 #22692
It could be that your custom js has some typos / script errors that only IE stumbles on.
What you can do (after you have done what Keith recommended regarding JSHint.com) is to load the form and hit OK to close the error message, and then bring up the developer console and paste your entire Custom JS code in the console and hit Enter. This will most likely give you some more details about where the error is detected in the code.
Alexander
-
November 8, 2018 at 17:41 #22762
Hi Alexander,
Sorry for the late reply.
I figured it out. The problem was that Internet Explorer doesn’t recognize the arrow operator in JavaScript and because of that created the error message. Chrome does recognize the operator and because of that it was working in Chrome.I’ve modified the function and now it also works in Internet Explorer.
BR,
Chris -
November 8, 2018 at 18:42 #22764
I’m glad you figured it out.
Alexander
-
-
AuthorPosts
- You must be logged in to reply to this topic.