• I converted over to 1.2.1 and my wordpress installation broke. So, I diffed my installation with the new stuff, removed any index/template stuff, and applied the changes one file at a time.
    I’m running FreeBSD 5.3 patch branch with the following ports:
    mathopd-1.5p3 A very small, yet very fast HTTP server
    php4-cgi-4.3.9 PHP Common Gateway Interface
    php4-mysql-4.3.9 The mysql shared extension for php
    php4-pcre-4.3.9 The pcre shared extension for php
    I’ve tried both updating my wordpress 1.2.0, and using a clean unzip with just my wp-config.php file copied over, neither worked.
    So, here’s a diff of the changes that are causing problems:

    diff -ubBr wordpress/wp-includes/functions-formatting.php wordpress-1.2.1/wp-includes/functions-formatting.php
    --- wordpress/wp-includes/functions-formatting.php Fri May 21 23:35:16 2004
    +++ wordpress-1.2.1/wp-includes/functions-formatting.php Tue Oct 5 19:39:08 2004
    @@ -78,6 +78,47 @@
    return $pee;
    }
    +
    +function seems_utf8($Str) { # by bmorel at ssi dot fr
    + for ($i=0; $i<strlen($Str); $i++) {
    + if (ord($Str[$i]) < 0x80) continue; # 0bbbbbbb
    + elseif ((ord($Str[$i]) & 0xE0) == 0xC0) $n=1; # 110bbbbb
    + elseif ((ord($Str[$i]) & 0xF0) == 0xE0) $n=2; # 1110bbbb
    + elseif ((ord($Str[$i]) & 0xF8) == 0xF0) $n=3; # 11110bbb
    + elseif ((ord($Str[$i]) & 0xFC) == 0xF8) $n=4; # 111110bb
    + elseif ((ord($Str[$i]) & 0xFE) == 0xFC) $n=5; # 1111110b
    + else return false; # Does not match any model
    + for ($j=0; $j<$n; $j++) { # n bytes matching 10bbbbbb follow ?
    + if ((++$i == strlen($Str)) || ((ord($Str[$i]) & 0xC0) != 0x80))
    + return false;
    + }
    + }
    + return true;
    +}
    +
    +function remove_accents($string) {
    + $chars['in'] = chr(128).chr(131).chr(138).chr(142).chr(154).chr(158)
    + .chr(159).chr(162).chr(165).chr(181).chr(192).chr(193).chr(194)
    + .chr(195).chr(196).chr(197).chr(199).chr(200).chr(201).chr(202)
    + .chr(203).chr(204).chr(205).chr(206).chr(207).chr(209).chr(210)
    + .chr(211).chr(212).chr(213).chr(214).chr(216).chr(217).chr(218)
    + .chr(219).chr(220).chr(221).chr(224).chr(225).chr(226).chr(227)
    + .chr(228).chr(229).chr(231).chr(232).chr(233).chr(234).chr(235)
    + .chr(236).chr(237).chr(238).chr(239).chr(241).chr(242).chr(243)
    + .chr(244).chr(245).chr(246).chr(248).chr(249).chr(250).chr(251)
    + .chr(252).chr(253).chr(255);
    + $chars['out'] = "EfSZszYcYuAAAAAACEEEEIIIINOOOOOOUUUUYaaaaaaceeeeiiiinoooooouuuuyy";
    + if (seems_utf8($string)) {
    + $invalid_latin_chars = array(chr(197).chr(146) => 'OE', chr(197).chr(147) => 'oe', chr(197).chr(160) => 'S', chr(197).chr(189) => 'Z', chr(197).chr(161) => 's', chr(197).chr(190) => 'z', chr(226).chr(130).chr(172) => 'E');
    + $string = utf8_decode(strtr($string, $invalid_latin_chars));
    + }
    + $string = strtr($string, $chars['in'], $chars['out']);
    + $double_chars['in'] = array(chr(140), chr(156), chr(198), chr(208), chr(222), chr(223), chr(230), chr(240), chr(254));
    + $double_chars['out'] = array('OE', 'oe', 'AE', 'DH', 'TH', 'ss', 'ae', 'dh', 'th');
    + $string = str_replace($double_chars['in'], $double_chars['out'], $string);
    + return $string;
    +}
    +
    function sanitize_title($title) {
    $title = do_action('sanitize_title', $title);
    @@ -85,6 +126,7 @@
    }
    function sanitize_title_with_dashes($title) {
    + $title = remove_accents($title);
    $title = strtolower($title);
    $title = preg_replace('/&.+?;/', '', $title); // kill entities
    $title = preg_replace('/[^a-z0-9 _-]/', '', $title);

    Applying everything else that 1.2.1 changes doesn’t affect my installation, but that diff does. If you go to <http://test.weller-fahy.com&gt; you’ll see a broken installation, <http://weller-fahy.com&gt; is working (without the above patch).
    Anyone have any suggestions?

Viewing 4 replies - 1 through 4 (of 4 total)
  • Did you run wp-admin/upgrade.php after uploading all of the 1.2.1 files?

    Thread Starter sinecure

    (@sinecure)

    Yep, tried that, and I still have the same problem.

    Not sure if I am having the same problem, but on trying to upgrade from 1.0.2 to 1.2.1, the upgrade happened normally, but I couldn’t login. I ran upgrade.php a couple of times, and fortunately had zipped up a backup of the entire directory structure.
    I restored and tried copying the files again, thinking I messed it up, and got the same results. Everything worked except the login. Being completely hopeless at programming, I tried extracting the old login.php file and replacing just that with the upgrade and, magically, it worked.
    Scott Shultis
    wordpress.uncomplicated.net

    Thread Starter sinecure

    (@sinecure)

    Hrm. I don’t think you’re having the same problem. I’ve been able to narrow mine down to line 129 of the file wp-includes/functions-formatting.php (in 1.2.2, as I’ve recently upgraded to that). If I comment that line out everything works as advertised, otherwise my webpage stops rendering halfway through the right-side floater (which means no content).

    My upgrade to 1.2.2 just reminded me that I never found a solution other than commenting that line out. Any suggestions for further steps to trouble-shoot from a guru/programmer? ;]

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Problem with 1.2.1 upgrade’ is closed to new replies.