I’m not sure what the purpose of this feature is, but it has something to do with static pages being fed from the database. This is somewhat different from the way EzStatic works, because EzStatic will allow you to include dynamic pages that exist in your file system.
Why EzStatic is better than WordPress 1.3’s built-in static pages:
- Include existing real files as static pages.
- Allows dynamic (PHP, ASP, JSP, etc.) code to be included in the "static" content.
- If the file that EzStatic includes is a full HTML page, EzStatic will insert the <head> area of the page automatically into the WordPress <head> output, including any script.
- When you use EzStatic, you know immediately how to get the page to appear (index.php?static=filename). Static pages in WP 1.3 use post slugs as filename-like identifiers. These can only be known by looking in the database after they are create.
The static page feature might be useful for some folks, but it’s not exactly what I had in mind.
There are a number of ways to get a post not to appear in the post listings in WordPress 1.3. If all you were going to do with static posts was how WordPress 1.3 has implemented them, you might as well have used a regular post and gotten the comment feature thrown in on your static page for free.
Can someone explain how the Pages feature of 1.3 is useful for you?
