Forum Replies Created

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter levitymn

    (@levitymn)

    I can see how pages can increase the rule set since they do not use dates in the generation of their perma links. Having said that, it is not pertinent to categorizing pages. This post is about the ability to categorize pages not the poor performance lots of pages will induce in a worpress install.

    I want to be able to categorize a reasonable number of pages with good parent <-> child relationships (which should improve page performance), in the tens of pages. the act of using categories with pages does not induce the performance issues of pages, the very nature of pages does. Turning this conversation into a discussion around the poor performance of many pages is a derailment of the topic. Let us set that aside.

    I can see how custom post types could be beneficial in many places that one would use categorized pages, however I do not have the time to write custom post type code for every site I manage where I need solid categorization of content. Custom content types are a developer solution not a user solution and far more time consuming than categorizing and spilling links to categorized content.

    to end the thread about many pages causing performance issues let me state one more time:

    This discussion is about categorizing pages not the performance issues induced by having too many pages.

    Thread Starter levitymn

    (@levitymn)

    Ipstenu,

    Actually I did read the WHOLE post, multiple times and again after your reply. Even the section about “Pages” specifically mentions going through the rewrite rules one at a time. The act of categorizing something does not affect the rewrite rules, unless you have put %category% in your permalink structure settings.

    You are right Otto does indeed know what he is talking about and he is talking about permalinks and rewrite rules in that post with respect to how starting a permalink with an string type variable like %category% is bad, not about categorizing WordPress Pages.

    Thread Starter levitymn

    (@levitymn)

    Ipstenu,

    That issues is referring to using %category% in the generation of permalinks. I think in this article the term “page” is not referring to the WordPress Page type but instead content referred to by a URL. Really the post you reference has nothing to do with categorization but with using a string (instead of a number) for the first part of your permalink structure.

    I am not suggesting using category for any part of the permalink structure for pages. I am looking to just be able to associate categories to pages so I can generate categorized lists of content.

    Thread Starter levitymn

    (@levitymn)

    Ipstenu,

    I do not follow your logic. Usually in a blog you have hundreds of blog posts and few pages. Even in a site with a relatively large number of pages there are usually fewer pages than posts. I don’t see how categories on pages would prove more taxing to the system that categories on posts.

    Even if there were thousands of pages and thousands of pages I just cannot see how maintaining and using category <-> type <-> contentID relationships can be that taxing to the system.

    Thread Starter levitymn

    (@levitymn)

    Esmi, for instance on an interior designer’s site the pages are children of the projects page, and when there is enough content the projects page may have sub groping pages by type of projects. But because this client works in many cities and states it would be helpful for prospective clients in different regions to have the same content spilled by state. I would also like to spill project pages by thematic elements as well. So I could get one of the groupings using page parent <-> child relationships I cannot expose the pages in the number of ways I want.

Viewing 5 replies - 1 through 5 (of 5 total)