Capacity for a large number of pages using %postname%

  • jjbbrr

    (@jjbbrr)


    13 years, 9 months ago

    Hi, I’ve used WordPress as a content management system for small sites (not blogs) and it works extremely well. I just use pages with urls: %postname%.

    I’d love to use it for larger sites too but it sounds like there will be problems once the number of pages increases if using %postname% for urls, which is what I prefer to do (see http://wordpress.org/support/topic/420032).

    If this was fixed it seems to me that WordPress would be totally awesome as a cms so I would like to suggest this as a feature.

    What do you think?

Viewing 2 replies - 1 through 2 (of 2 total)
  • Moderator James Huff

    (@macmanx)

    Volunteer Moderator

    13 years, 9 months ago

    Per the thread you linked to, there is a fix in the pipeline, but an estimate at this point is unlikely.

    I recommend using /%year%/%postname%/ for now. If you decide to change it to /%postname%/ when the fix makes it way into the core, WordPress will take care of all the permanent redirects.

    Or, do the exact opposite. Start with /%postname%/ and change it to /%year%/%postname%/ if you start to notice too much lag. WordPress will again take care of all the permanent redirects.

    mrmist

    (@mrmist)

    13 years, 9 months ago

    Now that I re-read the trac ticket I’m not certain that it is designed to fix this particular issue, but I guess any major change to the way URLs are handled would have an impact. Given it’s set to future release, though, it’s not going to turn up any time soon unless someone writes the (presumably large and complex) patch.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Capacity for a large number of pages using %postname%’ is closed to new replies.