[Valid RSS] This is a valid RSS feed.


This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.


  1. <?xml version="1.0" encoding="utf-8" ?>
  2. <rss version="2.0">
  3. <channel>
  4. <title>FlatPress</title>
  5. <link></link>
  6. <description><![CDATA[]]></description>
  7. <copyright>Copyright 2006, NoWhereMan</copyright>
  8. <managingEditor>[email protected]</managingEditor>
  9. <language>en-us</language>
  11. <generator>FlatPress</generator>
  12. <item>
  13. <title>FlatPress 1.0.3</title>
  14. <link></link>
  15. <description><![CDATA[ <p>Hi guys! New FlatPress release!</p>
  16. <p>This release fixes an XSS (<a href="">CVE-2014-100036</a>). </p>
  18. <p>Bonus: a new style for Leggero theme by <a href="" class="user-mention">@MarcThibeault</a> and other UI enhancements by <a href="" class="user-mention">@MarcThibeault</a> and <a href="" class="user-mention">@liquibyte</a> </p><p>Have fun!</p>
  19. ]]></description>
  20. <category>News, Announcements </category> <guid isPermaLink="true"></guid>
  22. <author>NoWhereMan [email protected]</author>
  23. <pubDate>Fri, 12 Jun 2015 03:36:44 -0400</pubDate>
  24. <comments></comments>
  25. </item>
  26. <item>
  27. <title>Security Advisory: Exploit in SEO Metatag Info Plugin</title>
  28. <link></link>
  29. <description><![CDATA[ <p>In case you are using this plugin, make sure to replace it. Thanks to fellow FlatPress user Igor Kromin for letting us know!</p>
  30. <p>Igor also walks through an alternative way to to define seo metatags  <a href="">on his blog</a>. It is not really necessary to edit FlatPress core files for that, though. You may actually want to use a Smarty filter :)</p>
  31. <p>bye
  32. </p>
  33. ]]></description>
  34. <category>News </category> <guid isPermaLink="true"></guid>
  36. <author>NoWhereMan [email protected]</author>
  37. <pubDate>Fri, 05 Jun 2015 03:28:25 -0400</pubDate>
  38. <comments></comments>
  39. </item>
  40. <item>
  41. <title>Bug Fix release 1.0.2</title>
  42. <link></link>
  43. <description><![CDATA[ <p>Yay, two point-releases in less than two weeks. This addresses the rushed patch of v1.0.1. As a bonus, fixes some strict standard notices. You are probably going to get still some, but feel free to fork and issue a pull request to fix the others!
  44. </p>
  45. ]]></description>
  46. <category>Announcements </category> <guid isPermaLink="true"></guid>
  48. <author>NoWhereMan [email protected]</author>
  49. <pubDate>Thu, 28 Nov 2013 14:52:08 -0500</pubDate>
  50. <comments></comments>
  51. </item>
  52. <item>
  53. <title>Bug Fix release 1.0.1</title>
  54. <link></link>
  55. <description><![CDATA[ <p>Download it from our new home on <a href="">GitHub</a>.
  56. </p>
  57. ]]></description>
  58. <guid isPermaLink="true"></guid>
  60. <author>NoWhereMan [email protected]</author>
  61. <pubDate>Thu, 21 Nov 2013 04:15:38 -0500</pubDate>
  62. <comments></comments>
  63. </item>
  64. <item>
  65. <title>FlatPress is now on GitHub</title>
  66. <link></link>
  67. <description><![CDATA[ <div style="text-align:center"><br />
  68. <img src="" alt="flatpress-hearts-github.png" title="flatpress-hearts-github.png"  width="300" height="225" /><br />
  69. </div><p>I am very proud to announce that FlatPress repositories are now hosted on GitHub.</p>
  70. <ul>
  71. <li><a href="">FlatPress main repository</a>
  72. </li>
  73. <li><a href="">FlatPress extras</a>
  74. </li>
  75. </ul>
  76. <p>Now you can freely enjoy FlatPress in all of its true open source goodness! :)
  77. </p>
  78. ]]></description>
  79. <category>News, Announcements </category> <guid isPermaLink="true"></guid>
  81. <author>NoWhereMan [email protected]</author>
  82. <pubDate>Mon, 16 Sep 2013 04:16:30 -0400</pubDate>
  83. <comments></comments>
  84. </item>
  85. </channel>
  86. </rss>

If you would like to create a banner that links to this page (i.e. this validation result), do the following:

  1. Download the "valid RSS" banner.

  2. Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)

  3. Add this HTML to your page (change the image src attribute if necessary):

If you would like to create a text link instead, here is the URL you can use:

Copyright © 2002-9 Sam Ruby, Mark Pilgrim, Joseph Walton, and Phil Ringnalda