New to the community? Start here

Google Maps conflict with Hide Broken Shortcodes

When Hide Broken Shortcodes is activated, Google Maps do not show up at all in any theme, even Twenty Eleven.

Is there any way to fix this?

Tue, 9 Oct 2012 19:03:15
  • Specialist
    • Design Lord, Child of Thor

    Hi aecnu,

    Hide Broken Shortcodes is a WordPress plugin which hides the shortcodes when the plugin which the shortcode refers to is deactivated or uninstalled.

    Timothy – the only way to solve the conflict was to deactivate the Hide Broken Shortcodes plugin which is a shame because I find it pretty useful when developing large sites and testing plugins.

    If someone could figure out how to get the WPMUDEV Google Maps plugin and the Hide Broken Shortcodes plugin to play nicely with one another that would be great!

    Hide Broken Shortcodes does not seem to affect other plugins which is why I posted here.

  • aecnu
    • WP Unicorn

    Greetings Specialist,

    Thank you for the great informative reply, it is certainly appreciated and enlightening as well.

    If someone could figure out how to get the WPMUDEV Google Maps plugin and the Hide Broken Shortcodes plugin to play nicely with one another that would be great!

    It never hurts to ask and maybe the lead developer of the Google Maps plugin will be interested in this as well. I am not a coder or I would consider trying to figure it out myself.

    Therefore I will see if I can get the lead developer in here with his invaluable insight into this plugin for his advice/advise for us.

    Though this may take a bit longer then a normal ticket, I will try to get him in here asap.

    Cheers, Joe

  • Vladislav
    • Dead Eye Dev

    Hi,

    I think I have managed to track the conflict down to a bit of overzealous regular expression matching in “Hide Broken Shortcodes” plugin – basically, it detected a javascript array as “false positive” for a broken shortcode. Fortunately, if I got everything right, we can fix the conflict from our side. The attached update worked nicely for me, can you please give it a spin and see if it solves the issue for you too?