WordPress.org

Ready to get started?Download WordPress

Forums

Problem with Update Network after upgrade from WPMU (10 posts)

  1. wiesel82
    Member
    Posted 2 years ago #

    Hi all,
    i run successfully the update from WPMU to WP 3.3.1.
    Everything run fine and the most run without problems.

    Only 4 blogs have problems. It's not possible to run "Update Network". All 4 blogs start with blog.DOMAINNAME. And if i press "Update Network" it go to DOMAINNAME/wp-admin/network/upgrade.php and not blog.DOMAINNAME/wp-admin/network/upgrade.php. The same problem if i open directly blog.DOMAINNAME/wp-admin/network/upgrade.php it opens DOMAINNAME/wp-admin/network/upgrade.php.

    I think it's a bug in the script of "Update Nework".
    Does anybody know a solution to resolve this problem?

    Best regards
    Wiesel

  2. dgilmour
    Member
    Posted 2 years ago #

    i run successfully the update from WPMU to WP 3.3.1.
    Everything run fine and the most run without problems.

    Given the problems you're seeing, it's not true to say you've run the update successfully.

    The first step here is to understand the extent of the upgrading you've been attempting to do, and whether you did it in the correct way.

    What version of WPMU did you upgrade from? The term WPMU was used up to V2.9.2, when WPMU was merged into the core WordPress code.

    Did you follow the instructions for upgrading WPMU here? http://codex.wordpress.org/Upgrading_WPMU

  3. wiesel82
    Member
    Posted 2 years ago #

    Ok i upgraded 2.8.5.2 to WPMU 2.9.2 and than to 3.3.1 by following the instruction step by step. But the same problem.

    I had 30 blogs.
    26 were updated successful and 4 can't be updated with "Update Nework".

    This 4 blogs starts with blog.DOMAINNAME.TLD.

    Everytime if i press the "Update Nework" button in wp-admin i will be moved to DOMAINNAME/wp-admin/network/upgrade.php.

  4. Ok i upgraded 2.8.5.2 to WPMU 2.9.2 and than to 3.3.1

    You should have gone from 2.9.2 to 3.0 manually, and THEN 3.3... I hope you did.

    This 4 blogs starts with blog.DOMAINNAME.TLD.

    Are you using a domain mapping plugin?

  5. wiesel82
    Member
    Posted 2 years ago #

    > You should have gone from 2.9.2 to 3.0 manually, and THEN 3.3... I hope you did.

    I test it also from 2.9.2 to 3.0 and then to 3.3.1.
    Result the upgrade from 2.9.2 to 3.0 worked fine but i got the same problem after the upgrade to 3.3.1. This 4 blogs can't be updated.

    > Everytime if i press the "Update Nework" button in wp-admin i will be moved to DOMAINNAME/wp-admin/network/upgrade.php.

    All Plugins were deactivated by update to 3 and 3.3.1.

  6. Are you using a domain mapping plugin?

  7. wiesel82
    Member
    Posted 2 years ago #

    No, i don't use a domain mapping plugin.

  8. Where is WP installed?

    blog.example.com or example.com?

  9. wiesel82
    Member
    Posted 2 years ago #

    example.com is WP installed.
    And this 4 Blogs like
    blog.exam.com
    blog.sample.com
    ...

  10. That doesn't make ANY sense.

    You get two options with WordPress Multisite, if you're not mapping domains, and you installed in example.com:

    1) Subdomains: site1.example.com, site2.example.com, etc etc.

    2) Subfolders: example.com/site1, example.com/site2

    So ... there's no way, WITHOUT mapping domains, for you to install in example.com and get subsites of blog.otherdomain.com

Topic Closed

This topic has been closed to new replies.

About this Topic

Tags

No tags yet.