this is an oversight of module/skin developers who incorrectly assumed jquery/jquery-migrate would always be registered rather than using the correct API's (http://www.dnnsoftware.com/wiki/page/jquery). As part of 7.3.0's performance optimization (http://www.dnnsoftware.com/wiki/page/dnn-7-3-developer-quick-start) there are a few cases where jquery-migrate is no longer loaded as it was not needed (e.g. on a default install with no new modules when a user was logged out, this used to be loaded for no reason, so we removed that).

That said, there were a number of skinners/module developers who correctly registered jquery, but did not register jquery migrate. The issue there is that jquery broke aspects of the API with the 1.9.1 release, so this has stung those developers. As jquery breaking the API so much was not a predictable event, we (platform team) thought that it would be better if we registered jquery-migrate on their behalf for the occasions where they only registered jquery. Whilst this is not ideal, as some users will now load jquery-migrate even though nothing on the page needs it, the other option was to not add this back in and that would need lots of updates to skins and modules. As such adding it back (which restores it to pre 7.3.0 like behaviour), was seen as the lesser of two evils - the fix was made as https://dnntracker.atlassian.net/browse/DNN-5497 and will come out in the expedited 7.3.1 release.

---

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US

you should only need the first as that skin object registers both jquery and jquerymigrate . The 2nd is unnecessary, but as both use the client dependency framework (CDF) API, it simply means that while jquery/jquerymigrate etc have multiple register requests, CDF will remove the duplicates and ensure each script is only added to the page once. This of course means that when you update to 7.3.1, CDF will also remove those duplicates

---

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US