William P. Davis
will.davis at gmail.com
Sun Dec 16 02:27:33 UTC 2012
Chrome dev tools are fantastic for this as well - better than Firebug, I'd say. Both will give you the line number in the script where the failure occurred, and at least Chrome allows you to click on that to be taken directly to the error.
Sent from my BlackBerry
From: Daniel Fenn <danielx386 at gmail.com>
Sender: wp-hackers-bounces at lists.automattic.com
Date: Sun, 16 Dec 2012 13:21:43
To: <wp-hackers at lists.automattic.com>
Reply-To: wp-hackers at lists.automattic.com
I don't know if you tried this but if you got firefox installed, you may
want to look at firebug.
Also if you think that there may be some caching going on, I would try
pressing Ctrl F5 to do a force refresh..
On Sun, Dec 16, 2012 at 1:13 PM, Dobromir Yordanov <dyordan1 at ramapo.edu>wrote:
> Hey guys and gals,
> Anyone know of a good way to find out what JS function is responsible for
> a certain behavior other than going through the JS files and trying to
> guess? I'm trying to patch up some JS bugs on Wordpress and it seems a bit
> trickier than PHP patching. Also, whatever I change doesn't seem to be
> reflected when I reload so I'm guessing some caching kicks in (other than
> my browser's which should be disabled). Any ideas how to get around that?
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
wp-hackers mailing list
wp-hackers at lists.automattic.com
More information about the wp-hackers