sp.init.js - JavaScript Error in Previously Working Item Display Template

Hi - I've run to an issue after applying the April 2015 Cumulative Update. I am working on a VM for training and testing purposes using SharePoint 2013 with SP1. No previous CU's have been previously applied, April 2015 was the only CU since SP1 was applied in mid 2014.

The error I am receiving in a previously working item display template is:

Object doesn't support property or method 'split' (CoreRender: ~sitecollection/_catalogs/masterpage/Display Templates/Content Web Parts/Item_SmallPicture.js)

Where Item_SmallPicture.js is my display template.

The template uses the CSWP which returns pictures using a custom content type - the field that is causing the issue is a custom field that allows users to add a hyperlink to an image which in turns clicks off to another website or other content. Its really just a simple hyperlink filed in the content type list.

There has been no programming (code) changes in the environment. The problem presented itself only AFTER the April 2015 CU was applied but could have been introduced had an earlier CU been applied.  

Using MSIE debugger I was able to determine the sp.init.js is where the issue is happening. As a trouble shooting method I took the updated sp.init.js from th VM that had the April 2015 CU applied and the sp.init.js from a VM that had not had the CU applied.

The updated file that produces the error:

SP.ScriptHelpers.getDocumentQueryPairs = function() {
    ULSVCK:;
    var a = window.self.ajaxNavigate,
        b = a.get_search();
    return SP.ScriptHelpers.getUrlQueryPairs(b)
};


The original file that works without error:

SP.ScriptHelpers.getDocumentQueryPairs = function() {
    ULSVCK:;
    var a = window.self.ajaxNavigate,
        b = a.get_href();
    return SP.ScriptHelpers.getUrlQueryPairs(b)
};


As you can see the b = a.get is different. Another interesting thing about this is the whole reason I applied the CU was to correct for the known issue in the Enterprise Search Center for double encoded URLS.

Any ideas or help in how to correct this would be greatly appreciated.

Thank you,
JCrowe