• As I have around ten sites running in Norwegian, I prefer to install WP in my native language. However, for 3.5.1, this has proven to be a major concern. Trying the 3.5.1-nb_NO fails on all sites.

    Using the default US-version works 100% without a flaw.
    Retrying the nb_NO version after the US install seems to work, but then I get warning that 3.5.1 is available …..

    Any idea what this could be? Is it th nb_NO version only, or does anyone else have an issue with “national” editions for 3.5.1?

    Best regards,
    Hans

Viewing 12 replies - 1 through 12 (of 12 total)
  • Trying the 3.5.1-nb_NO fails on all sites.

    In what way does it fail? Can you give us as much detail as possible please?

    Thread Starter Hans

    (@hansu)

    Hi,
    Trying 3.5.1-nb_NO as first upgrade option, after some considerable time (about 4-5 times longer than processing the US version) the panel returns as if nothing has happened, and displays the message that a new version 3.5.1 is available for installation. The version stamp at the bottom of the page still reads 3.5.0.
    Using the default WP-install package (UK/US), the process is about one/fifth of the faulty nb_NO one, and everything looks a-ok to me.

    Can you have a look in your site’s error logs for any errors around the time you tried the 3.5.1-nb_NO upgrade?

    Thread Starter Hans

    (@hansu)

    Sorry, but no error-logs are active, so no trace available at this time.

    Your server doesn’t have any error logs?

    Thread Starter Hans

    (@hansu)

    esmi,
    “My server” is hosted by a remote company, i.e. I do not have access to their logs.
    As for my WP installs, all of these have WP_DEBUG set to false, have had no reason so far to change it ??

    Most hosts allow access to site specific error logs – even on shared servers. What I’m trying to figure out is whether the 3.5.1-nb_NO upgrade simply timed out.

    Thread Starter Hans

    (@hansu)

    Copied, but to me it looked like it went through the entire install process (longer processing time as noted), without displaying any error-messages, ending up with no version change at all.

    As I tried the nb_NO install on more sites, this was not a site-specific issue, but a general one.
    Sorry for not being able to pinpoint this any better, or clearer.

    Had the same problem as Hans.

    Just checked my error-logs and there is nothing there.

    My way around the problem was to open the wp_config file, remove nb_NO, reload the wp-admin page. Update and then put back nb_NO in wp_config

    Thread Starter Hans

    (@hansu)

    Hi arvem,

    Thanks for the tip, must admit I only checked the wp_config.php after the failed install to confirm it still included WPLANG ‘nb_NO’.

    But, did you re-install the 3.5.1-nb_NO AFTER this, or did you just skip the Norwegian version all together (besides having WPLANG as nb_NO)??

    No I didn`t re re-install 3.5.1-nb_NO. I only made changes to the wp-config file

    Thread Starter Hans

    (@hansu)

    Thank you, appreciate it!

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘nb_NO version issue’ is closed to new replies.