• Newbie here. May be trying to run before I walk, but I’d rather start things off right.

    I’m trying to convert my choir’s hand-coded website to WordPress. It seems to me that concerts and repertoire will be posts, and everything else will be pages.

    Let’s take a concert on 15th July 2012, which I add today and will update at various times until just after the concert date. A slug of 20120715 works best for me, because we quite often make the booking before we know the concert title and we may also have a few concerts with the same title. The problem comes with how I structure the permalink:

    • a url like …/2011/20120715 would be misleading;
    • as far as I can see, a url like …/2012/20120715 (or …/2012/0715) would mean re-dating the post – which is fine, except that it then wouldn’t appear until the day of the concert which is a bit useless for publicity
    • a url like …/concerts/20120715 works for me, but the codex says “it is nota good idea to start your permalink structure with the category, tag, author, or postname fields”.

    I suspect that for a site this size the performance hit from starting with the category field won’t be a major issue, but I’d welcome comments on that.

Viewing 2 replies - 1 through 2 (of 2 total)
  • This may not be such as issue in WordPress 3.3 but, in the meantime, why not use a structure like /%post_id%/%postname%?

    Thread Starter HenryLeeds

    (@henryleeds)

    Thanks esmi, but nobody’s ever going to be able to guess the post_id and I’d prefer a url to be predictable.

    I see 3.3 is expected in November. Given the time it’s going to take me to move content across and make it play nicely then tinker with a child theme, I doubt I’ll be publishing before than. So maybe I’ll gamble on /%category%/ and a hand-edited slug.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Advice on structure, please: permalinks and slugs’ is closed to new replies.