[Mitch]

I’m honestly not sure if this conflict is related to the base plugin or the template, so I thought I’d start here.

When activating the new RC1 of WooCommerce 2.1, with Connections 0.7.9.3 and CMap 3.1 active, makes it so that any click on the Bio or Notes link jumps to the top of the page, never actually opening the Bio/Info window.

Can you think of anything I can from your end do to resolve this?

Thanks.

[Steven Zahm]

@ Mitch

Sounds like there is a javascript causing a fatal error. This will break every script being loaded after the error occurs. Load the page up in Chrome, hit the F12 key and then click the Console tab to see the page render error.

[Mitch]

I’m not sure exactly what it means, but I recognize an error (406) from a previous problem with WooCommerce. Their integration with Genesis isn’t even working right right now. I’m going to wait until they move past beta and RC1 to try and resolve this issue.

I’ll then make the code change that fixed the old version, and see if it fixes this issue too.

I will update here if/once I get it resolved.

Thanks for pointing me in the right direction.

[Steven Zahm]

@ Mitch

Hmm, that is just the a server error, that should prevent the javascript from working unless the 406 relates to the loading/serving of a javascript file. If it is page I can get to, I’d be happy to take a quick look.

[Mitch]

If I recall, there was a security conflict between WC and my host based on the naming of some files, throwing the 406 and creating havoc in other items. I had hoped they’d fix it in 2.1, but it looks like I’ll need to find and insert the code mods so the host and WC play nice together.

I’m going to wait until final release, load it on the sandbox, and see if that resolves. At that point, I’ll know more.

I had just forgotten about this mod being needed, and I am hoping that is what caused the Connections error. They are supposed to release a final 2.1 this month, so I’ll let you know as soon as I do.

Thanks again for your prompt reply.

[Mitch]

OK, so this was bugging me too much to wait for the final release. I found the old code, and applied the mod to the WC RC1, and it worked to resolve the error.

This was an across the board js error, based on the host’s conflict with the naming of a js file in WC. Silly stuff, really.

This error had nothing to do with Connections or CMap.

Keep up the good work! :)

[Steven Zahm]

@ Mitch

Curious, what exactly is the conflict and the fix?

[Mitch]

Easiest explained in the link I re-found. It is here:

http://docs.woothemes.com/document/jquery-cookie-fails-to-load/

WC blames it on host. Host says it will not modify for security reasons. Best way is for me to just mod code.

Your comment about js fatal error triggered my memory of having to do this previously.

Thanks.

[Steven Zahm]

@ Mitch

ahhh… modsec, yes, now I remember another user having the same issue. I bet they’re using WC too.

Honestly, if renaming the file is the “fix” to get around the rule … well, my opinion is WC should just rename the file themselves so no users run into this issue. That’s what I would do. Stuff is just supposed to work, right? :)

[Author]

Posts