Title: igarrett's Replies | WordPress.org

---

# igarrett

  [  ](https://wordpress.org/support/users/igarrett/)

 *   [Profile](https://wordpress.org/support/users/igarrett/)
 *   [Topics Started](https://wordpress.org/support/users/igarrett/topics/)
 *   [Replies Created](https://wordpress.org/support/users/igarrett/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/igarrett/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/igarrett/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/igarrett/engagements/)
 *   [Favorites](https://wordpress.org/support/users/igarrett/favorites/)

 Search replies:

## Forum Replies Created

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

 *   Forum: [Reviews](https://wordpress.org/support/forum/reviews/)
    In reply to:
   [[MaxButtons - Create buttons] Great Plug-in](https://wordpress.org/support/topic/great-plug-in-annoying-banner/)
 *  Thread Starter [igarrett](https://wordpress.org/support/users/igarrett/)
 * (@igarrett)
 * [10 years, 7 months ago](https://wordpress.org/support/topic/great-plug-in-annoying-banner/#post-8009023)
 * Thanks for the fix, that seems to take care of it! I’ll amend my rating and I’m
   upgrading.
 *   Forum: [Reviews](https://wordpress.org/support/forum/reviews/)
    In reply to:
   [[MaxButtons - Create buttons] Great Plug-in](https://wordpress.org/support/topic/great-plug-in-annoying-banner/)
 *  Thread Starter [igarrett](https://wordpress.org/support/users/igarrett/)
 * (@igarrett)
 * [10 years, 7 months ago](https://wordpress.org/support/topic/great-plug-in-annoying-banner/#post-8009014)
 * I’ve gone through the Javascript Debugging steps suggested in the codex here:
   [https://codex.wordpress.org/Using_Your_Browser_to_Diagnose_JavaScript_Errors](https://codex.wordpress.org/Using_Your_Browser_to_Diagnose_JavaScript_Errors)
 * I get the Javascript error: Uncaught ReferenceError: jQuery is not defined
 *   Forum: [Reviews](https://wordpress.org/support/forum/reviews/)
    In reply to:
   [[MaxButtons - Create buttons] Great Plug-in](https://wordpress.org/support/topic/great-plug-in-annoying-banner/)
 *  Thread Starter [igarrett](https://wordpress.org/support/users/igarrett/)
 * (@igarrett)
 * [10 years, 7 months ago](https://wordpress.org/support/topic/great-plug-in-annoying-banner/#post-8009005)
 * The only link that works in the banner is the link to the plug-in page to give
   it a rating. The close “x” on the right and the ‘I’ve already reviewed’ link 
   do nothing for me.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Jetpack - WP Security, Backup, Speed, & Growth] Jetpack Stats precipitous drop off](https://wordpress.org/support/topic/jetpack-stats-precipitous-drop-off/)
 *  Thread Starter [igarrett](https://wordpress.org/support/users/igarrett/)
 * (@igarrett)
 * [12 years, 4 months ago](https://wordpress.org/support/topic/jetpack-stats-precipitous-drop-off/#post-4442811)
 * Hi Jeremy,
 * We just implemented a new theme and that seems to have solved it for us. I don’t
   know if it had to do with the theme itself (Atahualpa) which is database driven.
   I know we moved away from it because it would tax our server a bit with a lot
   of DB calls. Though, while we were on that theme, we had W3 Total Cache implemented
   for a while so that wouldn’t have solved it, since it was already there (it isn’t
   on our new theme because we moved the hosting to Dreampress and were advised 
   that caching plug-ins can conflict with their caching on a WordPress specific
   VPS… true?)
 * We had admins set to not track on both WordPress and Google Analytics, but the
   difference in numbers (Google: 150 vs WP Jetpack: 5) would have to be a different
   issues than just logging the 5 admins that have access to the site. I really 
   do mean that it was a precipitous drop off where Jetpack shoved 90&+ less traffic
   than Google.
 * Anyway… it’s resolved with the new theme, so we may never know. But the rest 
   of that info might be helpful to someone else to know that it was apparently 
   a conflict with our DB driven theme.

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