Title: [Plugin: Multi-column Tag Map] Javascript conflict?
Last modified: August 20, 2016

---

# [Plugin: Multi-column Tag Map] Javascript conflict?

 *  [pricklepantz](https://wordpress.org/support/users/pricklepantz/)
 * (@pricklepantz)
 * [13 years, 9 months ago](https://wordpress.org/support/topic/plugin-multi-column-tag-map-javascript-conflict/)
 * Helo, I’m able to pull and place in mega menu. but it seems the js conflict with
   theme’s js as it now has 2 search box.
    I hv no idea why.
 * Please check screen shot here
    [http://i.minus.com/i7FjzSs9Ldclr.jpg](http://i.minus.com/i7FjzSs9Ldclr.jpg)
 * [http://wordpress.org/extend/plugins/multi-column-tag-map/](http://wordpress.org/extend/plugins/multi-column-tag-map/)

Viewing 1 replies (of 1 total)

 *  Plugin Author [tugbucket](https://wordpress.org/support/users/tugbucket/)
 * (@tugbucket)
 * [13 years, 9 months ago](https://wordpress.org/support/topic/plugin-multi-column-tag-map-javascript-conflict/#post-2975616)
 * You tagged this post for the plugin in Multi-column Tag Map. Sounds like you 
   need to tag it for Mega Menu.

Viewing 1 replies (of 1 total)

The topic ‘[Plugin: Multi-column Tag Map] Javascript conflict?’ is closed to new
replies.

 * ![](https://s.w.org/plugins/geopattern-icon/multi-column-tag-map_9e2525.svg)
 * [Multi-column Tag Map](https://wordpress.org/plugins/multi-column-tag-map/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/multi-column-tag-map/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/multi-column-tag-map/)
 * [Active Topics](https://wordpress.org/support/plugin/multi-column-tag-map/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/multi-column-tag-map/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/multi-column-tag-map/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [tugbucket](https://wordpress.org/support/users/tugbucket/)
 * Last activity: [13 years, 9 months ago](https://wordpress.org/support/topic/plugin-multi-column-tag-map-javascript-conflict/#post-2975616)
 * Status: not resolved