2

Uncaught TypeError: Cannot redefine property: title throws at https://final-bugfix1-dev-ed.lightning.force.com/auraFW/javascript/dpJ3LUIaUXt-CtvrXqBcnQ/aura_prod.js:459:356

I have enabled Locker Service in my org with a lightning app and start getting above error. The initial error was related to loading the JQuery i.e Uncaught TypeError: Cannot read property 'expando' of undefined

Somehow this got resolved following: Unable to load jQuery in Salesforce Lightning Application after Summer '16 Release

But now stuck with this one. Any thoughts appreciated. Thanks

  • I'm also facing similar issue, salesforce.stackexchange.com/questions/128895/… – Suresh Kumar Jun 27 '16 at 14:43
  • Which version of jQuery are you using? – JF Paradis Jun 28 '16 at 20:53
  • I am using JQuery 2.2.4 version. Infact earlier i was using some older version JQuery version was getting following error: Uncaught TypeError: Cannot read property 'expando' of undefined. But after updating to 2.2.4 the above errors is no longer coming and but the new one as mention in this question. – Ashok Kumar Jun 30 '16 at 7:32
3

I am able to resolve this error, sharing details here.

After summer 16 release, we need to change the code to include the external JQuery/Css files from static resource. Here is an example of the same:

<ltng:require .... scripts="{!$Resource.JQuery}" />

Here JQuery is the static resource name, and this static resource is having only single JS File.

For a zip file having multiple files/folder follow another syntax:

<ltng:require ....  scripts="{!join(',', 
    $Resource.jsLibraries + '/jsLibOne.js', 
    $Resource.jsLibraries + '/jsLibTwo.js')}" />

More details you can find in following salesforce doc: https://developer.salesforce.com/docs/atlas.en-us.lightning.meta/lightning/js_libs_platform.htm

1

This error persists: "Uncaught TypeError: Cannot redefine property: title throws at .../aura_prod.js:459:356"

I've opened a separate thread for this.

0

This happens when you use old JQuery resource (previous releases from 2016 & earlier).

Use the latest version of Jquery.min.js as resource & issue will be resolved.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.