That was my best guess at what “TypeError: undefined is not an object (evaluating ‘c.localized._disabled’)” was referring to. BrowserDetect would also use variable names like that, you’re right.
The offending script originates when the function loadCzr fires in tc-scripts.js – that appears to be Customizr causing a problem – it’s looking to see if the variable “c.localized._disabled” is set but it claims localized._disabled isn’t valid and hasn’t been declared yet.
Here’s the GitHub for that plugin:
https://github.com/presscustomizr/customizr/search?utf8=?&q=localized._disabled&type=Code
In that case, localized is actually probably referring to the use of wp_localize_script() in PHP, namely – the Javascript is set to accept variables that WordPress localizes into Javascript.
* Constructors and methods can be disabled by passing a localized var TCParams._disabled (with the hook ‘tc_disabled_front_js_parts’ )
193 * Ex : add_filter(‘tc_disabled_front_js_parts’, function() {
I haven’t got much farther than that yet. d4z_c0nf – you might be onto something with Modernizr or missing JS files – I’m not really used to working with FancyBox, just adding to the conversation.
Hope this helps!