sc456a

Just checking in, @gantry. Right now my priority is getting pages/posts working again so we can use tools like the Divi Builder. The conflict with Yoast is a little easier to work around but we can’t use Divi without disabling Gantry which of course breaks the entire site.

Mind chiming back in here, @newkind @gantry? We’re in a pretty bad place right now. Gantry is conflicting with RokSprocket, Yoast, and Divi – and probably others. We need to get this fixed ASAP or we’re all going to have a lot of angry clients on our hands.

Any updates on this? @tiiunder, I saw in your Yoast forum post that you see the conflict with RokSprocket, which I’m seeing now as well.

This really needs to be properly resolved and it’s going to have to be by the Rockettheme team.

Quick addition – this conflict breaks the very popular Divi Builder plugin as well, making it a bit more serious.

Ouch.

Have you thought about contacting Yoast and asking them to resolve the conflict on their end?

Thanks!

Ah, OK. Missed that. It was working before but stopped with the recent Woocommerce 3.x update. Thanks!

Please see my original post. There are no console errors. I’m using the default WP theme and no plugins are active.

This question has been open for over two weeks and zero progress has been made. Others are having the same issue and you haven’t provided any troubleshooting steps for anyone. You’ve asked us to disable plugins/themes several times despite my having done that already and stating as much in the original post.

I’ve gone to a lot of effort, including the creation of a staging site, to help resolve this issue. I think we’d all appreciate a little more effort on your part.

I would love an answer to this as well. We’ve got the plugin setup on several sites and will have to find an alternative if the maps won’t load.

Using my link in the OP, there are no errors in the console and yet the map doesn’t appear.

Any update on this? My link was included in the OP.

“Location not found” in admin.

Yes and none. See original post.

The updated Github code fixed the issue on my server as well, but it would be great if it could be folded into an update. Thanks!