Title: Craig's Replies | WordPress.org

---

# Craig

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

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

 Search replies:

## Forum Replies Created

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

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[ActivityPub] Mastodon: Approve follow request](https://wordpress.org/support/topic/mastodon-approve-follow-request/)
 *  [Craig](https://wordpress.org/support/users/csmall2/)
 * (@csmall2)
 * [5 years, 7 months ago](https://wordpress.org/support/topic/mastodon-approve-follow-request/#post-13763212)
 * I’ve got the same issue. On my Mastodon instance, I search for the blog user.
   I click the “follow” button. The web server hosting the WordPress site gets a
   request and replies with a 202 response and that’s it!
 * “POST /wp-json/activitypub/1.0/users/1/inbox HTTP/1.1” 202 3005 “-” “http.rb/
   4.4.1 (Mastodon/3.2.1; +https://social.dropbear.xyz/)”
 * Nothing in the error logs.
 *   Forum: [Requests and Feedback](https://wordpress.org/support/forum/requests-and-feedback/)
   
   In reply to: [Old bug CVE-2012-5868](https://wordpress.org/support/topic/old-bug-cve-2012-5868/)
 *  Thread Starter [Craig](https://wordpress.org/support/users/csmall2/)
 * (@csmall2)
 * [12 years, 5 months ago](https://wordpress.org/support/topic/old-bug-cve-2012-5868/#post-4537232)
 * Thanks Samuel, I have updated the Debian bug tracker with some more details.
   
   I thought the underlying problem was that if you logout then someone could use
   the cookies to “revive” the session. As I didn’t report this and have adopted
   the Debian package only recently that take might be wrong. I was surprised by
   that, because session_destroy() is supposed to make that not happen.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[SlimStat Analytics] [Plugin: WP SlimStat] No footer js served on Debian installation = no humans](https://wordpress.org/support/topic/plugin-wp-slimstat-no-footer-js-served-on-debian-installation-no-humans/)
 *  Thread Starter [Craig](https://wordpress.org/support/users/csmall2/)
 * (@csmall2)
 * [15 years, 1 month ago](https://wordpress.org/support/topic/plugin-wp-slimstat-no-footer-js-served-on-debian-installation-no-humans/#post-2134910)
 * Will do once I work out the voting thingy. The Debian changes permit you to be
   a multi-site easily; unless you directly read the config file of course.
 * Now that the js script works I can see all the data!!
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[SlimStat Analytics] [Plugin: WP SlimStat] No footer js served on Debian installation = no humans](https://wordpress.org/support/topic/plugin-wp-slimstat-no-footer-js-served-on-debian-installation-no-humans/)
 *  Thread Starter [Craig](https://wordpress.org/support/users/csmall2/)
 * (@csmall2)
 * [15 years, 1 month ago](https://wordpress.org/support/topic/plugin-wp-slimstat-no-footer-js-served-on-debian-installation-no-humans/#post-2134900)
 * OK, I got the fix for this. The problem is Debian installations don’t use wp-
   config, but /etc/wordpress/config-<site>.php
 * I’m not sure how this can be handled without breaking other sites, but if you
   are running the Debian wordpress packages, edit line 15 of wp-slimstat-js.php
   from:
    `$wp_config = file_get_contents($wp_root_folder.'/wp-config.php');`
 * to look like:
 *     ```
       $debian_server = preg_replace('/:.*/', "", $_SERVER['HTTP_HOST']);
       $debian_server = preg_replace("/[^a-zA-Z0-9.\-]/", "", $debian_server);
       $debian_file = '/etc/wordpress/config-'.strtolower($debian_server).'.php';
       /* Main site in case of multisite with subdomains */
       $debian_main_server = preg_replace("/^[^.]*\./", "", $debian_server);
       $debian_main_file = '/etc/wordpress/config-'.strtolower($debian_main_server).'.php';
       if (file_exists($debian_file)) {
               $wp_config = file_get_contents($debian_file);
       } elseif (file_exists($debian_main_file)) {
               $wp_config = file_get_contents($debian_main_file);
       } else
               die("Cannot open config file");
       ```
   
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[SlimStat Analytics] [Plugin: WP SlimStat] No footer js served on Debian installation = no humans](https://wordpress.org/support/topic/plugin-wp-slimstat-no-footer-js-served-on-debian-installation-no-humans/)
 *  Thread Starter [Craig](https://wordpress.org/support/users/csmall2/)
 * (@csmall2)
 * [15 years, 1 month ago](https://wordpress.org/support/topic/plugin-wp-slimstat-no-footer-js-served-on-debian-installation-no-humans/#post-2134809)
 * OK, there are two separate problems.
 * The first is when I test from home I don’t get the script. The reason is that
   I’m running IPv6 and the ip2long tests all fail. That’s a reasonably simple explanation
   and its why I was not seeing the script. A couple of echos around the relevant
   parts of the code clearly show that is what is going on there.
 * The second problem is other times the js script gets loaded and then it goes 
   to GET wp-slimstat-js.php and we get the database problem. I can see in the apache
   logs those sorts of accesses but if I go there directly even with the right query
   string the database error occurs.

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