Where code meets community

Did you just upgraded the FirePHP or DeveloperCompanion Extension and FirePHP is no longer working?

It is assumed that only the client has been updated and nothing has changed on the server.

It is assumed you have the FirePHP Extension or DeveloperCompanion installed on the client (not both).

First thing to check:

If using the FirePHP Extension with Firebug:

  • Make sure the Firebug Console and Net panels are enabled for the hostname you want to debug.

If using DeveloperCompanion:

  • TODO

Second things to try:

  1. Restart Firefox
  2. Reboot your computer
  3. Create a new Firefox profile and install the FirePHP client + Firebug only.

    SEE: See http://support.mozilla.com/en-US/kb/Managing-profiles


Contact Support and provide the following:

  • Firefox version:
  • FirePHP Extension version (if installed):
  • DeveloperCompanion version (if installed):
  • Firebug version (if installed):
  • FirePHP server library name: (typically FirePHPCore or ZendFramework)
  • FirePHP server library version:
  • Were things working before upgrading the client?
  • How was the client upgraded?
  • Is anything FirePHP related working?

Are you not seeing any messages in the console?

It is assumed that FirePHP has never worked or stopped working after changing something on the server.

If using FirePHPCore (or equivalent) on server with FirePHP Extension or DeveloperCompanion + Firebug on client:

See Configuration/Traditional for how to configure this setup on the server.

  1. Make sure your client works by going to firephp.org and looking for messages in the console. If the client is not working see above.
  2. Make sure the Firebug Console and Net panels are enabled for the hostname you want to debug.
  3. Is FirePHP enabled on the client?

    If using FirePHP Extension: Go to Tools -> FirePHP and ensure there is a checkmark next to FirePHP Enabled.

    If using DeveloperCompanion: TODO

  4. Do you have output buffering enabled? Ensure you are using ob_start() at the beginning of your script or you have the output_buffering PHP ini directive enabled.

If it is still not working see if you get any x-wf- headers for the response in the Firebug Net panel and include these when contacting support (see Finally above).

If using FirePHP 1.0 configured securely:

It is assumed that FirePHP is configured using the Configure: constants or Configure: files approaches.

The easiest way to troubleshoot a secure FirePHP 1.0 installation is to use DeveloperCompanion to test the setup.

Docs and tools to troubleshoot manually.

When adding a Workspace in DeveloperCompanion the setup is automatically tested and any errors are displayed in detail.

If the Workspace was already setup but things are not working all of a sudden, the connection can be manually tested:

This requires a DeveloperCompanion license. If you do not have a license you can delete the workspace and re-create it as the connection will be tested when setting up a new Workspace.

  1. Open DeveloperCompanion by clicking on the icon in the browser status bar.
  2. Select the first tab (that is the home or companion tab) and then Workspaces.
  3. Double-click the workspace you want to test
  4. When the workspace has launched locate the Check Workspace Connection button and click it.

If you need additional help you can get support here.

One of the most common problems is an incorrect setting for the /<ServerScript.php> path. This is evidenced by a No wildfire messages detected message.

The /<ServerScript.php> path must be set to the path of a PHP script relative to the hostname that includes FirePHP just like the rest of your application does. It typically refers to the homepage of the application. The path is set as follows depending on which configuration method is used:

Configure: constants

define('INSIGHT_SERVER_PATH', '/<ServerScript.php>');

Configure: files

package.json ~ {
  "implements": {
    "cadorn.org/insight/@meta/config/0": {
      "server": {
        "path": "/<ServerScript.php>"

For more information about all configuration options see Install.

Homepage: Sourcemint.com


Sourcemint is incomplete ALPHA technology and continuously evolving in sync with underlying and related projects. Production ready aspects will be documented and made available in time. Your Feedback is welcome and appreciated!


Sourcemint is one of the results of intense focus by Christoph Dorn over the past several years and continuous exploration throughout Christoph's interest in software development over the past 15+ years.

Sourcemint is the love child of one person guided by the voices of passionate developers at the top of their game who are leading the industry into a new era of software development.


Sourcemint is an integral part of Christoph's work intended to realize his dream of one global toolchain under which components may be arbitrarily combined into maintainable mission critical systems by providing an all-encompassing and organized package repository from which consistent and autonomic systems may be built.

Sourcemint provides an automated software building and integration service as well as an intelligent software delivery network to distribute built software to all deployed systems and Internet users.

This means an arbitrary (code, configuration, network, ...) change may be made to a software system which can then be automatically built, tested, distributed and deployed. Every change constitutes a completely new system made possible by the fact that changes, any changes, are cheap and fully tested in every way before going live.

Just imagine what this means in your daily work.


Automated software builds, continuous integration processes, streamlined issue trackers, community supported software, source control, online collaboration and automated cloud deployment have wet our appetite but hardly scratch the surface of what it actually means to have a completely automated production cycle from idea to delivery. The full potential is only realized once these separate solutions addressing different areas work together harmoniously.

What has been missing is new ways of looking at how to build software.


Christoph's work provides a new way to build software that is not necessarily new in the sense of ideas or technology but rather arrangement and timing. Christoph has through exploration and experimentation distilled current cutting edge technology, knowledge and wisdom into a toolchain platform called PINF available open source under the MIT license to realize a new breed of software.

Imagine software and systems that just work and are a pleasure to maintain.

Sourcemint is built entirely on PINF, as is all of Christoph's work, and can be used by any developer to tap into the power of the PINF approach to build open source or commercial libraries, frameworks, applications, systems and services.

Christoph's hope is that PINF and related projects will provide a foundation for developers to cooperate more widely and experiment with new ideas by eliminating some of the major constraints imposed by traditional toolchains. Traditional toolchains create systems that typically rot because they are practically impossible to refactor. We need a toolchain such as PINF which has refactorability designed into its core.

Let's create software that breathes with life and is in large part self-sustaining!


Join Christoph in his mission to help you, the developer, and help yourself by broadly applying the tools and approaches you know work to all of your work. Lean on PINF, your mind is begging you. Learn it, teach others, and let your inspiration soar!

Follow Sourcemint and PINF on twitter to watch for news of cutting-edge tools, tutorials and services coming online. You can also follow Christoph's work directly.