New to the community? Start here

site just went down, only thing done was update a handful of plugins

a new site I’m working on (fortunately still under development) won’t load… i.e. a blank screen is all that I get: http://tinyurl.com/mj5zkp

all I’ve done:

– I updated the following plugins (basically those that saw updates in July), only by uploading the files, hadn’t opened wp-admin yet:

ad sharing, admin ads, admin footer text, avatars, friends, mailchimp, recent global comments, comment indexer, remove email verification, supporter

– I updated .htaccess for the avatars plugin (& then reverted it, no dice).

any ideas of what I can look into to get this site active again? I’m at a loss here.

thanks,

scott

Mon, 3 Aug 2009 13:53:09
  • drmike
    • DEV MAN’s Mascot

    Need a correct url please. Tinyurl and other redirection services are blocked as porn sites here at the library, brueggers and with most security (ie censorship) filters. Not really kosher either to make folks you;re asking for help from to jump through hoops.

    – Always step 1: Check the webserver’s error logs. SHould be done even before posting about the problem.

    – Rename the plugin and mu-plugins subdirectories so they won’t load,

    – Return the htaccess file to the original form.

    – Recreate the plugin and mu-plugins subdirectories but leave them blank and empty.

    – Give your mu install a try.

    – If it works, return the plugins one at a time while testing to see which plugin causes the fail. Probably a good idea to do that when upgrading. One step at a time then test. Especially when you go live.

    – If it doesn’t work, best bet would be to delete the mu install including the databases and do a reinstall. Again, be sure to check the error logs to see what’s in there.

  • Scott Pruett
    • Design Lord, Child of Thor

    thanks!

    url is realestatephotos.me. sorry, just trying to avoid google grabbing it early :slight_smile:

    I checked the server logs, nothing.

    I "fixed" .htaccess, nothing.

    I renamed /mu-plugins… that fixed it. So the problem is indeed a mu plugin. I just need to figure out which one is the culprit. WPMU is up to date. I simply updated the plugins to eliminate conflicts, if any, that could arise w/ the new WP version.