evardsson

I am getting the same error, but only on the sites that are updated via SVN and manual plugin upgrades. WP 3.0, Stats 1.7.2 (rolled back to 1.6.3 because it still works)

Another site I manage is on a hosting provider and is a “one-click” WP install, using the single-click upgrade buttons etc. On that site WP 3.0 with Stats 1.7.2 works just fine.

Still not sure what the difference is, unless it has something to do with the hosted site having more than one user and the others being one user only.

Where is it meant to save the settings (bit.ly account API key, ping.fm key, etc)?

I am unable to get any changes I make to stick. Should it be saving in the wp_options table, or should it be writing it into the shorten2ping.php file directly, or …?

Thanks,

PS – Once I get this working I am going to add hashtags for the ping (they don’t mean much in Facebook, MySpace, etc, but can be important in Twitter)

Adding these is simple –

$post_url = get_permalink($post_id);
    $post_title = get_the_title($post_id);
    // --- add some tag bits here ------ //
    $tags = wp_get_post_tags($post_id);
    $my_tag_list = '';
    if ($tags) {
    foreach ($tags as $j=>$tag) {
        $my_tag_list .= '#'.$tag->slug.' ';
    }
    // --- back to regular processing ----- //
    // --- cut for brevity ----- //
            //get message from settings and process title and link
            $message = $s2p_options['message'];
            $message = str_replace('[title]', $post_title, $message);
            $message = str_replace('[link]', $short_url, $message);
            // --- add the tags ----- //
            // --- ToDo: determine length and truncate Title(?) or Tags in order to fit in Twitter post //
            $message = str_replace('[tags]', $my_tag_list, $message);

It is interesting that the only fix seems to be a manual install from a tarball. I have been using SVN forever to upgrade my WordPress, and doing the switch to tags/2.7 causes the same fatal error every one else is seeing. So I did an experiment. I deleted everything they say to delete or overwrite in a manual install, and did an svn up. Theoretically, that should have solved it. It did not. I am now going to try doing a full svn checkout and copy my config file and theme over.

Well, that worked. Something is not behaving properly in the svn switch.