FeedWordPress 0.97: one small increment for the revision number, one giant leap for the software(posted on 06 November 2005)

Update 2007-11-21: FeedWordPress 0.97 is now out of date. You can download the latest release — 0.991 at the time of this writing — from the project homepage.

Huzzah! FeedWordPress 0.97 is now available for download (also in zip format, if you’re in to that kind of thing). Enjoy, and please feel free to report any problems you have with the software or the documentation to me in the comments section below or by e-mail.

Version 0.97 represents major changes, I hope for the better, on several fronts in FeedWordPress. (If I weren’t running out of revision numbers between the current version and 1.0, I would have added a lot more than 0.01 to the version. Stupid decimal notation.) This release will address several long-standing bugs, and hopefully also make other bugs easier to diagnose and to fix. First, the minor inconvenience that this update will impose on you if you are upgrading:

  • INSTALLATION PROCEDURE: Some of the changes between 0.96 and 0.97 require upgrades to the meta-data stored by FeedWordPress to work properly. Thus, if you are upgrading from 0.96 or earlier to 0.97, most FeedWordPress operations (including updates and template functions) WILL BE DISABLED until you run the upgrade procedure. Fortunately, running the upgrade procedure is easy: just go to either Options –> Syndication or Links –> Syndicated in the WordPress Dashboard and press the button.

Now, the fun stuff. The most important are the new, humane interface for setting feed-specific settings (check it out under Links –> Syndicated –> Edit … no more nerding around with key-value pairs!), Atom 1.0 support, and the overhaul of update-feeds.php. Details follow:

  • FEED FORMAT SUPPORT: Support has been added for the Atom 1.0 IETF standard. Several other elements are also newly supported (dcterms:created, dcterms:issued, dcterms:modified, dc:identifier, proper support for the RSS 2.0 guid element, the RSS 2.0 author element, the use of Atom author or Dublin Core dc:creator constructs at the feed level to identify the author of individual items, etc.)

    N.B.: full support of several Atom 1.0 features, such as categories and enclosures, requires you to install the optional rss-functions.php upgrade in your wp-includes directory.

  • BUG FIX: Running update-feeds.php from command line or crontab returned “I don’t syndicate…” errors. It turns out that WordPress sometimes tramples on the internal PHP superglobals that I depended on to determine whether or not the script was being invoked from the command line. This has been fixed (the variables are now checked before WordPress can trample them). Note that update-feeds.php has been thoroughly overhauled anyway; see below for details.

  • BUG FIX: Duplicate categories or author names. Fixed two bugs that could create duplicate author and/or category names when the name contained either (a) certain international characters (causing a mismatch between MySQL and PHP’s handling of lowercasing text), or (b) characters that have a special meaning in regular expressions (causing MySQL errors when looking for the author or category due to regexp syntax errors). These should now be fixed thanks to careful escaping of names that go into regular expressions and careful matching of lowercasing functions (comparing results from PHP only to other results from PHP, and results from MySQL only to other results from MySQL).

  • BUG FIX: Items dated Decembr 31, 1969 should appear less often. The function for parsing W3C date-time format dates that ships with MagpieRSS can only correctly parse fully-specified dates with a fully-specified time, but valid W3C date-time format dates may omit the time, the day of the month, or even the month. Some feeds in the wild date their items with coarse-grained dates, so the optional rss-functions.php upgrade now includes a more flexible parse_w3cdtf() function that will work with both coarse-grained and fully-specified dates. (If parts of the date or the time are omitted, they are filled in with values based on the current time, so ‘2005-09-10′ will be dated to the current time on that day; ‘2004′ will be dated to this day and time one year ago.

    N.B.: This fix is only available in the optional rss-functions.php upgrade.

  • BUG FIX: Evil use of HTTP GET has been undone. The WordPress interface is riddled with inappropriate (non-idempotent) uses of HTTP GET queries (ordinary links that make the server do something with significant side-effects, such as deleting a post or a link from the database). FeedWordPress did some of this too, especially in places where it aped the WordPress interface (e.g. the “Delete” links in Links –> Syndicated). That’s bad business, though. I’ve changed the interface so that all the examples of improper side-effects that I can find now require an HTTP POST to take effect. I think I got pretty much everything; if there’s anything that I missed, let me know.

    Further reading: [Sam Ruby 2005-05-06: This Stuff Matters] (http://www.intertwingly.net/blog/2005/05/06/This-Stuff-Matters)

  • BUG FIX: Categories applied by cats setting should no longer prevent category-based filtering from working. In FeedWordPress, you can (1) apply certain categories to all syndicated posts, or all posts from a particular feed; and (2) filter out all posts that don’t match one of the categories that are already in the WordPress database (allowing for simple category-based filtering; just load up WordPress with the categories you want to accept, and then tell FeedWordPress not to create new ones). However, the way that (1) and (2) were implemented meant that you couldn’t effectively use them together; once you applied a known category to all syndicated posts from a particular feed, it meant that they’d have at least one familiar category (the category or categories you were applying), and that would get all posts past the filter no matter what categories they were originally from.

    Well, no longer. You can still apply categories to all syndicated posts (using either Syndication –> Options, or the feed-level settings under Links –> Syndicated). But these categories are not applied to the post until after it has already passed by the “familiar categories” filter. So now, if you want, you can do category filtering and then apply as many categories as you please to all and only posts that pass the filter.

  • BUG FIX: Other minor typos and HTML gaffes were fixed along the way.

  • PERFORMANCE: getfeedmeta() no longer hits the database for information on every call; it now caches link data in memory, so FeedWordPress only goes to the database once for each syndicated link. This may substantially improve performance if your database server resources are tight and your templates make a lot of use of custom settings from getfeedmeta().

  • API CHANGE: Link ID numbers, rather than RSS URIs, are now used to identify the feed from which a post is syndicated when you use template functions such as getfeedmeta(). The practical upshot of this is you can switch feeds, or change the feed address for a particular syndicated site, without breaking your templates for all the posts that were syndicated from the earlier URI.

  • API CHANGE: if you have plugins or templates that make use of the getfeedmeta() function or the $fwpfeedmeta global, note that the data formerly located under the uri and name fields is now located under the link/uri field and the link/name field, respectively. Note also that you can access the link ID number for any given feed under the global $fwpfeedmeta['link/id'] (in plugins) or getfeedmeta(’link/id’) (in a template in post contexts).

  • FEATURE: the settings for individual feeds can now be edited using a humane interface (where formerly you had to tweak key-value pairs in the Link Notes section). To edit settings for a feed, pick the feed that you want under Links –> Syndicated and click the Edit link.

  • FEATURE: The “Unsubscribe” button (formerly “Delete”) in Links –> Syndicated now offers three options for unsubscribing from a feed: (1) turning off the subscription without deleting the feed data or affecting posts that were syndicated from the feed (this works by setting the Link for the feed as “invisible”); (2) deleting the feed data and all of the posts that were syndicated from the feed; or (3) deleting the feed data and keeping the posts that were syndicated from the feed setting the Link to “Invisible” (meaning that it will not be displayed in lists of the site links on the front page, and it won’t be checked for updates; (2) deleting the Link and all of the posts that were syndicated from its feed; or (3) deleting the feed data but keeping the posts that were syndicated (which will henceforward be treated as if they were local rather than syndicated posts). (Note that (1) is usually the best option for aggregator sites, unless you want to clean up the results of an error or a test.)

  • FEATURE / BUG FIX: If you have been receiving mysterious “I don’t syndicate…”, or “(local) HTTP status code was not 200″, or “(local) transport error – could not open socket”, or “parse error – not well formed” errors, then this update may solve your problems, and if it does not solve them, it will at least make the reasons for the problems easier to understand. That’s because I’ve overhauled the way that FeedWordPress goes about updating feeds.

    If you use the command-line PHP scripting method to run scheduled updates, then not much should change for you, except for fewer mysterious errors. If you have done updates by sending periodic HTTP requests to http://your-blog.com/path/wp-content/update-feeds.php, then the details have changed somewhat; mostly in such a way as to make things easier on you. See the README file or online documentation on Staying Current for the details.

  • FEATURE: FeedWordPress now features a more sophisticated system for timed updates. Instead of polling every subscribed feed for updates each time update-feeds.php is run, FeedWordPress now keeps track of the last time it polled each feed, and only polls them again after a certain period of time has passed. The amount of time is normally set randomly for each feed, in a period between 30 minutes and 2 hours (so as to stagger updates over time rather than polling all of the feeds at once. However, the length of time between updates can also be set directly by the feed, which brings us to …

  • FEATURE: FeedWordPress now respects the settings in the ttl and Syndication Module RSS elements. Feeds with these elements set will not be polled any more frequently than they indicate with these feeds unless the user manually forces FeedWordPress to poll the feed (see Links –> Syndicated –> Edit settings).

Advertisement

Replies to FeedWordPress 0.97: one small increment for the revision number, one giant leap for the software (93 so far…) Syndication feed

  1. hipocratico says:

    I must be something wrong.

    In the last version I used to update with: http://mysite.com/blog/wp-content/update-feeds.php?shibboleth=secretword

    With no problems at all.

    I couldn´t get my contributors to ping to my site…their post never appeared.

    Now this option dissapeared, and I still can get the pingins service on.

    Any help?

  2. Rad Geek says:

    Hi hipcratico,

    I knew there was something I was forgetting in my updates to the documentation.

    I mention this but I should have made it much more prominent in the initial post. If you use the update-feeds URI to update your syndication site, you need to use a new format. You can update manually with:

    http://mysite/blog/wp-content/update-feeds.php

    And if you want to update from a cron job, you can do so by sending an HTTP POST request, with the username and password of one of the users in your WordPress database for authentication. So, for example, if you’re using curl:

    curl --user login:pass http://mysite.com/blog/wp-content/update-feeds.php -d update=quiet
    

    Where “login” and “pass” can be anybody in your WP database.

    Does this fix your problem?

  3. hipocratico says:

    Thanks, I´ll try that…I´m not using cron jobs, because I don´t know how to use it.

    My host doesn´t have cpanel, which I know it could be easier to use.

    So I manage so far to do it “manually”.

    With this new version, what is the use of the “secret word” at options—>syndication?

  4. hipocratico says:

    Another question…when updating, do you have to INACTIVATE, the older plugin first?

  5. hipocratico says:

    Ok, I manage to update manually. But I used:

    http://mysite/blog/wp-content/update-feeds.php

    and add: “www”

    http://”www”.mysite/blog/wp-content/update-feeds.php

    I just can´t get someone to ping to the blog, still

  6. Hi, just upgraded to 0.97 Excellent work! I’m having trouble though getting the feed updates to work with cron. I’m running the cron as /usr/bin/curl –user peter:abc http://xyz.com/blog/wp-content/update-feeds.php -d update=quiet

    And get this as a result: ERROR: Could not log in as ”/pass=”]

    Any ideas?

  7. Rad Geek says:

    best web hosting provider:

    > And get this as a result: > ERROR: Could not log in as ”/pass=”]

    Well, as you may have guessed update-feeds.php doesn’t seem to be receiving the HTTP Authentication data like it should. This may be an issue with your version of cURL, or it may be an issue with the way that PHP is configured on your host. In any case, FWP allows you to use HTTP POST variables as a fall-back; so try:

    /usr/bin/curl http://xyz.com/blog/wp-content/update-feeds.php -d update=quiet -d log=peter -d log=abc
    

    Let me know if this solves your problem.

    hipocratico:

    > Thanks, I’ll try that… I’m not using cron jobs, because I don’t know how to use it.

    If your web host provides you with access to a shell prompt, you can connect with SSH and then set up a crontab the command:

    > crontab -e

    This should bring up a text editor such as emacs or joe, probably with an empty file. (If the file is not empty, you’ll just add the data on the next empty line). Add a line something like this:

    > */30 * * * * curl –silent –user login:pass http://xyz.com/wp-content/update-feeds.php –data update=quiet

    … changing login, pass, and http://xyz.com/ to the real values for your setup, of course. The first five fields are time fields; the way I have it here will cause a POST request to be sent to update-feeds.php every 30 minutes. For nitty-gritty, pull up man 5 crontab.

    If your host doesn’t allow you to get to a shell prompt, you can e-mail them to see if there is any way for you to set up cron jobs. If not, let me know; there are some jury-rigged set-ups you could try.

    > With this new version, what > is the use of the “secret > word” at options—>syndication?

    It still provides light security for the XML-RPC update interface: FeedWordPress updates all URIs when it receives a request to update a particular “magic” URI, and if the “magic” URI is the same for all installations someone could theoretically try to gum up your server by blasting you with update-all requests over and over again. It isn’t really a very big threat, though, and I’m considering eliminating the ability to update all from the XML-RPC interface in upcoming versions anyway (now that update-feeds.php does not use the XML-RPC interface, there’s not much reason to honor XML-RPC requests for the “magic” URI). But there are a lot of things further up on the priority list than deciding what to do about it.

    > Another question…when updating, do you have to INACTIVATE, the older plugin first?

    No. You can just copy the files in place. All the critical code is in a single file, so even if FWP tries to update in the middle of your installation there shouldn’t be any real problem.

  8. Thanks for the tip! I’m still getting the same error. Will check with my hosting provider.

  9. btw, it seems like the end of the curl line should read: update=quiet -d log=peter -d pwd=abc

    note the second pwd. Is that correct? The update-feeds.php seemed to reference ‘pwd’

  10. voila! looks like it worked with ‘pwd’ in there; as mentioned in the previous post.

    Thanks!!

  11. hipocratico says:

    I could access to the shell prompt, and into the editor.

    Now for the next 2 questions, and sorry if I sound so dumb.

    The user and pass are the ones you use to get to the server or to the blog?

    If the user is “hipo” and pass “me”, the line must be:

    */30 * * * * curl –silent –user hipo:me http://xyz.com/wp-content/update-feeds.php –data update=quiet

    if that´s correct?

    Thanks

  12. Rad Geek says:

    hipocratico:

    Don’t worry about asking — like most Unix things, cron is very useful but also pointlessly arcane.

    The username and password that you should use are a username and password that will log you in to the WordPress Dashboard. Not the username and password you use to log in to the shell prompt. The line you have above is basically correct; but you should use two dashes in front of the silent, user, and data options. (Sorry about that! I hadn’t noticed that WordPress was converting double dashes into a single em dash until after I saw your comment. So the line should be:

    */30 * * * * curl --silent --user hipo:me http://xyz.com/wp-content/update-feeds.php --data update=quiet
    

    Hope this helps.

  13. Rad Geek says:

    best web hosting provider:

    > btw, it seems like the end of the curl line should read: [...]

    Yep! My mistake.

    So here’s the correct line. Backslashes represent the continuation of a single line, not literal backslashes:

    /usr/bin/curl http://xyz.com/blog/wp-content/update-feeds.php \
         -d update=quiet \
         -d log=peter \
         -d pwd=abc
    

    Thanks for the typo catch.

  14. hipocratico says:

    I just can´t get to update. I used “crontab -e”, the text editor appeared, copy-paste the line you wrote, with the correct user-pass. I set it to 10 (10 mins). Nothing happened.

    I save the line after I exit the editor. I think there´s no problem there.

    Do I have to CHMOD the archives?

    Is there hope for me?

  15. ServerTastic says:

    Excellent plugin. Had it up and working in a few minutes.

    I’d like to make a suggestion. When syndicating we have the permalink option set to our website as I want to encourage comments about the feed on our site as well as maintain the visitor longer.

    However I would also like to show the link that the RSS article originally linked to. So can this be added as an option to show within the post body the original feed link.

  16. Calnet says:

    Dear Charles,

    I must be doing something wrong. I’ve been trying to figure this out for a few days but I cannot.

    After the fresh installation of feedwordpress 0.97, I am unable to view the “Syndication” tab under option. Can you please tell me what I should look into? (I’m using wpmu.)

    Thank you alot! Calnet

  17. John says:

    Hi Rad,

    I really do like your fedwordpress plugin-it is great.

    I have a couple of questions though…..

    Firstly I use the format GET http://www.xyz.info/wp-content/update-feeds.php?shibboleth=password

    to update my cron, what will be the new format for my crons now?

    Also, for some reason the rss2 feed generated keeps reporting parser errors, although it is from yahoo and works well.

    I would be greatful for your help

    your sincerly John

  18. John says:

    Hi Rad,

    Is there a way in which I can limit the amount of post that feedwordpress post at any one time?

    For example, my sports blog pulls in a lot of posts, sometimes 20 odd. I would really like to adjust the amount of posts that are posted or set a maximum limit.

    thanks as always john

  19. [...] r WordPress che permette di aggregare news provenienti da altre fonti sul proprio blog. Le novit sono tan [...]

  20. [...] /2005/11/15/340/” rel=”bookmark” title=”Permanent Link: “> Aggiornamento di FeedWordPress [...]

  21. Kim P says:

    Hi Rad,

    I have a problem with the timestamp of the feeds. It seems like it’s odd by 6 hours. But it is actually the local servertime, so I wonder if there’s something wrong with the feeds. I am using both rss2 and blogspots atom-feed.

    Still I guess it should be possible to configure the “fallback-offset” to some other value than the local servertime, but how/where ???

  22. EJ says:

    I am having consistent problems with the crontab and getting the job to go thru.

    With the original setting you provide,

    8 * * * * cd $HOME/http://yoursite.com/etc

    the CRON mailer sends me a message stating that the PHP command does not work.

    with the other cron jobs you suggest,

    curl –user login:pass http://mysite.com/blog/wp-content/update-feeds.php -d update=quiet

    and

    /usr/bin/curl http://xyz.com/blog/wp-content/update-feeds.php -d update=quiet -d log=peter -d log=ab (or pwd=ab, either one)

    I am getting the following from the mailer when it attempts:

    curl: option -d: requires parameter curl: try ‘curl –help’ or ‘curl –manual’ for more information

    All of the necessary CHMOD stuff is done. I have also tried using the secretword to no avail. The commands work from within the bash shell if I run them from a command line, but the cron job will not complete.

    Any suggestions?

  23. sander says:

    Hi, I use your plugin on two sites and I like it very much. Cron is working :-)

    As you can see in this post: http://torrents.neerladen.nl/music-other-benhuman-gohumannotape-2004-hq_ape-pwcsaoriginal-csarar/ I have a problem with very long file names. Ie there anything I can do to let it fit in my theme ? Thanks in advance, Sander

  24. Steve Weintraub says:

    This is a great plugin! I have one problem and one request:

    However, when I run cron and it updates, it ignores my manual setting. Am I doing something wrong?

    • Speaking of cron, is there a way to to display, outside the loop, the timestamp of the cron? I would like to show at the top of my site “Updated 1/2/2005 at 9:00 EST” or words to that effect.
  25. Steve Weintraub says:

    Oops, the markup got munged. I’m calling this:

    thesyndicationsource()

  26. Steve Weintraub says:

    One other thing (sorry!). I am also having the time offset problem. The timestamp on my feed posts are +6hrs, which is my server’s time (UTC). Is there a way to offset this so it matches my timezone?

  27. Kim P says:

    Yes, there is. I’m going to bed now (in Copenhagen), but I’ll be back. This is my feed-blog and it seems to work well:

    http://www.polit-blogs.net/

  28. Kim P says:

    OK, the trick is done in feedwordpress.php , approx. line 2070 and 2071, where you add an offset. (I and the majority of the users live in Denmark, which is GMT+1 and the server is somewhere in USA)

    I replaced

    $post['postdate'] = date(’Y-m-d H:i:s’, $post['epoch']['issued']); $post['postmodified'] = date(’Y-m-d H:i:s’, $post['epoch']['modified']);

    with

    $post['postdate'] = date(’Y-m-d H:i:s’, $post['epoch']['issued']+66060); $post['postmodified'] = date(’Y-m-d H:i:s’, $post['epoch']['modified']+66060);

    Not being a php-programmer, it took me a while..

    Next version could have define-statement with SERVER_OFFSET set to 0 , and the lines:

    $post['postdate'] = date(’Y-m-d H:i:s’, $post['epoch']['issued']+SERVEROFFSET); $post['postmodified'] = date(’Y-m-d H:i:s’, $post['epoch']['modified']+SERVEROFFSET);

    Then it should be easy to make the adjustments.

    Hope it works..

  29. Kim P says:

    it should be “66060″ all the way, and likewise “_” between “SERVER” AND “OFFSET”

  30. Kim P says:

    Well, it is hard to write messages in this place, I mean: 6 times 60 times 60 aka 6×60x60 with the x’s replaced with *’s

  31. Steve Weintraub says:

    Kim, thanks for hack!

  32. Scasquiov says:

    Absolutely great plugin!

    I’ve been doing some hacking around and finnaly got it working with Wordpress 2.0 RC1. I would like to suggest a change to the code though: Users are currently identified by their name which means if two users, from two different feeds, happen to have the same username they will be taken for the same user when aggregated into wordpress. My suggestion would be to compose the username created by FWP for each user with the author’s name and author’s url, so that they would look something like this:

    jhondoe.somedomain.com/weblog

    For a user who’s original username is “jhondoe” and who’s weblog URL is actually htp://somedomain.com/weblog

    I’m not sure if I’m missing something though, it’s quite possible this is just silly :)

    any toughts?

    Cheers

  33. Steve Weintraub says:

    I’m having a new problem with the plugin..it seems to be not updating all the feeds it used to..it seems to randomly not update them, even when I manually hit update-feeds.php

  34. Scasquiov says:

    Steve, what happens if you schedule the “Next update” for “ASAP” before hitting update-feeds.php?

  35. Steve Weintraub says:

    There’s definitely a problem..when I do the manual update, it lists three or four sites only, and I know that lots more sites in my list have udpated feeds. It’s as if update-feeds.php times out or something. If update each one manually, it works..update All is where it hangs up.

  36. IO ERROR says:

    Yeah, I definitely need WP 2.0 support. Any ideas when this might happen?

  37. Ben says:

    When there are pictures in my feeds, is it possible to copy those pictures to my server so they can be displayed on my site? As of now, images are just hotlinked.

    Thanks!

  38. Usabilist says:

    Hi Charles,

    your WordPress PlugIn for the feed syndication seems to be something I was looking for a long time! Currently I’m trying to make it work but I have troubles with an automatic update via RPC.

    I have 2 original blogs and 1 summary, where the FeedWordPress is installed. I have added a link to XMLRPC.php of the summary blog to the list of notified services in original blogs but when I post a new record it doesn’t appear in summary blog.

    Is there any way to see what happens on RPC and why the summary blog is not being updated? Or are there some Hosting-issues that prevent this from happening?

  39. xen says:

    Outstanding plugin! I’ve been looking for something like this for a while. Great work!

    One question: Is there a way to enclosures included in the syndicated feeds? Specifically I’m interested in syndicating podcasts. I’m getting text on the syndicated feeds but not the enclosures.

    Thanks again for the great plugin.

  40. Scasquiov says:

    Steve,

    I am having the same problem you were. I think it might have to do with the version of PHP you’re using. The only reference I found to this issue was this one: http://minutillo.com/steve/weblog/2004/06/08/fsockopen-and-php-4-3-4

    It isn’t very helpfull but I will try to upgrade the version of PHP I’m using (4.3.4) to the latest one (4.4.1) and see how it goes. If it solves the problem… good enough to me :)

  41. mike says:

    FeedWordPress work’s great when I use it on my computer localy through apache and ect.. But when I load it on online and try to add a feed through links/syndicated it tells me “no feed found”. Do you know what the problem is?

  42. Scasquiov says:

    Updated PHP, but no luck with that. I traced the problem to the file wp-includes/class-snoopy.php (snoopy is a http client in PHP), the failing function is actually fsockopen but no error is being returned. I think the cause to this is the script timing out before fsockopen has a chance to. I’ve just added the following line before the invocation to fsockopen so that the script’s timeout is extended beyond fsockopen’s timeout:

    settimelimit($this->fptimeout + 5);

    Seems to be working alright now. It appears to be a snoopy bug to me.

    HTH! Scasquiov

  43. Scasquiov says:

    Also, an alternative, if you don’t want to change class-snoopy.php is to add the following line as the first one in feed2wp() function (you can find it in feedwordpress.php):

    settimelimit(35);

  44. Scasquiov says:

    Yet another issue: the feeds I’m aggregating frequently have images, that is not a problem if we are talking about external images (regarding to the feed’s site). However, when we are talking about relative paths (ie, images in the same site as de feed) the images URL’s may be relative and in such cases they aren’t being correctly resolved.

    Anyone else having this problem? Any thoughts?

    Perhaps it has to do with the resolverelativeuri() function in feedwordpress.php, but from what I can find out this function is only being used for anchor tags.

  45. Scasquiov says:

    Rad,

    Is this normal? am I doing something wrong?

    Thanks in advance, Scasquiov

  46. abstrakONE says:

    I too am looking for Wordpress 2.0 support.

  47. [...] icio.us bookmarks as asides in your blog in under 3 minutes? Use K2 as your theme, install FeedWordPress [...]

  48. Ronald says:

    Got FeedWordPress working on a Wordpress 2.0 blog relatively easily after I deleted SWL calls to first_name. Still get some SQL errors but nothing that gets in the way of syndication.

    err… and I just noticed the trackback from post where I explain the way I am using Feedwordpress in my blog

  49. achedy says:

    Thank for your project. But I have problem.

    If I input RSS from multiply, URL The article can’t inset into DB.

    RSS in multiply not make http://bla..bla..

    but make

    http://bla..bla..

    can’t you give me information about it ?

    Thank’s

  50. john says:

    I had .97 working with WordPress 2.0 with no modifications for about 24 hours, but now I’m getting this error:

    WordPress database error: [You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near 'ORDER BY linkname' at line 1] SELECT * FROM newsfeedlinks WHERE linkvisible = ‘Y’ AND linkcategory = ORDER BY link_name

  51. Scasquiov says:

    It was pretty hard to find it, but I think I finnaly understood what is going on wrong with the relative paths I’m getting in some images.

    Seems to me that the regular expressions that are extracting attribute values from each tag (ie, anchors and images) so that relative paths are translated to absolute paths aren’t quite working as intended. The regular expressions i’m talking about are the ones in the itemtopost() function (in feedwordpress.php). They are taking into account that each tag’s attribute values are delimited by quotation marks but fail when, in fact, attribute values are delimited by apostrofes.

    For example, where this expression appears:

    “:(]$attr=\”)([^\">])(\”[^>]*>):i”

    should actually be used: “:(]$attr=[\"|'])([^\"^'>])([\"|'][^>]*>):i”

    This seems to solve it, but my regular expressions are a bit rusty, please clarify if I am doing something wrong.

    Anyone ele having the symptoms I described previously? I’d love to hear about other possible ways to solve this.

    Cheers, Scasquiov

  52. [...] even made a point of mentioning that I did not like it. Then I got distracted playing with FeedWordPress [...]

  53. Ovidiu says:

    I’ve deactivated the updates on a community site since migrating to WP2. Wordpress 2.0 support would be quite welcome for me too. ;) Happy new year!

  54. satanuke says:

    Hi Rad Geek, first I would like to say this is a great plugin you have got here. I also had some problems with the cron-jobs on my hosts so I had to use my own computer to update the feeds using curl for win32. I was using that option until now but I have implemented a new way, which is updating the feeds every-time the page is loaded, I know this can be bad because the page will take more time to load but it works really good. What I did was adding PHP code on the template that uses the php curl extension to run the update-feeds.php script. It is something like this :

    :@www.mysite.com/blog/wp-content/update-feeds.php”); curlsetopt($ch, CURLOPTPOSTFIELDS, “update=quiet”); curlexec($ch); curl_close($ch); ?>

    Of course, you should change the domain and login details to match your configuration.

    And of course, the host must have the php curl library enabled.

  55. satanuke says:

    The above code is not correct, anyway, you can check it at my blog – http://www.hugosoft.net/web/archives/825

  56. Marc says:

    I have blogs a, b and c. Blog a uses feed wordpress to aggregate posts from blogs b and c. I have the “Allow comments” radio button selected. I have the permalinks pointing to the original website. When a post gets a comment on either blogs b or c, the same post as it appears on blog a shows no comments. Is there a way to fix this? I notice one of the keys added to the post is the comment feed for the post, so I’m sure the data is there. I would guess this would be a template mod, but I’m not really sure where to start.

    Gosh….I hope this makes sense…

  57. News says:

    Hi Rad Geek

    Quick question, I have selected a RSS feed and the sample copy looks fine however when I go to update my feeds it doesn;t import any.

    Could it be to do with the Encoding. The Encoding displayed when I select ‘Swicth links’ is showing as UTF-8, however the actual encoding for the feed is ISO-8859-1

    Not sure if you can replicate the issue with this feed:

    http://www.mobileread.com/feeds/full_rss20.xml

    It may be (and most probably is) just me.

    Thanks for a great script. For most of the other feeds it works great. Just a couple of awkward ones :)

  58. The Big Deal says:

    Any work being done to support Wordpress 2.0 now that it has been released?

  59. Tomas France says:

    I’ve hacked FWP to work with WP2 and also made another minor hack.

    The file is at http://key2marketing.net/php/feedwordpress.php.txt

    NOTE: I am a bad coder so don’t expect much, but it seems to be working.

    Tomas

  60. Di says:

    Hi there,

    I upgraded to WP 2.0 and upgraded/reinstalled the feed. It worked fine prior to the upgrade but now when I manually update I get the following: WordPress database error: [Unknown column 'userfirstname' in 'where clause'] SELECT ID from wpusers WHERE TRIM(LCASE(userlogin)) = TRIM(LCASE(’sparklegrrl@livejournal.com’)) OR TRIM(LCASE(userfirstname)) = TRIM(LCASE(’sparklegrrl@livejournal.com’)) OR TRIM(LCASE(usernickname)) = TRIM(LCASE(’sparklegrrl@livejournal.com’)) OR TRIM(LCASE(usernicename)) = TRIM(LCASE(’sparklegrrllivejournalcom’)) OR TRIM(LCASE(userdescription)) = TRIM(LCASE(’sparklegrrl@livejournal.com’)) OR ( LOWER(userdescription) RLIKE CONCAT( ‘(^|\n)a.k.a.( |\t):?( |\t)‘, LCASE(’sparklegrrl@livejournal\.com’), ‘( |\t|\r)*(\n|$)’ ) )

    WordPress database error: [Unknown column 'userfirstname' in 'where clause'] SELECT ID from wpusers WHERE TRIM(LCASE(userlogin)) = TRIM(LCASE(’sparklegrrl@livejournal.com’)) OR TRIM(LCASE(userfirstname)) = TRIM(LCASE(’sparklegrrl@livejournal.com’)) OR TRIM(LCASE(usernickname)) = TRIM(LCASE(’sparklegrrl@livejournal.com’)) OR TRIM(LCASE(usernicename)) = TRIM(LCASE(’sparklegrrllivejournalcom’)) OR TRIM(LCASE(userdescription)) = TRIM(LCASE(’sparklegrrl@livejournal.com’)) OR ( LOWER(userdescription) RLIKE CONCAT( ‘(^|\n)a.k.a.( |\t):?( |\t)‘, LCASE(’sparklegrrl@livejournal\.com’), ‘( |\t|\r)*(\n|$)’ ) )

    Also for some reason my crontab seems to have stopped working. Can anyone help?

  61. Seems FeedWordPress support has fallen off since WP 2 ;) — maybe some of you guys who have gotten it successfully working could outline exactly how you’re using it? Are you using the XMLRPC stuff or just by cron? I’ve hacked a small part of the file where it looks at user_levels instead of roles/capabilities but I’m thinking the plugin needs a complete overhaul now and I’m not quite sure where to start…

  62. Aaron says:

    Tomas– You’ll have to comb that code and sort through every instance of $userlevel. Rad Geek has globalized numerous times throught the code, tested for $userlevel, etc. Granted, $user_level has been legacied but for how long?

  63. Kiersten says:

    Hi, I’d like to try using this, but what I want to do is set up a separate page on my website, using wordpress, which would be a feed from several different sources. Is there a way to do that with this plug-in? Thanks!

  64. LordRich says:

    I’ve installed Thomas France’s modified version, and can confirm it is working – just about. There are a few bugs in it, but generally it seems to cope as well as the official version did with WordPress 1.5. I’m syndicating using the cron job method (with an already modified update-feeds.php).

    Kierston – If you’re not already using WordPress then you’ll have to design yourself a template which looks like the rest of your website. If you are already using WordPress and want a seperate page with just syndicated posts then the simplest way is to install a seperate version of WordPress.

  65. Jimmer says:

    Were can I find this version by Thomas Frances?

  66. Jimmer says:

    I didn’t look close enough

  67. Very very exciting plugin. Thanks to Charles Johnson for the original plugin and to Thomas France for the adapations to Wordpress 2.0.

  68. KSvensson says:

    hello there! does this plug support rssfeeds with foreign characters? i want support for swedish feeds and characters like Å,Ä,Ö.

  69. KSvensson says:

    ok i now use this croncommand: /usr/bin/curl http://allvetaren.se/wp-content/update-feeds.php -d update=quiet -d log=username -d pwd=password

    and has emailsendings to me wich shows this:

    % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed

    0 0 0 0 0 0 0 0 –:–:– 0:00:01 –:–:– 0 0 0 0 0 0 0 0 0 –:–:– 0:00:02 –:–:– 0 0 0 0 0 0 0 0 0 –:–:– 0:00:03 –:–:– 0 0 0 0 0 0 0 0 0 –:–:– 0:00:04 –:–:– 0 0 0 0 0 0 0 0 0 –:–:– 0:00:04 –:–:– 0 0 0 0 0 0 0 0 0 –:–:– 0:00:04 –:–:– 0

    what does this mean?? is it a way to show when a feed has been transfered or nor?

  70. KSvensson: you may want to play with the options on CURL to quieten it down. I’m using “-sS”, which tells it not to output progress information (what you’re currently receiving), but to still output any errors if they occur.

  71. Greg says:

    Hi,

    Under options -> Syndication, I have the Permalinks point to: option set to “this website”.

    This is what I want. However, in the body of the post after the rss content is displayed, I want something that says “Click here to read the full story”, with a link that will open a new window to the corresponding post.

    How and where do I modify the code to make this happen?

    Thanks in advance!

  72. KSvensson says:

    Simon: Thanx, now i dont get any emailreposrt,is that equal to a working rssfeed? i am unsure if the plugin updates my blog automatic or just when i visit the blog (if i look at the postings date and timestamp its older then actual time when i visit but thats just because timestamp is equal to the news own posting on the real site that i am receiving my feed from right?) shit my english isnt that good hope you understand ;(

    Another question; the new posts doesnt seem to be included in the categorys “number of posts in each category” (look at http://www.allvetaren.se )

  73. KSvensson says:

    yes my new croncommand in cpanel is now: /usr/bin/curl http://allvetaren.se/wp-content/update-feeds.php -sS -d update=quiet -d log=xxx -d pwd=xxx

    Simon is that what you meant?

  74. KSvensson says:

    hello!

    is there a way to format the rssfeeds (fontsize, color, how much text to show in post etc)?

  75. Brian Pratt says:

    Hi

    Great plugin – I had it working well under 1.5 but now after 2.0 I have problem I don’t know how to solve.

    Have sucessfully installed the plugin and selected a feed. My issue is with update-feeds.php

    When I select the page with firefox I get a “document has moved here message” then when I run the file a 404 message.

    When I run this in ie I get a to the php file ok but again get a 404 error when I try to update the feeds.

    Can anyone provide some advice to help me track the problem down ?

    Thanks in advance.

  76. KSvensson says:

    hmm get feeds but the mailmesssage shows this some times ” curl: (52) Empty reply from server “

    is that when no new updates are on feeds?

  77. Stephen says:

    I can’t find Thomas France’s update, but I did find some updated code over at the Wordpress foum:

    http://wordpress.org/support/topic/56808

    It really bugs me when people do not post the sources for updates when they are talking about them. Please post the source for this Thomas France update.

    I still have a problem that when I run the update-feeds.php it always says:

    “0 new posts were syndicated and 0 existing posts were updated”

    I have several feeds listed in the syndication section on the links page but it never seems to post any content from them. Maybe I am missing something here, can anyone help?

  78. Stephen says:

    I am getting this error from the Cron Job:

    Fatal error: Class ‘FeedWordPress’ not found in /backup/home/monkeyn/public_html/techness/wp-content/update-feeds.php on line 151

    I am using the standard Cron settings found in the help, of course changed to my path settings. Any ideas?

  79. Steve Garratt says:

    Version 0.97 makes posts that cause my rss feed to become “Not well-formed”. This appears to happen with feeds that use GET arguments in the link. Examination of the source feed shows that the offending links are enclosed in sections but feedwordpress strips out the CDATA information. XML readers then fail because they think the link is not well formed. The output of my feed viewed in Firefox is below. I would very much like to get this problem solved because this is a great script otherwise.

    XML Parsing Error: not well-formed Location: http://how-to-reduce-cholesterol.magicblur.com/feed/ Line Number 33, Column 117: http://www.cite-sciences.fr/francais/alacite/scienceactualites/sitesactu/fsbreves2.php?langue=an&idbreve=1274 ——————————————————————————————————————–^

  80. Steve Garratt says:

    In my last post I typed the syntax of the CDATA section but of course it dissappeared in the post. It also truncated the offending link. I’m attempting to show it better below.

    Version 0.97 makes posts that cause my rss feed to become “Not well-formed”. This appears to happen with feeds that use GET arguments in the link. Examination of the source feed shows that the offending links are enclosed in CDATA sections but feedwordpress strips out the CDATA information. XML readers then fail because they think the link is not well formed. The output of my feed viewed in Firefox is below. I would very much like to get this problem solved because this is a great script otherwise.

    XML Parsing Error: not well-formed Location: http://how-to-reduce-cholesterol.magicblur.com/feed/ Line Number 33, Column 117: {link}http://www.cite-sciences.fr/francais/alacite/scienceactualites/sitesactu/fsbreves2.php?langue=an&idbreve=1274{/link} ——————————————————————————————————————–^

  81. Tomas France says:

    Stephen,

    The “hacked version” is at http://key2marketing.net/php/feedwordpress.php.txt .

    Tomas

  82. Rod says:

    WordPress database error: [Unknown column 'userfirstname' in 'where clause'] SELECT ID from wpusers WHERE TRIM(LCASE(userlogin)) = TRIM(LCASE(’Mortgage News Daily – Mortgage and Real Estate News’)) OR TRIM(LCASE(userfirstname)) = TRIM(LCASE(’Mortgage News Daily – Mortgage and Real Estate News’)) OR TRIM(LCASE(usernickname)) = TRIM(LCASE(’Mortgage News Daily – Mortgage and Real Estate News’)) OR TRIM(LCASE(usernicename)) = TRIM(LCASE(’mortgage-news-daily-mortgage-and-real-estate-news’)) OR TRIM(LCASE(userdescription)) = TRIM(LCASE(’Mortgage News Daily – Mortgage and Real Estate News’)) OR ( LOWER(userdescription) RLIKE CONCAT( ‘(^|\n)a.k.a.( |\t):?( |\t)‘, LCASE(’Mortgage News Daily – Mortgage and Real Estate News’), ‘( |\t|\r)*(\n|$)’ ) )

    WordPress database error: [Unknown column 'userfirstname' in 'field list'] INSERT INTO wpusers SET ID=’0′, userlogin=’Mortgage News Daily – Mortgage and Real Estate News’, userfirstname=’Mortgage News Daily – Mortgage and Real Estate News’, usernickname=’Mortgage News Daily – Mortgage and Real Estate News’, usernicename=’mortgage-news-daily-mortgage-and-real-estate-news’, userdescription=’Mortgage News Daily – Mortgage and Real Estate News’, useremail=”, user_url=’http://www.MortgageNewsDaily.com/’

  83. Rod says:

    Appologies let me complete that last post.

    Looking for some assistance with these errors formed when running update-feeds.php. WordPress database error: [Unknown column 'user_firstname' in 'where clause']

    WordPress database error: [Unknown column 'user_firstname' in 'field list']

    More detail in prior post. Help much appreciated.

  84. Gil says:

    Any idea how I could truncate the displayed post to x characters? I’m receiving full length posts using feedwordpress.

    Anyone have an idea?

    Tried evermore, post-teaser, etc, and they don’t seem to be compatible with feedwordpress.

    Thanks,

  85. Brian Pratt says:

    Help I need some grown-up support.

    See previous post. I have updated WP to 2.01 and also installed it on another domain with a different host.

    Installed the marked up feedwordpress on both and also the update-feeds file which is standard.

    Both installations give exactly the same error.

    Feed wordpress plugin appears to be working fine. It sees a feed and downloads its details no problem.

    Update feeds is giving the same problem on both installations.

    When I run the script it loads fine and sees the feed. But when I ask it to update the feed I get a 404 error.

    Have been trying to crack this nut for 2 weeks now and have run out of ideas.

    Will gladly pay someone to look at my site to sort it out – Any takers ?

    Thanks in advance Brian

  86. Phillip A Smith says:

    I’ve applied Tomas France’s hack, but now I have to update all the feeds manually… anyone else having this issue?

    Phillip.

  87. Gil says:

    Hi Phillip,

    I didn’t use Thomas France’s hack. I used this new code someone wrote and replaced the old one, and it worked.

    Link – http://paste.uni.cc/8492

    Anyone out there know how to truncate the posts that are displayed? Still trying to figure it out.

  88. indi says:

    the ‘update all’ simply doesn’t work for some feeds, they have to be updated manually.

    is it possible to turn the staggered delay off so that it actually will update all the feeds?

  89. bullair says:

    Feedwordpress is not pulling from subdomain on the same site.

    We have two installs of wordpress, one on a subdomain and one on the main domain. We want to feed the main domain install, but it won’t work.

    We need to pull from subdomain blog at http://subdomain.domain.com to http://domain.com

    Feedwordpress works fine pulling the same feeds to other domains.

    Any know issues or reasons?

  90. Mashiyoshi says:

    This has been asked numerous times without a response, so I’ll try again:

    How do you limit the length of each post to display x number of characters? Right now, I’m receiving full length articles. I just want to display a short summary.

    I’d be very greatful if anyone here can present a workable solution.

  91. John says:

    First off I have to say I love your plugin and my blog cant live with out it.

    I recentu upgraded to Wordpress MU and although I have the plugin working under WP2.0 I now have a BIGGGG issue with WPMU.

    The user database is formatted wpBLOG NUMBERtable name

    I am not a php coder by any imagination and hack away at the best of times.

    If you could point me in the direction to make the mod I would appreciate it.

    PS. FeedWordPress shows on the nav bar in WP2.0 but i dont see the option in WPMU, any help you can offer me will be greatly appreciated.

    Thanks for a great plugin.

  92. Great plugin. Thanks. I would like to aggregate some things without dates: images from yahoo, abstracts, but the seem to get a new date every time the updated, that upsets the order of the posts. I though a solution might be to simply turn off updating, so that the time for each post with no date information will just be when it was loaded, and then that does not change. New post will come in eventually creating the right order. Is it possible to have an option to turn off updating, or what line of code would I change to do that? Thanks

  93. al says:

    Hello I had all ready used this very nice plugin before (WP1.5) and it worked like a charm (nice job). I just made a new WP installation (on another domain at the same hosting company, using php4.3.10, FWP 0.98 and WP2.02). When adding a new feed I get the message “no feed found” (the feed validates fine), I don’t know what is causing this. I found on the WP support forum somebody with the same problem and he resolved it by changing host.I wonder what is causing this problem and how it can be fixed (ie:chmod a file… ). Any idea somebody?