Extension breaks with version 35.0.1 of Firefox

I took a quick look and it looks like the browser parameter isn't passing correctly to the showPanel method. this might mean that mozillas changed the object returned by getBrowser.

I was planning a complete rewrite of the firefox extension. With DrupalCampLA coming up next week I don't really have the time to do this.

I would recommend that if you require this module [Drupal for Firebug] as part of your workflow, downgrade (or don't upgrade) Firefox for the time being.

I am sorry this is taking so long. I have been really busy.

I have not pushed it yet, however, then next release of the Drupal module will not need a browser extension. I am not eliminating the extension, but I am making it optional.

Also, if you really need the an extension AFAIK the chrome extension still works. The change in the Mozilla API should not have changed that.

I finally had the time to make some progress on this. If you want to follow my progress then follow the project for the Firefox extension over on bitbucket: https://bitbucket.org/frob/drupalforfirebug

unfourtunatly no, currently the new (from the ground up) plugin registers itself with firebug and firefox; it displays the drupal tabs and subtabs. But it doesn't gather the data from the drupalforfirebug drupal module yet.

Once it is ready I will package it as an xpi and allow it to be downloaded from bitbucket while mozilla reviews the update. I should be done sometime this week.

So now the code on bitbucket is functional. I wouldn't call it testable -- still hanging around pre-alpha.

Before I we call it testable I need to do two things.

1. Further abstract the connection between the Drupal Module and the Firefox Module. Right now the presentation layer calls the connector that returns the content directly. However, once I abstract that connection to an API call layer then changes to the API will be less problematic for Firefox plugin to deal with.
2. Remove the dependency on jQuery for the plugin. Currently the plugin loads jQuery to deal with a couple of UI niceties.<-- this is what is blocking the release.

By all means though, If you know how to install from code a firefox plugin then please do so. It works just like the old one for the time being.

I am moving this from bug to task and marking as needs review.

I will package up an xpi tonight. I opted to just throw out the expande/collaps functionality of the field sets. Its a little less user friendly but its working.

https://bitbucket.org/frob/drupalforfirebug

The latest release of the Firefox extension is awaiting review. You can download it from Mozilla's Developer Channel or from Bitbucket.

https://addons.mozilla.org/en-US/firefox/addon/drupal-for-firebug/
https://bitbucket.org/frob/drupalforfirebug/downloads

So something is broken in the xpi. I will fix this afternoon.

Okay, I didn't put the -r flag into zip when building the xpi. So even though the module was installing correctly with firefox firebug looked for the module and found that the module didn't do anything. This has been fixed.

eltioseba, could you please post a screenshot? That is what would come from the general Drupal > General tab, if you haven't sent any messages through to firep.

you are correct. there is no search and no collapsable fieldset. This is as designed. I didn't think this should hold up the release. Nor do I tink that these are huge features. The next version will have a whole new feature set but that will require a rewrite of the drupal module as well and I think one rewrite is enough for now.

If you have a new issue please open a new issue. I do not find it helpful to reopen the same issue over and over again every time Mozilla changes an api.

I just tested this with everything up-to-date as of today. Nothing seems to be wrong with the firebug extension.

It has been a long time since anything has been done on the Drupal module side, that is because it all works. I have been working very slowly on a 2.x but that doesn't work at all yet.

The extension had a major rewrite two years ago and just last month I put together a new release and wrote a grunt script to ease development, so that I can keep up with Mozilla's changing apis easier. (Released December 30, 2014)

Will this tool ever be revised to function properly?

If so, when?
If not, why not just take everything down, because it's nuts to think that at the rate Firebug and Firefox are evolving that not keeping up is an option and giving us the impression that there is a tool when there isn't is a waste of our time.

This is not helpful. The project is far from abandoned and projects cannot simply be "taken down" from Drupal.org.

If you have anything else to post please open a new issue, or if you have something to contribute please issue a PR on drupalforfirebug's github.