Uncaught TypeError: Cannot read property 'getElementsByTagName' of null
We are getting a JavaScript error on v7.4.1 in the CMS tool. Not sure which content or action is causing this yet. Seems sporadic at the moment. Thank you.
Uncaught TypeError: Cannot read property 'getElementsByTagName'
of null
interact.js?v=7_4_1-07312013:2176
-
cms-js-error.png 8.72 KB
Discussions are closed to public comments.
If you need help with Cascade CMS please
start a new discussion.
Keyboard shortcuts
Generic
? | Show this help |
---|---|
ESC | Blurs the current field |
Comment Form
r | Focus the comment reply box |
---|---|
^ + ↩ | Submit the comment |
You can use Command ⌘
instead of Control ^
on Mac
Support Staff 1 Posted by Tim on 27 Aug, 2013 02:37 PM
Hi,
Thanks for the heads up. I apologize for the delayed response, but I did want to let you know that we have several internal conversations going on regarding this behavior you've mentioned. We have seen it just a handful of other times and it appears to be very intermittent (making it very hard to track down). We are working towards what we believe will be a fix and I'll let you know if we have any specific questions for you.
2 Posted by Ryan Griffith on 05 Feb, 2014 09:38 PM
Hi,
I was going over some older discussions and noticed this one is still open and wanted to provide a follow up. Are you still experiencing this error message?
We have not been able to track down an actual cause for the error, but it appears to occur sporadically and cause the New and History menus to no longer load for a given user. That being said, we do have an internal improvement logged that has been confirmed to clear up the error. This improvement is very high on our timeline, so I would expect it to be out in the very near future.
Please feel free to let us know if you have any other questions.
Thanks!
3 Posted by a6wu on 06 Feb, 2014 12:33 AM
Hi,
No we have not seen this error since a couple weeks after it first appeared.
Thank you for following up.
-Alex Wu
4 Posted by Ryan Griffith on 06 Feb, 2014 03:25 PM
Not a problem at all, Alex. I am glad to hear you have not encountered the error since.
I'm going to go ahead and close this discussion, please feel free to comment or reply to re-open if you have any additional questions or run into the issue again.
Have a great day!
Ryan Griffith closed this discussion on 06 Feb, 2014 03:25 PM.