yearginsm

I’m fairly sure eelay meant a missing &, although I cannot be sure which one is which.

I also noticed the latest version (1.3.2) is not showing up in the plugin directory. You can get to it regardless (add 1 to the release number in the link to the zip file) but I thought it seemed a bit strange.

Mine is having an issue obtaining data. Here’s the log when I enabled the built-in debugger:

08-03-19 02:03:55 list is not in cache, get out and get it!
08-03-19 02:03:55 error fetching recenttracks xml
08-03-19 02:03:55 getlist returned false

Running PHP 5.2.5 (Open Solaris at Joyent) and WordPress 2.3.3.

Here’s the reference to short tags and why it’s causing mine to fail.

https://www.php.net/manual/en/ini.core.php#ini.short-open-tag

Fantastic! Thanks again for your hard work.

I too am having trouble with this. I on ocassion will get an e-mail from a visitor telling me my site is broken, even though I haven’t changed anything about my permalinks, and it worked fine immediately after posting. I’m on TextDrive and running the recent 2.2.3 upgrade via the subversion branch.

Here is the version that eventually took shape. It replaces against a lookup for {c:999}. I’m posting it here for anyone who might come across it.

function tnk_contact_filter($text)
{
    preg_match_all('/\{c:([0-9]+)\}/', $text, $brother);

    foreach ($brother[1] as $id)
    {
        $find[] = "/\{c:($id)\}/";
        $replace[] = tnk_contact_link($id);
    }

    if (!empty($id))
    {
        $text = preg_replace($find, $replace, $text);
    }

    return $text;
}

Resolved: The page called a remote JavaScript improperly. For whatever reason, this did not generate any errors in Firefox, but caused IE to fail once it left [head /] section.

Other pages, which do validate, are also invisible. I’m not the primary writer on the site, and haven’t had the chance to go behind and clean up the code in some of the posts. I’ll admit it is horrible.

Even stranger: Some IE users I’ve asked to check it report seeing the site fine, while others do not.

This would be a great addition to the Codex. Thanks for the great doc.

I used this version that I hacked out of the flickr plugin…

<?php

// Use Magpie (built into WordPress) //
if (!function_exists('MagpieRSS')) {
require_once (ABSPATH . WPINC . '/rss-functions.php');
error_reporting(E_ERROR);
};

$url = " <--- This is where your URI goes --->";
$rss = fetch_rss($url);

foreach ($rss->items as $item ) {
$title = $item[title];
$url = $item[link];
$desc = $item[description];

// PHP knowledge needed if you're wanting to change the format at all. This works well for me.
echo "<h3><a href=$url>$title</a></h3>n";
echo "<p>$desc</p>n";
};

?>

This works great on any feed that is not on my site. However, if I’m trying to load my own current feed on a page, Magpie goofs up and says that it was unable to fetch the feed, returning a HTTP/1.1 200 error (isn’t that a good thing, not bad?).

I’ve tried a few tricks to make it pass through a Google redirect and others, but I’m still against the same brick wall on it.

I’ve tried about three or four different queries for it, but nothing but this topic comes up in the search results. As an aside, I’m not a huge fan of the new search engine. ?? If you happen to come accross the link to it, mind dropping it in here?

Anybody know where the hook would be to redefine those variables rather than hacking the core? I’m sure this works, but I like my one-click updates too.

I usually download the “packaged” version from the author’s web site. For smaller plugins, I download the files off the wp-plugins.org site individually. I didn’t see an option to package the “trunk” on there.

Noticed in the source code of the Dashboard that the rest of the page (including the </body> and </html> tags are not loading either. This error appears to be with the coding itself.