The MU forums have moved to WordPress.org

Problems upgrading. (1 post)

  1. nathanrdotca
    Member
    Posted 16 years ago #

    TROUBLESHOOTING
    Is VHOST true or false? true
    Is the path to your WordPress? MU install "/" or some directory? /
    Anything in the error logs? No.
    Did you receive any sort of error within your browser? No.
    Does the information in wp_blogs, wp_users and wp_site match your blog, user and site? Yes.
    Mention the version number, SVN check-in number or the date you downloaded the snapshot. 1.2.5 (freshly upgraded yesterday/10th Sept)
    Plugins in place? Have you tried turning them off and seeing if that affects the issue? Yes, yes and no, it doesn't.
    Server environment: Apache or IIS? What OS are you running? Apache/2.0.59 (Unix) DAV/2 PHP/4.4.4, custom Linux distro, info from uname -a is "Linux xorn 2.6.8-022stab078-up #1 Sun Sep 3 20:56:12 EDT 2006 i686 athlon-4 i386 GNU/Linux".
    Any proxy or cache server in place? No. iptables packet filtering but that's irrelevant.
    End user environment: Browser and version? (IE, Opera, Netscape, Safari?) OS? Security programs? Firefox 2.0.0.6 & IE 7 w/ XP Pro w/ Outpost Firewall & AVG Free (all correctly configured)

    I've posted this before, leading to some sort of kafuffle with drmike for which I'd like to apologise and let's just forget it happened. This is a support site and those who have the knowledge to help should volunteer that help without reservation.

    BACKGROUND
    I have a setup where my WPMU site is running one blog on a subdomain of a custom domain. This is the only blog it's hosting.

    PROBLEM:
    I seem to have some troubles upgrading my WPMU site.

    I go through the upgrade (replacing files, etc, I know the drill), then going to the Upgrade option in the WPMU admin panel.

    The error was:
    Warning:
    fopen(http://xblogs.cawp-admin/upgrade.php?step=1)
    [function.fopen]: failed to open stream: Success in
    /home/nathan/xblogs.ca/wp-admin/wpmu-upgrade-site.php
    on line 32

    You notice the missing slash? I fixed that.

    It hangs now. No errors.

    The solution was: to allow url_fopen in php.ini, right?
    Well, you can imagine my confusion when I was told that this setting has been on since day one.

    Now I'm stuck. Any thoughts?

    Before you ask, I've followed the upgrade instructions (except for backing things up, yes you can make fun of me for not doing that).

    I'll be grateful for any help, a customer's blog is in jeopardy. Since this downtime costs money (that my customer has already paid for), I'm willing to even pay for a solution if it'll get me one.

    I think that if I don't get a solution by the end of the week (time is money, as they say), I'll have to try my hand at converting the customer's blog into WordPress. At least with WP, I know my way around, this WPMU stuff is confusing.

    I'll update if I can scrounge up any new information.

About this Topic

  • Started 16 years ago by nathanrdotca