<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>Snipplr</title>
    <description>Recent snippets posted on Snipplr.com</description>
    <link>https://snipplr.com/</link>
    <lastBuildDate>Tue, 09 Jun 2026 21:31:49 +0000</lastBuildDate>
    <item>
      <title>(PHP) Display the First Image Attachment of a WordPress Post - trey</title>
      <link>https://snipplr.com/view/12513/display-the-first-image-attachment-of-a-wordpress-post</link>
      <description>&lt;p&gt;&lt;/p&gt;</description>
      <pubDate>Mon, 23 Feb 2009 15:15:56 UTC</pubDate>
      <guid>https://snipplr.com/view/12513/display-the-first-image-attachment-of-a-wordpress-post</guid>
    </item>
    <item>
      <title>(PHP) PHP Include Path - trey</title>
      <link>https://snipplr.com/view/7313/php-include-path</link>
      <description>&lt;p&gt;If you're using includes that sit in different relative locations to the files your including *into*, you normally end up with stuff like `include("../../header.php")` in one place and `include("../../../header.php")` in another.  This is a bit easier, but be sure to include a leading `/`, because depending on your sever configuration, it may or may not add one for you.  It's better to have 2 `/`s than none.&lt;/p&gt;</description>
      <pubDate>Tue, 15 Jul 2008 17:50:32 UTC</pubDate>
      <guid>https://snipplr.com/view/7313/php-include-path</guid>
    </item>
  </channel>
</rss>
