I have a problem with firebug. The css panel only shows the url of the loaded page instead the linked stylesheet with the corresponding row number. Any ideas what I do wrong? Please see enclosed screenshot.
System: Mac OS X Snow Leopard, Firefox 15.0.1, Firebug 1.10.3
I just updated Firebug to 1.10.4 on OSX 10.7.3 Firefox 15.0.1
Before the update it would show the linked css filename and corresponding line number in the Style tab. Now it just shows a long generated filename. See attached screen capture. The line numbers seem to be accurate but where the filename is coming from is anyone's guess.
HEY! Smack me up side the head. Every site that I visited before posting was one of mine (because I knew they worked before) and every one of them I had recently turned on "Allow Composite Files" in the CMS settings. So Firebug was accurately showing the filename of the composite file being generated by the CMS.
Turned off "Allow Composite Files" and Firebug shows the individual filenames.
Simple error on my part now that I figured it out but man, was that frustrating!
Hope this helps anyone else who may have the same issue. Keep Composite Files out of the equation until your site is completed.
> I had recently turned on "Allow Composite Files" in the CMS settings. So > Firebug was accurately showing the filename of the composite file being > generated by the CMS.
Thanks for the info, David! Clemens, do you use the same CMS with the same option enabled?
Hope this helps anyone else who may have the same issue.
By the way, the CMS that I'm using is DotNetNuke (DNN) and the setting "Allow Composite Files" creates one single CSS file from the multitude of CSS files associated with the particular DNN site. This enables a more efficient loading of pages but shouldn't be enabled until after your design phase is completed.
On Friday, October 12, 2012 9:18:25 AM UTC-4, David Wolters wrote:
> HEY! Smack me up side the head. Every site that I visited before posting > was one of mine (because I knew they worked before) and every one of them I > had recently turned on "Allow Composite Files" in the CMS settings. So > Firebug was accurately showing the filename of the composite file being > generated by the CMS.
> Turned off "Allow Composite Files" and Firebug shows the individual > filenames.
> Simple error on my part now that I figured it out but man, was that > frustrating!
> Hope this helps anyone else who may have the same issue. Keep Composite > Files out of the equation until your site is completed.
> David
> On Friday, October 12, 2012 4:23:23 AM UTC-4, Sebastian Zartner wrote:
>> It does this for every site I visit.
>> Really? What do you see when you visit https://www.getfirebug.com/ and >> inspect the slogan "The most popular and powerful web development tool"?
>> I see this using FF 16.0.1 + FB 1.10.4 on Win7:
sorry that I come back to the post only now. I still have the same problem. The external stylesheet (in my case styles.css) with corresponding line number is not shown in the firebug window. I don't think it is the same problem as David's because on my macbook air firebug has the problem with showing the style sheet with row number wheras my firebug on my desktop mac pro is showing the stylesheet with corresponding row number correctly. Do you have any idea what to do?
Thank you
Clemens
Am Samstag, 13. Oktober 2012 17:40:09 UTC+2 schrieb Sebastian Zartner:
> I had recently turned on "Allow Composite Files" in the CMS settings. So >> Firebug was accurately showing the filename of the composite file being >> generated by the CMS.
> Thanks for the info, David! Clemens, do you use the same CMS with the same > option enabled?
> Hope this helps anyone else who may have the same issue.
you didn't answer my previous questions yet. So do you use a CMS like DotNetNuke? Did you check the responses inside the *Net* panel? Also, do you have a public URL, so I can reproduce what you see?
On Thursday, November 29, 2012 2:04:52 PM UTC+1, Clemens Heilmann wrote:
> Hello Sebastian,
> sorry that I come back to the post only now. I still have the same > problem. The external stylesheet (in my case styles.css) with corresponding > line number is not shown in the firebug window. I don't think it is the > same problem as David's because on my macbook air firebug has the problem > with showing the style sheet with row number wheras my firebug on my > desktop mac pro is showing the stylesheet with corresponding row number > correctly. Do you have any idea what to do?
> Thank you
> Clemens
> Am Samstag, 13. Oktober 2012 17:40:09 UTC+2 schrieb Sebastian Zartner:
>> I had recently turned on "Allow Composite Files" in the CMS settings. So >>> Firebug was accurately showing the filename of the composite file being >>> generated by the CMS.
>> Thanks for the info, David! Clemens, do you use the same CMS with the >> same option enabled?
>> Hope this helps anyone else who may have the same issue.
- I am currently developing a magento based shop; I don't use DotNetNuke - I did open the Net panel of firebug but I have no idea what to look for - Url of our test site is as follows: http://magento.p148901.webspaceconfig.de/
I did deinstall firefox with all extensions and profiles and reinstalled firefox 17 plus firebug and 1Password. Still no stylesheet reference with firebug.
Hope you can help somehow.
Thanx
Clemens
Am Donnerstag, 29. November 2012 15:20:18 UTC+1 schrieb Sebastian Zartner:
> you didn't answer my previous questions yet. So do you use a CMS like > DotNetNuke? Did you check the responses inside the *Net* panel? > Also, do you have a public URL, so I can reproduce what you see?
> Sebastian
> On Thursday, November 29, 2012 2:04:52 PM UTC+1, Clemens Heilmann wrote:
>> Hello Sebastian,
>> sorry that I come back to the post only now. I still have the same >> problem. The external stylesheet (in my case styles.css) with corresponding >> line number is not shown in the firebug window. I don't think it is the >> same problem as David's because on my macbook air firebug has the problem >> with showing the style sheet with row number wheras my firebug on my >> desktop mac pro is showing the stylesheet with corresponding row number >> correctly. Do you have any idea what to do?
>> Thank you
>> Clemens
>> Am Samstag, 13. Oktober 2012 17:40:09 UTC+2 schrieb Sebastian Zartner:
>>> I had recently turned on "Allow Composite Files" in the CMS settings. So >>>> Firebug was accurately showing the filename of the composite file being >>>> generated by the CMS.
>>> Thanks for the info, David! Clemens, do you use the same CMS with the >>> same option enabled?
>>> Hope this helps anyone else who may have the same issue.
1. You normally don't have to completely reinstall Firefox to fix a problem. Simply creating a new profile<https://getfirebug.com/wiki/index.php/Install_Firebug_into_a_clean_pr...>often already does it. 2. From your screenshot it looks like the CSS gets merged into the HTML (via <style> tags). I explained this in more detail in the other thread<https://groups.google.com/forum/#!topic/firebug/utchKQx2T4g/discussion>I mentioned earlier, though accessing your page I can't see that. There's probably an option within Magento controlling this like for DotNetNuke, but I don't have any experience with that. Below is what I see when inspecting the main image inside your page. 3. Do you see this also at other pages than your shop? E.g. on getfirebug.com? 4. You have several ways to check where the CSS is actually coming from: 1. Right-click into the page and choose *View Page Source* (*Seitenquelltext anzeigen* in German). In the window that opens search for one of the styles you see inside the *Style* side panel<https://getfirebug.com/wiki/index.php/Style_Side_Panel>. (According to your screenshot e.g. vertical-align.) 2. Switch to the *Net* panel<https://getfirebug.com/wiki/index.php/Net_Panel>, reload the page and set the *CSS* filter. If the CSS isn't merged into the HTML, there should be 15 requests (see the screenshot below). If you can't see them, switch the filter back to *All* and search for one of the styles. 3. Inside the *HTML* panel<https://getfirebug.com/wiki/index.php/HTML_Panel>search for style and you'll probably find several <style> tags inside your HTML containing all the styles.
With all that information given you should be able to find out where the problem lies.
Currently, I am working on my mac pro with same firefox 17 and same firebug 1.10.6. When I load here the page I provided to you the stylessheet with row numbers is correctly shown (see attached screenshot). I would take that as a hint it has something to do with the firebug settings...
The problems with my macbook air not showing the stylesheet with the corresponding row number are caused by my umts provider vodafone or my wlan router Huawei E5. I just started firebug on my macbook using my wlan at home (network provider kabeldeutschland) and everything is fine: the correct stylesheet with corresponding row number is shown.
I will now look how to setup the vodafone connection to overcome the problem when I am not at home. I already read in another forum that vodafone somehow seems to compress the data somehow.
Thank you
Clemens
Am Freitag, 30. November 2012 09:55:19 UTC+1 schrieb Clemens Heilmann:
> Currently, I am working on my mac pro with same firefox 17 and same > firebug 1.10.6. When I load here the page I provided to you the stylessheet > with row numbers is correctly shown (see attached screenshot). I would take > that as a hint it has something to do with the firebug settings...
thanks for the feedback and your investigations. Now that you say that your UMTS connection is responsible for that I remember I already heard something similar some years ago. I'll add this to our FAQ.
On Friday, November 30, 2012 11:30:02 PM UTC+1, Clemens Heilmann wrote:
> Hello Sebastian,
> the problem is solved.
> The problems with my macbook air not showing the stylesheet with the > corresponding row number are caused by my umts provider vodafone or my wlan > router Huawei E5. I just started firebug on my macbook using my wlan at > home (network provider kabeldeutschland) and everything is fine: the > correct stylesheet with corresponding row number is shown.
> I will now look how to setup the vodafone connection to overcome the > problem when I am not at home. I already read in another forum that > vodafone somehow seems to compress the data somehow.
> Thank you
> Clemens
> Am Freitag, 30. November 2012 09:55:19 UTC+1 schrieb Clemens Heilmann:
>> Thank you Sebastian,
>> I will check your advice on my macbook air.
>> Currently, I am working on my mac pro with same firefox 17 and same >> firebug 1.10.6. When I load here the page I provided to you the stylessheet >> with row numbers is correctly shown (see attached screenshot). I would take >> that as a hint it has something to do with the firebug settings...
On Sunday, December 2, 2012 4:36:20 PM UTC+1, Sebastian Zartner wrote:
> Hello Clemens,
> thanks for the feedback and your investigations. Now that you say that > your UMTS connection is responsible for that I remember I already heard > something similar some years ago. > I'll add this to our FAQ.
> Sebastian
> On Friday, November 30, 2012 11:30:02 PM UTC+1, Clemens Heilmann wrote:
>> Hello Sebastian,
>> the problem is solved.
>> The problems with my macbook air not showing the stylesheet with the >> corresponding row number are caused by my umts provider vodafone or my wlan >> router Huawei E5. I just started firebug on my macbook using my wlan at >> home (network provider kabeldeutschland) and everything is fine: the >> correct stylesheet with corresponding row number is shown.
>> I will now look how to setup the vodafone connection to overcome the >> problem when I am not at home. I already read in another forum that >> vodafone somehow seems to compress the data somehow.
>> Thank you
>> Clemens
>> Am Freitag, 30. November 2012 09:55:19 UTC+1 schrieb Clemens Heilmann:
>>> Thank you Sebastian,
>>> I will check your advice on my macbook air.
>>> Currently, I am working on my mac pro with same firefox 17 and same >>> firebug 1.10.6. When I load here the page I provided to you the stylessheet >>> with row numbers is correctly shown (see attached screenshot). I would take >>> that as a hint it has something to do with the firebug settings...
