Home/ Questions/Q 8141425
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-06T12:30:14+00:00

Okay I’ve been doing JS merges for some time now and still can’t figure

  • 0

Okay I’ve been doing JS merges for some time now and still can’t figure out the logic behind making a successful merge. It comes down to repositioning libraries upwards and downwars on merge list. Sometimes jquery must be on top, sometimes it doesn’t. Sometimes fancybox needs to be added as addJs, sometimes as addItem.

So, what is in your experience causing JS libraries to break when you use Magento’s merge JS? Are there any rules for sucessful merge?

UPDATE: Just now in my local.xml I moved from

<action method="addItem"><type>skin_js</type><name>js/magiczoomplus.js</name></action>

to 

<action method="addJs"><script>jquery/magiczoomplus.js</script></action>

and that solved the magiczoomplus error I was getting on the page. How so?

I’m trying to understand this problem so I can better tackle it in the future

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    you need to understand the core principle here what conflicts between javascript libraries and what not.

    in case of jQuery and Prototype conflict and in Magento:

    • always include jQuery before any other script on your page , before Prototype is a must
    • add jQuery.noConflict(); call directly to the end of your jQuery library file
    • make sure that none of your jQuery based scripts are not using $ as method name (essence of the conflict here)
    • 0