Forum Replies Created

Viewing 3 replies - 1 through 3 (of 3 total)
  • Resolved via kludge :).

    We’re going to do this:
    on a 404 we’re going to call a script. If the page pretty-page-url is called it’s going to look in the wp_posts table for a page where the title field is “pretty page url’ (though case insensitive). It will then grab the page id, and with that information it will display index.php?page_id=ID.

    In otherwords, we’re going to do the mapping ourselves. I appreciate there are reasons wordpress does this the way they do – but frankly, it’s wrong. Rationalize however you like, in the end permalinks don’t work for large numbers of pages. It should be seamless, it’s not – it crashes and burns. (and the answer is not ‘modify user behavior 🙂 ).

    Shane, perhaps I’ve misunderstood, but I think that’s just the regular permalink .htaccess structure. And the problem is that works fine for 100 pages, but does not work fine for 1000 pages.

    Mercime, that’s a solution but very manual intensive. I’m looking to do this across a number of sites, some of those sites will have 10K to 50k pages. And I need to automate it, otherwise it becomes unmanageable. We’re already touching these pages way more than we should – it’s hugely labor intensive.

    I was thinking that I might just do this. Write a script that dumps all the pageid’s out to a database, onetime. then write a 404 error script that takes the pretty page address and maps it to the wordpress page id. In otherwords, bypass the wordpress page redirect. I’ve used this on other non-wordpress sites and it works fine. Not sure why wordpress doesn’t do something like this – I’m sure it’s technical – but I’m a bit astonished that a platform as big as this has a feature so widely used, that doesn’t work for more than a couple hundred pages.

    In any event – is there any other solution other than the cludge I’ve suggested?

    Thank you shane! I appreciate the assistance.

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