This repository was archived by the owner on Aug 7, 2026. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2
Expand file tree
/
Copy pathreadme.txt
More file actions
66 lines (42 loc) · 2.73 KB
/
Copy pathreadme.txt
File metadata and controls
66 lines (42 loc) · 2.73 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
=== Kint Debugger ===
Contributors: misternifty, chriswallace
Author: Brian Fegter
Author URI: http://upthemes.com/
Plugin URI: http://upthemes.com/plugins/kint-debugger
Tags: debug, debugger, print_r, var_dump, backtrace, debug_backtrace, krumo, php, tool, trace, developer, debug-bar
Requires at least: 2.5
Tested up to: 3.5
Stable tag: 0.3
Kint Debugger makes debugging and dumping variables a more pleasant experience. Kint Debugger integrates seamlessly with the Debug Bar plugin.
== Description ==
Kint Debugger is a simple WordPress wrapper for [Kint](http://code.google.com/p/kint), a debugging tool to output information about variables and traces. Debugging is presented in a styled, collapsible format that is easy on the eyes. Kint Debugger plays nice with the Debug Bar plugin by creating its own panel to display your debug results.
**No more adding PRE tags before print_r or var_dump!**
For those who love Krumo, **Kint is Krumo++**.
Dumping variables is easy:
* `d($variable)` will output a styled, collapsible container with your variable information
* `dd($variable)` will do exactly as d() except halt execution of the script
* `s($variable)` will output a simple, un-styled whitespace container
* `sd($variable)` will do exactly as s() except halt execution of the script
Backtrace is also easy:
* `Kint::trace()` The displayed information for each step of the trace includes the source snippet, passed arguments and the object at the time of calling
We've also baked in a few functions that are WordPress specific:
* `dump_wp_query()`
* `dump_wp()`
* `dump_post()`
When you use the ever awesome Debug Bar plugin, Kint Debugger keeps your theme looking beautiful by placing all debug output into a Debug Bar sub-panel. If you are not using Debug Bar, your debug output will be displayed inline.
== Installation ==
Upload the Kint Debugger plugin to your `wp-content/plugins/` directory and activate.
== Frequently Asked Questions ==
= I have called the debug functions, but I can't find the output! =
* If you have the Debug Bar plugin installed, all of your debug results will be displayed under the "Kint Debugger" sub panel.
If you have a feature request or question, please use the [Kint Debugger support forum](http://wordpress.org/tags/kint-debugger).
If you have a question about Kint specifically, please visit the [Kint site](http://code.google.com/p/kint/).
== Screenshots ==
1. Kint debugging outputs are easy on the eyes.
2. Kint integrates with WP Debug Bar
== Changelog ==
= 0.2 =
* Added Debug Bar support
= 0.1 =
* Added Kint 3.2 and created dump_wp_query(), dump_wp(), and dump_post() functions
If you have a feature request or question, please use the <a href='http://wordpress.org/tags/kint-debugger'>Kint Debugger support forum</a>.