New to the community? Start here

Activating WPMU Dev dashboard on a local dev server

Hi,

I'm developing on a local server (VM) with a non-real domain name, and I was wondering what the recommended way for using WPMUDev plugins in such a situation is? I can install on the live site and download the plugin files, but that's going to be a pain for keeping thins up-to-date, etc. Is there a different way I should be going about it? When I tried to just login into the dashboard on the dev site, it just timed out (as I rather expected it to).

Also, apologies if I screwed up trying to Live Chat somehow. I filled out the form twice, but it just went away and nothing happened, so I figured I did something wrong.

Sat, 8 Sep 2018 5:37:08
  • Adam
    • Support Gorilla

    Hello Technical Penguins

    I hope you’re well today!

    The WPMU DEV Dashboard can be installed on a local setups (I’m, for example, using it with WAMP and FlyWheel Local with no issues) just like on any live site. There are, however, two “pre-requisites” that should be taken care of:

    1. The WP install should use some rather “uncommon” URL so it shouldn’t be just “localhost” or “localhost:8181” or something like that, any “common” local domains might also not work. That’s because the same site cannot be assigned to more than a single account in The Hub and using e.g. “localhost” by multiple Members would mean just that.

    An acceptable address would be for example: “localhost/my-new-beta-site-001”. It’s just an example but the point is to make it unique.

    2. If it times out it might also be an issue of a local “connectivity”: you would want to make sure that no firewall is blocking connections either on your local machine or on your router/modem. You would also want to make sure that you got cURL enabled in your local PHP.

    Are you having any error messages when it times out? Have you checked WP debug.log and server error logs?

    You can enable WP debugging by adding following lines to the “wp-config.php” file of your local site:

    define('WP_DEBUG', true);
    
define('WP_DEBUG_LOG', true);
    
define('WP_DEBUG_DISPLAY', false);

    Make sure that they are above “/* That’s all, stop editing! */” line and it should produce a “debug.log” file inside /wp-content folder, which might give an additional clue on why that doesn’t work for you.

    Best regards,

    Adam