What can cause a persistent “Reload the page to get source for” error in firebug?

Question

I\'m trying to debug the javascript of a specific page, and I keep seeing

Reload the page to get source for page.htm in Firebug.

On Chrome, I\'m

Answer 1

I have tried all the answers described here, but for me the issue was something else.

I got the same message "Reload to see all sources" in firebug, and the Chrome debugger didn't display anything in the sources tab as well. I saw that the debugger was working on other pages for my website, so the problem was the page itself and after hours of sequentially deleting everything I had in the page, all that remained was an 'img' tag.

    <img src="#" />

It seems the src attribute should not contain "#", perhaps someone with a deeper understanding of HTML could explain this, but removing it has solved the problem for me.

Hopefully this will be of use to someone else as well.

Answer 2

I have this problem once.
the solve for me is the host name

page url: http://localhost
request url: http://192.168.0.1

Answer 3

I had the same issue, but had simply overlooked one obvious thing.

I had the noScript Firefox extension installed and hadn't enabled scripts from all the sources on the page, and it was blocking and causing that exact message persistently.

Answer 4

For the record, this can also happen if the certificate is jacked for https://www.xyz.com. You need to visit that site first and add a security exception.

Answer 5

With firebug icon, you'll see a dropdown arrow. Click that arrow to open up the drop down menu.

Click Clear Activation List.

Refresh the page now.

Now under script tab you'd see the Reload link. Click that to reload the page again. This time when the page reloads, you'd see the script.

Answer 6

This might help anyone who has encountered this message too.

I had this message too and could not get what the problem was. But then I had found it: My problem was that I hade some urls in an jQuery Ajax call that were just the ones from the hosting provider, not the actual domain name. With those urls all was fine during development. Then, after launching, the site was accessed by the new domain name. The mixture of the urls was the problem.

Strange was also that the GET url that was called via Ajax has worked in the regular browser url bar. Only in JS it did not work. Seems that I still have a knowledge deficit...