That could be any (but not limited) with the following points.
- A plugin conflict, it does not mean the error is coming from a file, that does not mean that file is causing the issue, the issue could be a plugin conflict and the
"In 'o.hoverIntent(l,c,u)', 'o.hoverIntent' is undefined" is just an aftereffect of it. I understand that you already have done a plugin test, please do it again with no caching and any optimizer features involve.
- A conflict between old X, Cornerstone and updated Wordpress (or the other way around), you mentioned above that you restored the X to the old version, but did you restore the Cornerstone and Wordpress version too?
Is that the site you're working on below? We are kind of looking blindly there because 1) We can not see the version of your X and Cornerstone from the
<body> class, not sure what you did there or are you using X at all? 2) the error
"In 'o.hoverIntent(l,c,u)', 'o.hoverIntent' is undefined" is not showing up on our end. Maybe we are looking on a different site? Please clarify.
A conflict between a modification you made on the child theme and parent X or Wordpress. One way to test this is to switch to the parent theme.
And also like Ruenel mentioned above, this can be also linked to a corrupted file issue when core files get damage when you do the updating/restoring process. If you still have the original copy of X when you start building the site, try to reinstall that.
Please consider this possibility, it can be one or combination of those.
Sorry, but I can not see how you linked this error with licensing, the only way I can link this error with licensing is because you need a license before you can update X and Cornerstone (automatic update). Updated X, Cornerstone, Wordpress, and Plugins can settle conflicts unless the conflict is on the child theme modification.
Hope this shed some lights.