Title: misconfigured setting …
Last modified: August 20, 2016

---

# misconfigured setting …

 *  Resolved [Texiwill](https://wordpress.org/support/users/texiwill/)
 * (@texiwill)
 * [13 years, 5 months ago](https://wordpress.org/support/topic/misconfigured-setting-2/)
 * Hello,
 * I was have the ‘misconfigured setting’ and have tested everything as suggested.
   If I use ‘curl’ to access wp-slimstat-js.php I get the Invalid data format, as
   expected. I also use Better WordPress Minify and excluded wp_slimstat from that
   as well (which is served up via CDN). I still get the misconfigured setting message.
   In all other respects slimstat works as expected.
 * I see in the HTML code produced a line that has slimstat_tid in it and the function
   ss_te(….) from the JSDeliver CDN. So the JS is getting loaded. THere is no difference
   if I use the CDN vs local.
 * Other thoughts?
 * Thanks,
    Edward
 * [http://wordpress.org/extend/plugins/wp-slimstat/](http://wordpress.org/extend/plugins/wp-slimstat/)

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

 *  Thread Starter [Texiwill](https://wordpress.org/support/users/texiwill/)
 * (@texiwill)
 * [13 years, 5 months ago](https://wordpress.org/support/topic/misconfigured-setting-2/#post-3288884)
 * Hello,
 * One other thing, I also use a memcache plugin but whether I have that enabled
   or not does not seem to make a difference. I actually have two sites, one it 
   works on, the other it does not and they should be the same.
 * PHP cache may be a different but unfortunately I cannot remove that to test it
   out.
 * site is ‘www.virtualizationpractice.com’
 * Edward
 *  Plugin Contributor [Jason Crouse](https://wordpress.org/support/users/coolmann/)
 * (@coolmann)
 * [13 years, 5 months ago](https://wordpress.org/support/topic/misconfigured-setting-2/#post-3288911)
 * I thought you had solved your issue, I’m confuses now 🙂
 *  Thread Starter [Texiwill](https://wordpress.org/support/users/texiwill/)
 * (@texiwill)
 * [13 years, 5 months ago](https://wordpress.org/support/topic/misconfigured-setting-2/#post-3288978)
 * I thought I did as well, I Have a development site and a production site. There
   are no differences in caching mechanisms between the sites. Both use Xcache, 
   DB Cache Reloaded, etc. The Dev Site works flawlessly. But the production site
   does not.
 * Turning on a JavaScript debugger, I found the cause of the problem. :} The wp-
   config.php file is being parsed but not executed, that will cause the problem
   in my setup as I go to different databases depending on the incoming URL…. So
   in essence it has different DB_ var names. On the dev server there is only 1 
   item…
 * This was an older way to do multi-site setup and we have not changed it yet….(
   wp_oneinstall plugin and it still works today). The MU will not work for us in
   its current form.
 * So we need a way to set the DB_ vars appropriately… the simplest way seems to
   just include wp-config.php instead of trying to parse it which could make this
   MU acceptable.
 * This is what I did on my dev environment and it seems to work.
 * Best regards,
    Edward
 *  Thread Starter [Texiwill](https://wordpress.org/support/users/texiwill/)
 * (@texiwill)
 * [13 years, 5 months ago](https://wordpress.org/support/topic/misconfigured-setting-2/#post-3288979)
 * Another solution is to rearrange my multi-wordpress configuration so that the
   DB variables that I want to use for this site show up last.
 * I suggest you include wp-config.php so that the proper vars are in place. There
   is a slight overhead but nothing huge.
 * Best regards,
    Edward
 *  Plugin Contributor [Jason Crouse](https://wordpress.org/support/users/coolmann/)
 * (@coolmann)
 * [13 years, 5 months ago](https://wordpress.org/support/topic/misconfigured-setting-2/#post-3288984)
 * Hi Edward,
 * Now this explains everything 🙂 Unfirtunately it’s not true that loading (and
   not parsing) wp-config only adds a little overhead. Why load the entire WP engine(
   about 40 megs of RAM!) when I don’t use any of it in that file? My plugin is 
   called “slim” stat for a reason, hehe…
 * Unfortunately I don’t see an easy way of solving your issue, other than telling
   you to manually change the source code of my plugin to include wp-config instead
   of parsing it. Also because it would be to accommodate the needs of a single 
   user who is doing something “non standard”.
 * If you come up with a better idea, feel free to share it on this forum!
 * Camu

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

The topic ‘misconfigured setting …’ is closed to new replies.

 * ![](https://ps.w.org/wp-slimstat/assets/icon.svg?rev=2832242)
 * [SlimStat Analytics](https://wordpress.org/plugins/wp-slimstat/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wp-slimstat/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wp-slimstat/)
 * [Active Topics](https://wordpress.org/support/plugin/wp-slimstat/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wp-slimstat/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wp-slimstat/reviews/)

 * 5 replies
 * 2 participants
 * Last reply from: [Jason Crouse](https://wordpress.org/support/users/coolmann/)
 * Last activity: [13 years, 5 months ago](https://wordpress.org/support/topic/misconfigured-setting-2/#post-3288984)
 * Status: resolved