munchkin.js - jQuery 1.9 compatibility

[Anonymous]

Hi there,

recently updated my jQuery to 1.9.2, now I see this

Uncaught TypeError: Cannot read property 'version' of undefined

munchkin.js:21

is munchkin.js known to work with jQuery 1.9.x and 1.9.2 specifically?

[Anonymous]

I received this response back from Marketo:

"Both the production and beta versions no longer have any dependency for jQuery" so the original poster shouldn't have any issues anymore.

[Anonymous]

Is there any chance someone from Marketo can answer my question above please?

[Anonymous]

Do you have a version of Marketo that doesn't require jQuery or doesn't download it's own version of jQuery?

We have jQuery 1.10.2 already on the page and Marketo is doing another http request for 1.7.1.

As a third party service I don't see why you need to do this or why you rely on a 3rd party library like jQuery.
We use optimizely for A/B testing and they let you build a version without jQuery bundled.

[Anonymous]

Standard jQuery plugin should be provided to all as soon as possible. It's been about an year since jQuery 1.9 was released. 

[Anonymous]

Hi Adam,

The version of Munchkin you use doesn't have any impact on jQuery compatibility. However, we do have a beta version which has been very stable and is compatible with 1.9. If you're interested, send me an email at erik@marketo.com and I'll give you the instructions.

[Anonymous]

One of our clients has jQuery 1.9.0 on their site and as we cannot see any anonymous leads in Web Analytics, I think we are suffering from the same issue here.

Is this just an issue when using the Asynchronous jQuery tracking code? Will downgrading to the Asynchronous (or even Simple) code work? Or is the only option (other than downgrading jQuery on the website) to include the migrate plugin?

Thanks in advance for any advice on this.

[Anonymous]

We are using jQuery 1.9 and ran into problems with munchkin.js. We tried the jQuery migrate plugin but that caused other compatibility issues. I'd like to ask Marketo to hurry up with updating munchkin.js to be compatible with jQuery 1.9 and beyond, since this issue seems to be affecting quite a few clients.

[Anonymous]

We just went through an exercise this week where we tried using the Beta Munchkin code. I just wanted to give folks a heads up. There is a bit of a catch-22 in using the beta.

The Beta is not backward compatible with the current Munchkin code. The standard Marketo landing pages use the current code. So the cookies on the website and those on the landing pages don't play nicely together leading to lack of tracking across all pages. If you replace the footer on the landing page templates with the Munchkin beta reference, then you loose the form pre-fill (and therefore progressive form) capabilities.

In the end, the company went back to the external web design company and paid them to redo the code so it would work with jquery 1.8. Of course, Ken's migrate answer above might have worked, but the web design company was already working on porting it backward.

[Anonymous]

Rencently encountered this problem while using Marketo with jQuery 1.9.1.  I was able to get around it by using the jQuery migrate plugin.  Seems to have fixed it.  We actually used jQuery 1.10.1 with the 1.2.1 migrate plugin.

<script src="scripts/jquery-1.10.1.js" type="text/javascript"></script>
<script src="scripts/jquery-migrate-1.2.1.js" type="text/javascript"></script>

Try it out and post your results back here.

[Anonymous]

I think we have run into the 1.9 issue at Get Satisfaction. Does it make sense that the _mkto_trk cookie is being set but there is information on web page visits being logged in Marketo?

I did email Erik to find out about the beta availability.

Is there another way to manage the jquery conflict besides using the beta?

Thanks for any hints.

[Anonymous]

I would also like to request that munchkin.js be updated as soon as possible. We are currently loading the jquery migrate plugin on our site only for the tracking code.

[Anonymous]

Hmm, not that I know of. Although I'm not exactly a Javascript master.

I did send you the beta however.

[Anonymous]

Is there some way to disable the code programmatically if there is a problem like this?  We are running into this now and this is affecting our end users.  I would rather not have to change the code if there is a problem (i.e. use a try catch clause).

[Anonymous]

I think it should be made clearer on the Munchkin Page that there is a dependency on Jquery - with reference to supported versions.

I had no idea, and lost a couple of days of tracking data because I missed the error.

[Anonymous]

Hey all,

We just created a beta version of Munchkin that supports 1.9. If you're interested in trying it please email me at erik@marketo.com

-Erik

[Anonymous]

Any updates on this?

[Anonymous]

We're testing a 1.9 version, but as Craig mentions they really changed the library in that update. I don't have a firm ETA yet, but we were thinking of making a beta available as the first step.

We won't update the Marketo hosted one until Munchkin fully supports the new version.

[Anonymous]

No idea.  Just happened to catch a thread yesterday morning regarding this, and I think it was Erik that assured us that the marketo hosted file would remain older version until they were sure nothing would break.

[Anonymous]

ah thank you, in the process of rolling back to jQuery 1.8.x

would you happen to know when/if an update to be 1.9+ compatible might be expect?

[Anonymous]

No.  1.9/2.0 killed off a bunch of deprecated elements, browser.version being one of them.  Reference the marketo store of jquery, they will make sure it doesn't update past a breaking point, or just roll back to your own hosted last working version files.  Don't reference the google or jquery hosted most recents.