14 Responses

1. Principe » Eccolo là

   May 11th, 2005 at 7:39 am

   1

   [...] che è stato scoperto un possibile buco nei feed nell’ultima versione di WordPress. [...]

2. Matt

   May 11th, 2005 at 8:20 am

   2

   Instructions in French were posted this morning here.

3. Tom Markiewicz » Potential issues in new WordPress version

   May 11th, 2005 at 8:31 am

   3

   [...] l issues in new WordPress version There looks to be a few minor issues cropping up with the new version of WordPress. I&#8 [...]

4. neuro

   May 11th, 2005 at 8:45 am

   4

   There’s a thread about it on the wordpress support forum.
   Posting a new entry or updating an old posts corrects the problem.

5. neuro

   May 11th, 2005 at 8:46 am

   5

   oh I misread, you already said it

6. marlyse.com » Possible WordPress1.5.1 RSS Errors

   May 11th, 2005 at 8:48 am

   6

   [...] f null. You can patch the source file by following these instructions.” — (Via Possible WordPress1.5.1 RSS Errors : Blogging Pro - Blo [...]

7. » About WordPress 1.5.1 - jonabad.com

   May 11th, 2005 at 10:49 am

   7

   [...] bug fix from the RSS department and so we have another problem on our hands as reported by BloggingPro and in the support forums. As always there are solut [...]

8. Mangas Verdes » WordPress 1.5.1, liberado y con errores

   May 11th, 2005 at 11:53 am

   8

   [...] ngs. De entre los errores que se van detectando en esta nueva versión, destaca un defecto en la generación de los feeds RSS que provoca un error 304. El f [...]

9. MacManX

   May 11th, 2005 at 8:57 pm

   9

   There is another patch, which claims to be “a better fix,” here: http://mosquito.wordpress.org/view.php?id=1323

   “When passed an empty string, strtotime() is returning a timestamp for midnight on the current day rather than treating it as an invalid date and returning -1 or 0 as I would have thought. That’s pretty annoying, but it is documented on the GNU page pointed to from the PHP docs. It would have been nice if the PHP docs directly documented it, though.

   Okay, so that’s the crux of the problem. Knowing that, we can write a better fix. We might just want to forego attempts to write the logic ‘elegantly’, and just put a chunk of more verbose logic there that handles the various possibilities in a more transparent fashion.”

10. Chetan’s monologue » Broken feeds in WordPress 1.5.1 and a fix

    May 12th, 2005 at 12:01 am

    10

    [...]
    A casualty for upgrading too quickly. A minor text edit should solve the problem. I got a 500 error when [...]

11. Dr Dave

    May 12th, 2005 at 12:46 am

    11

    WordPress 1.5.1 and Spam Karma 2.0

    WordPress 1.5.1 is now officially released. If you are a WordPress user, you really ought to upgrade. This version fixes many of the bugs and shortcomings that were introduced with the botched release of WP 1.5. It takes seconds to upgrade from 1.5 (j…

12. Mind Sharer - For The Marketing Mind » Technical: Solution to Wordpress 1.5.1 RSS errors

    May 13th, 2005 at 8:45 pm

    12

    [...] tion on how to fix this problem. Solution to WP1.5.1 RSS errors - [Fernando Graphicos via Blogging Pro]

    [...]

13. Marketing Loop Blog

    May 15th, 2005 at 4:07 am

    13

    WordPress 1.5.1 RSS Errors, and a Fix

    WordPress 1.5.1 has possible bug in RSS feed. The problem is the feeds are not accurate, and returning with error 304. The /feed page which should reflect the entire install feed is only outputting a feed when a new entry is produced and after what see…

14. Hans Hansen

    May 15th, 2005 at 11:54 am

    14

    Glad I found this as I was just about to upgrade.