Firebug 1.13.0a10 on Firefox 29 (beta) console.log not showing
5,412 views
Skip to first unread message
neongrau
Apr 10, 2014, 9:30:36 AM4/10/14
to fir...@googlegroups.com
Since i've switched to Firefox 29 Firebug is not showing any console logs anymore.
While the builtin developer console of FF is working fine, Firebug stays silent.
I can manually write a console.log statement in Firebug's command line which gets shown but none from the page i loaded.
When i uninstall Firebug and reinstall it'll momentarily work until first time i reload the page.
I've tried starting from scratch with a new profile (i've imported bookmarks, history and passwords from old one) but that didn't help either.
Anything i can do to get the console logs back?
Jan Honza Odvarko
Apr 10, 2014, 9:40:08 AM4/10/14
to fir...@googlegroups.com
> Anything i can do to get the console logs back?
Does Firebug 2.0 alpha 2 work for you?
https://blog.getfirebug.com/2014/04/04/firebug-2-0-alpha-2/
If you create a new Firefox profile, does it help?
https://getfirebug.com/wiki/index.php/Install_Firebug_into_a_clean_profile
(to avoid collision with another extension)
Honza
https://blog.getfirebug.com/2014/04/04/firebug-2-0-alpha-2/
If you create a new Firefox profile, does it help?
https://getfirebug.com/wiki/index.php/Install_Firebug_into_a_clean_profile
(to avoid collision with another extension)
Honza
Sebastian Zartner
Apr 11, 2014, 2:45:37 AM4/11/14
to fir...@googlegroups.com
> Anything i can do to get the console logs back?
Does Firebug 2.0 alpha 2 work for you?
https://blog.getfirebug.com/2014/04/04/firebug-2-0-alpha-2/
Note that Firebug 2.0a2 just works with Firefox 30.0+.
If you create a new Firefox profile, does it help?
https://getfirebug.com/wiki/index.php/Install_Firebug_into_a_clean_profile
(to avoid collision with another extension)
As I read from the original post this was already tried out.
For me it's working fine using FF 29.0 + FB 1.12.8 on Win7.
neongrau, which Firebug version and OS are you using? Do you have any other extensions installed in your new profile? Could you provide a screenshot of both, Firebug and the built-in console?
Sebastian
For me it's working fine using FF 29.0 + FB 1.12.8 on Win7.
neongrau, which Firebug version and OS are you using? Do you have any other extensions installed in your new profile? Could you provide a screenshot of both, Firebug and the built-in console?
Sebastian
Grassboy Wu
Apr 30, 2014, 2:57:07 AM4/30/14
to fir...@googlegroups.com
here is a screenshot...
when I invoke a console.log() and press ctrl+shift+k
the message should be displayed in firebug was shown in Firefox 29's Console
but I don't know if this is firebug's bug
or this should be firefox's bug
Jan Honza Odvarko於 2014年4月10日星期四UTC+8下午9時40分08秒寫道：
Lenny Maclean
Apr 30, 2014, 5:05:41 AM4/30/14
to fir...@googlegroups.com
I'm having the same problem. Installed Firefox v29. The native Firefox dev tools shows the console logs but not firebug :(
Jan Honza Odvarko
Apr 30, 2014, 7:04:54 AM4/30/14
to fir...@googlegroups.com
I can't see the problem on my machine. Could you please provide detailed instructions about what exactly to do? (what url to load, what buttons to press, etc.)
For example: does this test work for you?
https://getfirebug.com/tests/head/console/api/log.html
Honza
For example: does this test work for you?
https://getfirebug.com/tests/head/console/api/log.html
Honza
Yves Van Broekhoven
Apr 30, 2014, 7:36:01 AM4/30/14
to fir...@googlegroups.com
I'm seeing the same problem.
Browser specs:
Installed addons:
When I visit for example http://google.com, and use console.log, it works. After refreshing the page, it gives me 'undefined':
Does this give you enough info?
Yves
Sasquach
Apr 30, 2014, 7:43:10 AM4/30/14
to fir...@googlegroups.com
How to reproduce bug:
1. go to https://getfirebug.com/tests/head/console/api/log.html
2. open firebug and click "Execute Test"
3. everything works fine now
4. now refresh page with firebug open
5. click "Execute Test"
6. message won't appear in firebug console...
7. ... but open firefox native tools - there's our message
1. go to https://getfirebug.com/tests/head/console/api/log.html
2. open firebug and click "Execute Test"
3. everything works fine now
4. now refresh page with firebug open
5. click "Execute Test"
6. message won't appear in firebug console...
7. ... but open firefox native tools - there's our message
Álvaro G. Vicario
Apr 30, 2014, 7:47:27 AM4/30/14
to fir...@googlegroups.com
El jueves, 10 de abril de 2014 15:30:36 UTC+2, neongrau escribió:
Since i've switched to Firefox 29 Firebug is not showing any console logs anymore.
Same switch, same issue. In my case, console messages divide between Firebug and Firefox console. Test code:
<!doctype html>
<html>
<head><title>Test</title>
<meta charset="iso-8859-1">
<script type="text/javascript" src="http://ajax.googleapis.com/ajax/libs/jquery/1/jquery.min.js"></script>
<script type="text/javascript"><!--
/**/console.log("jQuery/%s is ready", jQuery().jquery);
jQuery(function($){
console.log("Document ready");
});
//--></script>
</head>
<body>
</body>
</html>
"jQuery/1.9.1 is ready" goes to Firebug. "Document ready" goes to Firefox (if enabled) or gets lost (if disabled).
Whoever figures out a workaround will be my hero.
Jan Honza Odvarko
Apr 30, 2014, 8:04:10 AM4/30/14
to fir...@googlegroups.com
On Wednesday, April 30, 2014 1:36:01 PM UTC+2, Yves Van Broekhoven wrote:
I'm seeing the same problem.Browser specs:Installed addons:
I still can't reproduce the problem.
Can you disable the addons you have installed?
Perhaps there is a collision (especially 1password, I recall there was a problem related to this one).
You can also create a new profile, but make sure 1password (or any other extension) isn't installed automatically even into the new profile.
https://getfirebug.com/wiki/index.php/Install_Firebug_into_a_clean_profile
Honza
Can you disable the addons you have installed?
Perhaps there is a collision (especially 1password, I recall there was a problem related to this one).
You can also create a new profile, but make sure 1password (or any other extension) isn't installed automatically even into the new profile.
https://getfirebug.com/wiki/index.php/Install_Firebug_into_a_clean_profile
Honza
Jan Honza Odvarko
Apr 30, 2014, 8:05:27 AM4/30/14
to fir...@googlegroups.com
On Wednesday, April 30, 2014 1:43:10 PM UTC+2, Sasquach wrote:
How to reproduce bug:
1. go to https://getfirebug.com/tests/head/console/api/log.html
2. open firebug and click "Execute Test"
3. everything works fine now
4. now refresh page with firebug open
5. click "Execute Test"
6. message won't appear in firebug console...
7. ... but open firefox native tools - there's our message
I tried the steps but no luck, I still can see the logs in Firebug's Console panel.
Any other extensions installed in your profile?
If yes, can you disable them and test again?
Honza
nom prenom
Apr 30, 2014, 9:04:56 AM4/30/14
to fir...@googlegroups.com
Hi, i have the same problem with firefox 29, for me, it's a conflict with wappalyzer module,
Sorry for my bad english.
I deactivated wappalyzer, and firebug works fine.
Sorry for my bad english.
Lenny Maclean
Apr 30, 2014, 9:27:21 AM4/30/14
to fir...@googlegroups.com
Ok i disabled all Add-ons except for FireBug and restarted FireFox. opened FireBug and i started to get console.log messages again, YAY! Closed FireBug and opened the native console to FireFox and i stopped getting console.log messages...... Basically the reverse problem.
I will go back and enable the add-ons and try and pin point the one that caused the FireBug issue.
Jan Honza Odvarko
Apr 30, 2014, 9:48:39 AM4/30/14
to fir...@googlegroups.com
Thanks for the info! I have reported the wappalyzer extension problem here:
https://github.com/ElbertF/Wappalyzer/issues/542
Honza
https://github.com/ElbertF/Wappalyzer/issues/542
Honza
Jan Honza Odvarko
Apr 30, 2014, 9:48:59 AM4/30/14
to fir...@googlegroups.com
On Wednesday, April 30, 2014 3:27:21 PM UTC+2, Lenny Maclean wrote:
Ok i disabled all Add-ons except for FireBug and restarted FireFox. opened FireBug and i started to get console.log messages again, YAY! Closed FireBug and opened the native console to FireFox and i stopped getting console.log messages...... Basically the reverse problem.I will go back and enable the add-ons and try and pin point the one that caused the FireBug issue.
Thanks!
Honza
Honza
Lenny Maclean
Apr 30, 2014, 9:54:29 AM4/30/14
to fir...@googlegroups.com
the problem Add-on for me is "Ghostey 5.2.1" disabled it and FireBug is working again but still no console logs on the FireFoxes native console.....
Andrew Jameson
Apr 30, 2014, 9:55:50 AM4/30/14
to fir...@googlegroups.com
I have the same problem, and I don't have Wappalyzer installed.
I uninstalled and reinstalled Firebug (v1.12.8, which seems to be the latest version compatible with FF29), restarted the browser and was able to print to the console from the console, but no console messages from javascript files would appear.
I then gave the browser another restart and now neither logging from the console or from javascript files works.
I uninstalled and reinstalled Firebug (v1.12.8, which seems to be the latest version compatible with FF29), restarted the browser and was able to print to the console from the console, but no console messages from javascript files would appear.
I then gave the browser another restart and now neither logging from the console or from javascript files works.
Álvaro G. Vicario
Apr 30, 2014, 10:57:57 AM4/30/14
to fir...@googlegroups.com
My findings:
- The guilty add-on is "The easiest Xdebug 1.2"
- It only fails with "http" ("file" is unaffected)
- It works fine in Private Browsing (no matter protocol or add-ons)
Farshid Beheshti
Apr 30, 2014, 11:17:47 AM4/30/14
to fir...@googlegroups.com
> I have the same problem, and I don't have
> Wappalyzer installed.
> Wappalyzer installed.
As you can see, the other extensions (no just Wappalyzer) cause the problem, so please install Firebug in a clean profile and let us know if you have the same problem yet.
https://getfirebug.com/wiki/index.php/Install_Firebug_into_a_clean_profile.
Farshid
https://getfirebug.com/wiki/index.php/Install_Firebug_into_a_clean_profile.
Farshid
Jan Honza Odvarko
May 1, 2014, 3:33:25 AM5/1/14
to fir...@googlegroups.com
One comment coming from Wappalyzer team:
https://github.com/ElbertF/Wappalyzer/issues/542#issuecomment-41801482
In order to see Wappalyzer logging we need to set in
about:config the variable extensions.sdk.console.logLevel to all see https://developer.mozilla.org/en-US/Add-ons/SDK/Tools/console#Logging%20LevelsSo, check also the preference in your config.
Honza
Andrew Jameson
May 3, 2014, 12:59:59 PM5/3/14
to fir...@googlegroups.com
I think I've found what was causing my no-console-logging problem: I'm using Visual Studio 2013, with Web Essentials. Web Essentials has a 'browser link' tool which allows - I think - some modifications made in the browser to be pushed back into Visual Studio.
I didn't notice this message on my work computer, but on my laptop I noticed that the Firefox console (i.e. not Firebug but the built-in developer tools' console) displayed a message saying that the console API had been disabled by a plug-in. I clicked on the message and it took me into a minified line of JS inside the browser-link.js file.
So I then went into Visual Studio's options and disabled the 'browser link' setting (set it to false) and tried again.
Voila! I now have console-logging in Firebug once more.
I didn't notice this message on my work computer, but on my laptop I noticed that the Firefox console (i.e. not Firebug but the built-in developer tools' console) displayed a message saying that the console API had been disabled by a plug-in. I clicked on the message and it took me into a minified line of JS inside the browser-link.js file.
So I then went into Visual Studio's options and disabled the 'browser link' setting (set it to false) and tried again.
Voila! I now have console-logging in Firebug once more.
Grassboy Wu
May 5, 2014, 7:27:11 AM5/5/14
to fir...@googlegroups.com
I built a simple firefox addon for reproducing the bug.
and place it in https://github.com/Grassboy/page-mod-test
this is a addon that will change all of your page title automatically
(source: https://github.com/Grassboy/page-mod-test/blob/master/lib/main.js )
then... following steps will reproduce the bug
1. create a new profile
2. install firebug and this addon (page-mod-test.xpi)
3. goto www.google.com
4. ctrl+shift+j open the browser console and F12 open firebug console
5. reload page
6. invoke console.log in firebug, the log string will appear in browser console
In my opinion... It should be firefox's bug...
( and i created a bug report in bugzilla: https://bugzilla.mozilla.org/show_bug.cgi?id=1005859 )
because this bug appeared after firefox 29 released
and the version of my firebug didn't changed these days...
---
btw, if you are using greasemonkey, the userscript with "@grant GM_xmlhttpRequest" will cause this bug either...
neongrau於 2014年4月10日星期四UTC+8下午9時30分36秒寫道：
and place it in https://github.com/Grassboy/page-mod-test
this is a addon that will change all of your page title automatically
(source: https://github.com/Grassboy/page-mod-test/blob/master/lib/main.js )
then... following steps will reproduce the bug
1. create a new profile
2. install firebug and this addon (page-mod-test.xpi)
3. goto www.google.com
4. ctrl+shift+j open the browser console and F12 open firebug console
5. reload page
6. invoke console.log in firebug, the log string will appear in browser console
In my opinion... It should be firefox's bug...
( and i created a bug report in bugzilla: https://bugzilla.mozilla.org/show_bug.cgi?id=1005859 )
because this bug appeared after firefox 29 released
and the version of my firebug didn't changed these days...
---
btw, if you are using greasemonkey, the userscript with "@grant GM_xmlhttpRequest" will cause this bug either...
neongrau於 2014年4月10日星期四UTC+8下午9時30分36秒寫道：
Kim Hildeqvist
May 5, 2014, 9:15:32 AM5/5/14
to fir...@googlegroups.com
I ran into this issue aswell with Win 8.1 - FF29 - Firebug 1.12.8
Deactivating Ghostery plugin solved it.
Alex Natrek
May 5, 2014, 11:10:58 AM5/5/14
to fir...@googlegroups.com
This resolve my problem, waiting when weppalyzer resolve this problem.
среда, 30 апреля 2014 г., 16:04:56 UTC+3 пользователь nom prenom написал:
среда, 30 апреля 2014 г., 16:04:56 UTC+3 пользователь nom prenom написал:
Roberto Segura
May 5, 2014, 12:41:15 PM5/5/14
to fir...@googlegroups.com
For me it was caused also by "The easiest Xdebug 1.2"
Thanks!!
Thanks!!
al...@clarkscomputers.co.uk
May 6, 2014, 8:34:53 AM5/6/14
to fir...@googlegroups.com
I've had the same issue. For me; disabling 'Skype Click to Call" resolved it.
Eric BLANQUER
May 7, 2014, 9:27:51 AM5/7/14
to fir...@googlegroups.com
For me, an active GreseMonkey script is the cause of this issue, when I disable GreaseMonkey, console.log works fine.
Zakaria Gatra
May 7, 2014, 9:34:41 AM5/7/14
to fir...@googlegroups.com
It was the same. I disabled it and everything worked well again
Ravshan Abbasov
May 7, 2014, 11:15:05 AM5/7/14
to fir...@googlegroups.com
On Wednesday, May 7, 2014 6:27:51 PM UTC+5, Eric BLANQUER wrote:
For me, an active GreseMonkey script is the cause of this issue, when I disable GreaseMonkey, console.log works fine.
The same for me. After disabling GreasyMonkey console.log is working like a charm.
jen.m...@gmail.com
May 8, 2014, 5:12:27 PM5/8/14
to fir...@googlegroups.com
I had the same issue with the Nimbus Screen Capture add on. Console log working fine now that's disabled.
Remo Outila
May 8, 2014, 5:48:48 PM5/8/14
to fir...@googlegroups.com
The Firebug 'console' object seems to get replaced (by Firefox?).
This workaround works for me:
This is not a global workaround though... For a global workaround you could probably use GreaseMonkey.
This workaround works for me:
// store the Firebug console object
var firebugConsole = console;
jQuery(document).ready(function() {
// and restore it on domready
window.console = firebugConsole;
});
This is not a global workaround though... For a global workaround you could probably use GreaseMonkey.
Jan Honza Odvarko
May 9, 2014, 5:37:00 AM5/9/14
to fir...@googlegroups.com
Note that this is Firefox platform regression bug.
Watch this bug report:
https://bugzilla.mozilla.org/show_bug.cgi?id=1005859
You can also vote for fix directly in the report!
Honza
Watch this bug report:
https://bugzilla.mozilla.org/show_bug.cgi?id=1005859
You can also vote for fix directly in the report!
Honza
Miqi180
May 10, 2014, 7:41:41 PM5/10/14
to fir...@googlegroups.com
After updating to Firefox 29.0.1 today, I ran into the same problem with Firebug 1.12.8. Removing Ghostery fixed it.
auroras
May 12, 2014, 5:17:24 AM5/12/14
to fir...@googlegroups.com
Thanks!
Disabling Ghostery also fixed it for me :-)
- Rich
Enrique Ramírez
May 12, 2014, 2:54:28 PM5/12/14
to fir...@googlegroups.com
Happening to me as well, but a little different.
My application has a lot of console.log on development. 20+ logs just on page load. I am getting around 4 of those 20, the rest of them appearing on firefox's console. I've removed all of my other plugins, reinstalled firebug and started with a new profile. It sorta fixed the issue. I get my 20 initial logs and the first event that is triggered by user input, but starting from there they all go to firefox's console.
Firefox version is 29.0 and firebug's is 1.12.8.
Christian Knuth
May 13, 2014, 10:06:20 AM5/13/14
to fir...@googlegroups.com
got the same problem today. i found out that "Wappalyzer" Plugin causes the error. The weird thing about it was that the console.log statements in the root lines of my js files worked, but within the jquery scope of:
$(function(){
console.log('foo');
});
it failed.
i deactived Wappalyzer now.
$(function(){
console.log('foo');
});
it failed.
i deactived Wappalyzer now.
Gavin Hewitt
May 14, 2014, 4:44:31 AM5/14/14
to fir...@googlegroups.com
For me it was disabling 1password that fixed it.
Steve Crickett
May 14, 2014, 6:58:44 AM5/14/14
to fir...@googlegroups.com
Thanks. 1Password was what was causing it for me also. Hope a fix comes out soon as 1Password is more important to me than Firebug, although I use both constantly. Don't really want to do without either, but at least the native FF console shows the output.
NotoriousWebmaster
May 14, 2014, 9:47:36 AM5/14/14
to fir...@googlegroups.com
Same issue using FF 29.0.1, OSX 10.9.2, FB 1.12.8.
Removed Easiest XDebug, and all's well again. Thanks guy!
Removed Easiest XDebug, and all's well again. Thanks guy!
Travis Detert
May 14, 2014, 3:02:43 PM5/14/14
to fir...@googlegroups.com
This was also my problem.
Chris Carey
May 14, 2014, 9:44:23 PM5/14/14
to fir...@googlegroups.com
Skype "click to call" was the culprit for me
Scott Penrose
May 14, 2014, 10:25:52 PM5/14/14
to fir...@googlegroups.com
I am having the same problem on fire fox 29.0.1, 1.12.8. However I can tell you for me it is only on a callback. So if I put in a console.log it appears. But as soon as I put it in a callback for a jQuery $.each or any type of AJAX, I don't get any console.log, but still get alert.
Other extensions like 1Password removed might work around the problem, but they have not changed and I need them too. Might move to using internal Firefox dev tools, can't work without a console.log.
Other extensions like 1Password removed might work around the problem, but they have not changed and I need them too. Might move to using internal Firefox dev tools, can't work without a console.log.
laz.br...@gmail.com
May 15, 2014, 11:52:30 AM5/15/14
to fir...@googlegroups.com
Am Donnerstag, 15. Mai 2014 04:25:52 UTC+2 schrieb Scott Penrose:
I am having the same problem on fire fox 29.0.1, 1.12.8. However I can tell you for me it is only on a callback. So if I put in a console.log it appears. But as soon as I put it in a callback for a jQuery $.each or any type of AJAX, I don't get any console.log, but still get alert.
Other extensions like 1Password removed might work around the problem, but they have not changed and I need them too. Might move to using internal Firefox dev tools, can't work without a console.log.
Same here. Only timeout callback or any sort of event handlers - no console.log
Disabling the one-password addon fixed it for me too though.
Strange.
John Pansewicz
May 19, 2014, 2:53:15 PM5/19/14
to fir...@googlegroups.com
Same for me... disabling Skype Click To Call fixed the problem.
Yuriy Shikhanovich
May 19, 2014, 5:16:29 PM5/19/14
to fir...@googlegroups.com
Just to add a data point Remo's fix worked for me as did removing "Coupons at Checkout" add-on.
Julio Loayza
May 28, 2014, 5:33:01 PM5/28/14
to fir...@googlegroups.com
Disabling Greasemonkey (1.15) solved the problem in my case.
Jan Honza Odvarko
May 29, 2014, 3:42:35 AM5/29/14
to fir...@googlegroups.com
Note that the problem is fixed in Firefox 30 (currently beta) that will be released in couple of weeks on Tuesday 10th of June.
Honza
Honza
Spencer Williams
Jun 4, 2014, 10:12:59 AM6/4/14
to fir...@googlegroups.com
Yep! I was experiencing all of this: No console messages in Firebug but double messages in Firefox's own debug console. Disabled "Skype Click to Call",
didn't even restart, and now I'm consoling it up in my favorite debugger again.
didn't even restart, and now I'm consoling it up in my favorite debugger again.
Jan Honza Odvarko
Jun 11, 2014, 7:54:27 AM6/11/14
to fir...@googlegroups.com
Note that Firebug 2.0 has been released. This version fixes the problem with the console logging
https://blog.getfirebug.com/2014/06/10/firebug-2-0/
Honza
https://blog.getfirebug.com/2014/06/10/firebug-2-0/
Honza
Grassboy Wu
Sep 28, 2014, 10:55:50 PM9/28/14
to fir...@googlegroups.com
Excuse me, now I am using Firefox 33 & Firebug 2.0.4 this bug comes again... is it cause by same issue? or there is another issue cause this bug? thanks for your help!!
Jan Honza Odvarko於 2014年6月11日星期三UTC+8下午7時54分27秒寫道：
Reply all
Reply to author
Forward
0 new messages