Forum Replies Created

Viewing 10 replies - 61 through 70 (of 70 total)
  • Thread Starter zedrino

    (@zedrino)

    Here is a txt of the

    wp.config

    and the

    htaccess.

    thank you.

    Hi, I have the same problem, Erro 310 when I click on Update Network or Admin – Network Admin

    I just upgrade from WordPress MU 2.9 to WP 3.2.1 with the help of Ipstenu. Everything work fine except this issue and also something strange, I don’t have access to the sub-menu in Plugins, then can’t install or uninstall new plugins.

    I guess changed the wp-config and .htaccess correctly but may be I missed something. Really have no idea…

    Please have a look on :

    – my wp-config (copy in txt format for reading) here
    – and my htaccess

    if you think it can help (me and the developers I hope).

    Thanks for any help.

    PS also I tried the issu with the www suggested by Ipstenu but nothing changed.
    I deleted the coockies of this specific site too but no success.
    I use Chrome.

    All done, whaou so nice ans so easy. You are great !

    Still have this on the dashboard Thank you for Updating! Please visit the Update Network page to update all your sites. With the link not working. All sites are running 3.2.1

    Sorry,

    I just add the
    define(‘DB_COLLATE’, ”);
    define(‘VHOST’, ‘yes’);
    $base = ‘/’;
    define(‘DOMAIN_CURRENT_SITE’, ‘exemple.com’ );
    define(‘PATH_CURRENT_SITE’, ‘/’ );
    define(‘SITE_ID_CURRENT_SITE’, 1);
    define(‘BLOGID_CURRENT_SITE’, ‘1’ );

    to the config and it’s much better…of course..

    Ok I think I did everything and then the only result is that:

    One or more database tables are unavailable. The database may need to be repaired.

    Should I go to the link https://mybrokensite.com/wp-admin/maint/repair.php?referrer=is_blog_installed

    Any suggestion ?

    Why this is not existing any more in the wp-config.php ? thanks

    /** The Database Collate type. Don’t change this if in doubt. */
    define(‘DB_COLLATE’, ”);
    define(‘VHOST’, ‘yes’);
    $base = ‘/’;
    define(‘DOMAIN_CURRENT_SITE’, ‘exemple.com’ );
    define(‘PATH_CURRENT_SITE’, ‘/’ );
    define(‘SITE_ID_CURRENT_SITE’, 1);
    define(‘BLOGID_CURRENT_SITE’, ‘1’ );

    You right you right, that’s good and normal, no problem. Don’t want to upset nobody.

    Then you suggest me to manually update the WPMU 2.9.1 to WP 3.0. Then I suppose I can do automatic upgrade from 3.0 to the last version with the magic button.

    thanks for your help.

    Thank you for your time. Will think about it…

    Ok that’s the revolution:
    https://wpcandy.com/series-on/wordpress-3-2-in-depth
    WordPress 3.2 introduced an update to the automatic updates built into WordPress (you know, the functionality that lets you click one button and update your install) to allow for partial downloads. This meant that when automatically updating your WordPress site, after 3.2, only a partial download (of changes) would be necessary, and not a full copy.

    But nothing to do with updating from other version.

    I think my “so long to update” is not “so long”.

    Whaou jmaxlow, please could you tell me how you upgraded your MU 2.9.2 to the last version of WP because I’m finding different versions on the net and I’m pretty scared of doing something irrevocable (even if I backup all with Xclone).

    I have WPMU 2.9.1 and in fact I’m really surprised that the developers (who are doing an excellent and wonderful project that I love of course) let this bug in this stage: the upgrade button is not working and there is no way to easily upgrade the script (forbidden what ? back to the stone age of the internet or what !!??)

    I’m surprise because I have intentionally waited for the 3.2 because it was supposed to offer different options for upgrades. And there is nothing there except more trouble.

    Like many, I used MU to offer free blogs to my community and I really don’t want to mess up their sites/blogs (and I did the backups…again).

    I dont have enough knowledge to play with a broken database. I really don’t feel secure in modifying the wp-config for NONCE-SALT especially because de documentation is for wordpress 3.0 and not 3.2.1 (supposedly different).

    Again, I was waiting since a long time to switch to the new and unique version of WordPress, the 3.2, now I feel like… abandoned with my old MU and a bunch of people in my back waiting for me… I don’t want to crash the thing…

    Thanks anyway

    Thread Starter zedrino

    (@zedrino)

    Hmm, good thank you,
    the thing is my host does not have cpanel, but I’m going to try those scripts, thanks

Viewing 10 replies - 61 through 70 (of 70 total)