Changeset 444753
- Timestamp:
- 09/28/2011 12:44:05 PM (14 years ago)
- Location:
- debug-bar-query-tracer/trunk
- Files:
-
- 1 added
- 1 edited
-
readme.txt (modified) (1 diff)
-
screenshot-1.jpg (added)
Legend:
- Unmodified
- Added
- Removed
-
debug-bar-query-tracer/trunk/readme.txt
r444752 r444753 1 === Plugin Name===1 === Galahad Query Tracer === 2 2 Contributors: inxilpro 3 3 Donate link: 4 4 Tags: debug bar, performance, backtrace, wpdb 5 Requires at least: 3. 05 Requires at least: 3.2 6 6 Tested up to: 3.2 7 7 Stable tag: 0.1 8 8 9 Here is a short description of the plugin. This should be no more than 150 characters. No markup here.9 A Debug Bar plugin that lets you trace what plugins are causing database queries. 10 10 11 11 == Description == 12 12 13 This is the long description. No limit, and you can use Markdown (as well as in the following sections). 13 This Query Tracer plugin backtraces all calls to WPDB::query() and determines a) which plugin caused that 14 database query (it ignores all queries that are a part of normal Wordpress activity) and b) the function 15 chain that led to that query. It then displays that information on an additional panel in the Debug Bar 16 plugin (which is required). 14 17 15 18 == Installation == 16 19 20 1. Install the [Debug Bar](http://wordpress.org/extend/plugins/debug-bar/) plugin 21 2. Install the Query Tracer plugin 22 17 23 == Frequently Asked Questions == 24 25 Feel free to ask questions [on my website](http://cmorrell.com/open-source/wordpress-plugins/debug-bar-query-tracer) and 26 I will update this section with any frequent questions. 18 27 19 28 == Screenshots == 20 29 21 1. This screen shot description corresponds to screenshot-1.(png|jpg|jpeg|gif). Note that the screenshot is taken from 22 the directory of the stable readme.txt, so in this case, `/tags/4.3/screenshot-1.png` (or jpg, jpeg, gif) 23 2. This is the second screen shot 30 1. The Query Tracer Panel 24 31 25 32 == Changelog ==
Note: See TracChangeset
for help on using the changeset viewer.