ilen

No help? Please??

This happens for all images; it is not an issue of image corruption. I’m looking for help with how to troubleshoot the server or wordpress configuration.

That’s the image, which is how I know there’s no problems with the image; it works fine when I host it on a different site.

Doing a manual upgrade seems to have fixed it. Not sure what went wrong…

don’t have twenty eleven yet; isn’t that part of the upgrade?

We’re using a couple of different custom themes. Should I reset them all? If so, do I do that in the db?

there is an empty “upgrade” folder that was created… should it have contents?

no, renaming plugins folder doesn’t help. still getting a blank screen.

THANK YOU!!!

Darn. Should have mentioned that this was specifically about the “Redirection” plugin.

Andrea. Edge case indeed. ??

I inherited this installation — the person who installed it is no longer with the company, so I’m a bit at sea. I’ve only ever dealt with a “normal” installations before and everything usually just works. This is also my first time using the multisite feature, so a bit of a learning curve yet to climb.

I’ve seen other references to “debianized” wordpress sprinkled here and there throughout the forums, but I can’t find the README referred to anywhere on my server or the web.

At this point I will try updating the db. If that fails, I will try re-installing WP manually and using the import feature.

One last question: My company’s current site responds to “companyname.com” and “companynamemisspelled.com” will the latter stop working once I point dns to the wordpress instance?

Thanks again!

sorry, should have been more specific.

the wp install I inherited is a little funky. it replaces the wp-config.php with a new file.

Specifically, wp-config.php instead of having the normal contents contains this:

/** WordPress's Debianised default master config file
Please do NOT edit and read about how the configuration works in the README.Debian
**/

    #https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=435289
    #https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=440572 (underscores, not dashes)
    $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';

    if (!file_exists($debian_file)) {
        header("HTTP/1.0 404 Not Found");
  echo "<b>$debian_file</b> could not be found. The file is either not readable by this process or does not exist. <br>
    Please check if <b>$debian_file</b> exists and contains the right password/username.";
        exit(1);
    }

    require_once($debian_file);

With the acutaly wp-config code in a file named config-mydomaingoeshere.php

Sadly, copying that file to config-mynewdomaingoeshere.php results in an “Error establishing database connection” message – presumably this is because I need to do search and replace on my db.

Is there just an easy way to have wp respond to both myIP and mynewdomain?

Thanks for all of your help … it can be a bit challenging to understand which bits of the documentation apply to what situations.

Andrea, I mention the OS because with the debian install of wordpress I don’t have a wp-config.php, per se.

Tim —

On the Settings->General screen in a single site installation of WordPress, there are two fields named “WordPress address (URL)” and “Site address (URL)”.

Those directions seem to be for a single site, have you used them successfully for multisite? Which of the four approaches documented would you recommend for debian install of a network with subdirectories?

Thanks.

Thanks for the response… I found the errant link category that was causing my troubles.

LOVE the plugin, by the way!