Title: Small code correction
Last modified: August 21, 2016

---

# Small code correction

 *  Resolved [qstudio](https://wordpress.org/support/users/qlstudio/)
 * (@qlstudio)
 * [12 years, 4 months ago](https://wordpress.org/support/topic/small-code-correction/)
 * Hi,
 * I’m loving this tool – it’s helping me fix errors I could not locate and teaching
   more about WP Action cycle.. thanks!
 * However, I have a small change request.
 * in db.php could you please consider to include a check on the CONSTANTS that 
   you are defining – for example:
 * /**
    * [@since](https://wordpress.org/support/users/since/) 0.71 */ if ( !defined(‘
   EZSQL_VERSION’ ) ) { define( ‘EZSQL_VERSION’, ‘WP1.25’ ); }
 * /**
    * [@since](https://wordpress.org/support/users/since/) 0.71 */ if ( !defined(‘
   OBJECT’ ) ) { define( ‘OBJECT’, ‘OBJECT’, true ); }
 * /**
    * [@since](https://wordpress.org/support/users/since/) 2.5.0 */ if ( !defined(‘
   OBJECT_K’ ) ) { define( ‘OBJECT_K’, ‘OBJECT_K’ ); }
 * /**
    * [@since](https://wordpress.org/support/users/since/) 0.71 */ if ( !defined(‘
   ARRAY_A’ ) ) { define( ‘ARRAY_A’, ‘ARRAY_A’ ); }
 * /**
    * [@since](https://wordpress.org/support/users/since/) 0.71 */ if ( !defined(‘
   ARRAY_N’ ) ) { define( ‘ARRAY_N’, ‘ARRAY_N’ ); }
 * This is to avoid a clash with the same file that is included in wp=cache-reloaded-
   fix – I’m also writing to the author of that plugin to ask the same!
 * Cheers.
 * Q
 * [http://wordpress.org/plugins/query-monitor/](http://wordpress.org/plugins/query-monitor/)

Viewing 4 replies - 1 through 4 (of 4 total)

 *  Plugin Author [John Blackbourn](https://wordpress.org/support/users/johnbillion/)
 * (@johnbillion)
 * WordPress Core Developer
 * [12 years, 4 months ago](https://wordpress.org/support/topic/small-code-correction/#post-4530478)
 * Hi Q,
 * Not sure I understand what you’re asking here. Query Monitor’s `db.php` does 
   not define these constants.
 * John
 *  Thread Starter [qstudio](https://wordpress.org/support/users/qlstudio/)
 * (@qlstudio)
 * [12 years, 4 months ago](https://wordpress.org/support/topic/small-code-correction/#post-4530482)
 * could you please try and install [http://wordpress.org/plugins/db-cache-reloaded-fix/](http://wordpress.org/plugins/db-cache-reloaded-fix/)
   and your own plugin and see if the combination gives you constant already defined
   errors?
 * Cheers
 * Q
 *  Plugin Author [John Blackbourn](https://wordpress.org/support/users/johnbillion/)
 * (@johnbillion)
 * WordPress Core Developer
 * [12 years, 4 months ago](https://wordpress.org/support/topic/small-code-correction/#post-4530691)
 * Query Monitor does not define those constants, so this problem is not related
   to Query Monitor. The problem is with the DB Cache Reloaded Fix plugin which 
   defines those constants in its `db.php` file.
 *  Thread Starter [qstudio](https://wordpress.org/support/users/qlstudio/)
 * (@qlstudio)
 * [12 years, 4 months ago](https://wordpress.org/support/topic/small-code-correction/#post-4530692)
 * Makes sense – the plugin is no longer maintained – I have an updated version 
   ready, but I don’t want to take on-going responsibility for this really.. so 
   I’m not sure of the correct way to deal with this.
 * Q

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Small code correction’ is closed to new replies.

 * ![](https://ps.w.org/query-monitor/assets/icon.svg?rev=2994095)
 * [Query Monitor](https://wordpress.org/plugins/query-monitor/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/query-monitor/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/query-monitor/)
 * [Active Topics](https://wordpress.org/support/plugin/query-monitor/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/query-monitor/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/query-monitor/reviews/)

 * 4 replies
 * 2 participants
 * Last reply from: [qstudio](https://wordpress.org/support/users/qlstudio/)
 * Last activity: [12 years, 4 months ago](https://wordpress.org/support/topic/small-code-correction/#post-4530692)
 * Status: resolved