Home › Forums › Classic DFFS › Problems with Chrome and Edge
- This topic has 6 replies, 3 voices, and was last updated 2 years, 6 months ago by Alexander Bautz.
-
AuthorPosts
-
-
September 7, 2021 at 17:35 #34417
HI,
I posted about problems viewing forms quite some time ago in Chrome (and now Edge), the form times out before it displays the form with the error “this took forever”
I have now found what maybe the cause and would like some guidance to understand the issue.
I have attached a screen grab of the Issue in the Dev console (F12)Thanks
Attachments:
-
September 7, 2021 at 20:17 #34432
I’m not familiar with commons.js referred to in the screenshot – if this is a third party script you are loading in your form you must try to remove it first to ensure it is the source of the error. If it is (and you need it) you must try to debug it to find out what is causing the error.
Alexander
-
September 8, 2021 at 08:49 #34441
I’ll have a dig around because I have no idea what commons.js is !
-
September 8, 2021 at 09:00 #34443
Ah! OK, I think I’ve got one step closer to the issue, apparently commons.js is used by an extension that my company have implemented called “walk me” this cannot be disabled and I’ve no idea what it’s for so I will contact our IT dept.
-
September 8, 2021 at 15:57 #34445
OK, but if you are only having this problem in some of your forms it might not be this script that is the cause of the problem.
Which version of DFFS are you running in this form?
Alexander
-
March 17, 2022 at 21:30 #35630
Curious if you ever found a final solution for this? My issue is persisting.
-
March 17, 2022 at 22:01 #35631
I’m not sure how Phil fixed it, but if you are using the DFFS installer / loader version 1 you most likely have better results if you change to use version 2.
See instructions in the installation manual: https://spjsblog.com/dffs/dffs-installation-manual/#InstallDFFS
When you change the DFFS installer to v2 you must uninstall and reinstall DFFS in the form you have trouble with.
PS: You don’t need to back up the config when changing the installer because it is stored in a separate list and is not related to the installer.
Alexander
-
-
AuthorPosts
- You must be logged in to reply to this topic.