Luminate Online 15.9 - jQuery is not a function - async load order related issue

Daniel Hartanto

Hi 



Just wanted to check if anyone has been experiencing similar issue recently within Luminate Online 15.9 (or at least since it's upgraded to 15.9 we have been seeing this sporadically)



Basically it's a TypeError: jQuery is not a function  that is likely caused by the core jQuery library not readily available as the dependent function(s) are calling for it resulting them not functional and affecting user experience on the site as they encountered these type of 'hiccups'



In one example that we've seen recently it happens on the Waiver page within the Teamraiser registration flow (attached), the "Next Step" button kept being disabled despite he/she has checked the "I agree" acknowledgement, thus user can't proceed to complete their registration. When one refreshes the page, or go back to previous page and come back, the thing resolves itself.



Looking at the debugger, we can see that the "Next Step" button is being controlled by the script section that seems to get inserted by default where we have no control on it programmatically, and these would behave similarly like "inline javascript" and those out-of-the-box jQuery lines seems to be missing the core jQuery (in this case jQuery 1.6.4 that Luminate Online is using by default) that they are dependent on, thus making the handler to enable/disable button validation not functional due to this kind of async load order issue.



Thus wandering if there might be remedy for this -- 

Technical Note:

• We have our own jQuery custom functionalities with newer jQuery core call to the CDN, but those are being written at the bottom of the HTML body thus won't likely cover these 'inline' generated jQuery lines.
• Furthermore, ours and those out-of-the-box Luminate Online jQuery functionalities are more of stand-alone and not related between one another through the use of the jQuery.noConflict

I am thinking whether putting another call to the jQuery core on the HEAD (within the "Additional HTML Tags for HEAD Element") would address this TypeError things -- kinda reluctant to do it blindly since we are already having 2 different jQuery core running.



Let me know and thank you in advance for the shared knowledge and help



regards,

Daniel

Daniel Hartanto

It's a bug  - Bug #70784