5 May 2011 11:16 PM #1
Good morning everyone
6 May 2011 1:21 AM #2
This is expected if you have "?nocache" in your URL and it is a sad side-effect. A better approach is to turn off caching in Firebug (the Net tab has a dropdown menu w/Disable Browser Cache).
Are you seeing this w/o "?nocache"?
6 May 2011 1:26 AM #3
I need to test this out. From what I understand, firebug treats the JS files with arguments as different files, and that's why breakpoints disappear.
6 May 2011 2:08 AM #4
6 May 2011 8:10 AM #5
You are correct: different URL = different File (URL includes query parameters). I don't see the "?dc" parameter on script tags unless I add "?nocache" to the page URL. But perhaps there are other reasons for the Loader to decide to add the "?dc" parameter... I'll have to look at the code.
6 May 2011 8:16 AM #6
12 Jul 2011 5:47 AM #7
Any tips how to disable this _dc parameter from appending to my controller's url? I can't debug it during the load because of that...
Also, my loader is like this, so either disableCaching is not working or there is a bug somewhere:
12 Jul 2011 10:19 PM #8
Have you tried disableCaching: false?
_dc = disableCache
So false should turn off this feature. Once off, the Firebug trick will be important to avoid stale responses from the Firefox cache.
Chrome, sadly, has no such feature, which means you will either have to clear the entire cache often, or set this option to true and use "debugger" statements. Sad indeed
5 May 2012 2:38 AM #9
I'm having exactly the same issue on both Firefox and chrome, while testing my sencha touch 2 app. One of my controller (the one i'm editing) is getting "_dc" and a number append after it's name and every time I reload the page, the number changes. so no way to keep a breakpoint in the controller. However the fix proposed by dongryphon is working !
Add this before your app code :
7 May 2013 1:57 AM #10
While debugging with NetBeans, I've had this problem also.
FYI, Netbeans has just filled in an issue in order to be able to debug whatever this ExtJS config is
And at last, when putting disableCaching to false, it becomes hard to debug as everything is kept in the cache of the browser
You have several plugins for that to disable cache on browser side, but there's another option, which seems better (because no need to reload the browser)
you put a livereload server that forces the browser to update the .js files whenever they get modified
(AFAIK, I use grunt and grunt-livereload for that)
Hope this helps
By dawesi in forum Community DiscussionReplies: 0Last Post: 10 Jan 2008, 8:40 PM
By Zakaroonikov in forum Community DiscussionReplies: 2Last Post: 2 Aug 2007, 1:48 PM