Download the PHP package kilbiller/debug_kit without Composer

On this page you can find all versions of the php package kilbiller/debug_kit. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Example code of kilbiller/debug_kit

Informations about the package debug_kit

CakePHP DebugKit Build Status

DebugKit provides a debugging toolbar and enhanced debugging tools for CakePHP applications.

Requirements

The master branch has the following requirements:

Installation

Using Composer

Install the plugin with Composer from the directory, where your project's composer.json is located:

Consider using "--dev", if you only want to include DebugKit for your development environment.

Because this plugin has the type cakephp-plugin set in it's own composer.json, composer knows to install it inside your /Plugin directory, rather than in the usual vendors file. It is recommended that you add /Plugin/DebugKit to your .gitignore file. (Why? read this.)

[Manual]

[GIT Submodule]

In your app directory type:

[GIT Clone]

In your plugin directory type

Enable plugin

Reporting Issues

If you have a problem with DebugKit please open an issue on GitHub.

Contributing

If you'd like to contribute to DebugKit, check out the roadmap for any planned features. You can fork the project, add features, and send pull requests or open issues.

Versions

DebugKit has several releases, each compatible with different releases of CakePHP. Use the appropriate version by downloading a tag, or checking out the correct branch.

Documentation

Toolbar Panels

The DebugKit Toolbar is comprised of several panels, which are shown by clicking the CakePHP icon in the upper right-hand corner of your browser after DebugKit has been installed and loaded. Each panel is comprised of a panel class and view element. Typically, a panel handles the collection and display of a single type of information such as Logs or Request information. You can choose to panels from the toolbar or add your own custom panels.

Built-in Panels

There are several built-in panels, they are:

Configuration

The toolbar has a few configuration settings. Settings are passed in the component declaration like normal component configuration.

Configuring Panels

You can customize the toolbar to show your custom panels or hide any built-in panel when adding it toolbar to your components.

Would display your custom panel and all built-in panels except the 'Timer' panel.

Controlling Panels

Using the panels key you can specify which panels you want to load, as well as the order in which you want the panels loaded.

Would add your custom panel MyCustomPanel to the toolbar and exclude the default Timer panel. In addition to choosing which panels you want, you can pass options into the __construct of the panels. For example the built-in History panel uses the history key to set the number of historical requests to track.

Would load the History panel and set its history level to 10. The panels key is not passed to the Panel constructor.

forceEnable

The forceEnable setting is new in DebugKit 1.1. It allows you to force the toolbar to display regardless of the value of Configure::read('debug');. This is useful when profiling an application with debug kit as you can enable the toolbar even when running the application in production mode.

autoRun

autoRun is a new configuration setting for DebugKit 1.2. It allows you to control whether or not the toolbar is displayed automatically or whether you would like to use a query string parameter to enable it. Set this configuration key to false to use query string parameter toggling of the toolbar.

When visiting a page you can add ?debug=true to the url and the toolbar will be visible. Otherwise it will stay hidden and not execute.

Developing Your Own Panels

You can create your own custom panels for DebugKit to help in debugging your applications.

Panel Classes

Panel Classes simply need to be placed inPanel directory inside a Lib path. The filename should match the classname, so the class MyCustomPanel would be expected to have a filename of app/Lib/Panel/MyCustomPanel.php.

See also the example Test/test_app/Plugin/DebugkitTestPlugin/Lib/Panel/PluginTestPanel.php.

Notice that custom panels are required to subclass the DebugPanel class. Panels can define the css and javascript properties to include additional CSS or javascript on the page. Both properties should be an array.

Callbacks

Panel objects have 2 callbacks, that allow them to hook into and introspect on the current request.

Each panel's startup() method is called during component startup() process. $controller is a reference to the current controller object.

Much like startup() beforeRender() is called during the Component beforeRender() process. Again $controller is a reference to the current controller. Normally at this point you could do additional introspection on the controller. The return of a panels beforeRender() is automatically passed to the View by the Toolbar Component. Therefore, under normal use you do not need to explicitly set variables to the controller.

Example of beforeRender Callback

This would return cake's internal params array. The return of a panel's beforeRender() is available in you Panel element as $content

Panel Elements

Each Panel is expected to have a view element that renders the content from the panel. The element name must be the underscored inflection of the class name. For example SessionPanel has an element named session_panel.ctp, and sqllogPanel has an element named sqllog_panel.ctp. These elements should be located in the root of your View/Elements directory.

Custom Titles and Elements

Panels should pick up their title and element name by convention. However, if you need to choose a custom element name or title, there are properties to allow that configuration.

Panels as Cake Plugins

Panels provided by Cake Plugins work almost entirely the same as other plugins, with one minor difference: You must set public $plugin to be the name of the plugin directory, so that the panel's Elements can be located at render time.

To use a plugin panel, use the common CakePHP dot notation for plugins.

The above would load all the default panels as well as the custom panel from MyPlugin.

Cache Engine

By default, DebugKit uses File as the engine for internal caching, but if you want to use another cache engine you can customize it by simply adding a cache key inside the components config array.

You can use any cache engine supported by CakePHP, the same way you set in both core.php and bootstrap.php files with the Cache::config() method.

Viewing the Toolbar for AJAX Requests

When doing AJAX requests, you will not be able to see an HTML version of the toolbar. However, if you have a browser extension that supports FirePHP, you can view the toolbar in your browser:

Once you have installed the correct extension, you should see the toolbar data output on each AJAX request.

All versions of debug_kit with dependencies

PHP Build Version
Package Version
Requires php Version >=5.3.0
composer/installers Version ^1.0.0
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package kilbiller/debug_kit contains the following files

Loading the files please wait ....