Cacheing with default ?p=nnnn permalinks?

  • Resolved psybertron

    (@psybertron)


    9 years, 5 months ago

    WP-Super-Cache tells me I need custom permalinks for it to work? I need to try something page rendering performance is very poor for casual read users.

    At https://www.psybertron.org I have 15 years, several thousand posts with many containing links referring to other posts – so I can’t just change my permalink settings without breaking existing links (can I?)

    Is there a cacheing solution I can try that works with the default permalinks?

    (Or am I missing something?)

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

  • I have 15 years, several thousand posts with many containing links referring to other posts – so I can’t just change my permalink settings without breaking existing links (can I?)

    They should still work. I just tested this on a localhost install where I have pretty permalinks enabled. I created a post with this link in it:

    https://127.0.0.1/wp-dev/?p=1725

    and when I publish the post and click on the link, it takes me to

    https://127.0.0.1/wp-dev/2015/07/26/this-is-a-status-update/

    Thread Starter psybertron

    (@psybertron)

    Not sure I understand. At which point in that process are you switching the WP permalink setting? When was the page ?p=1725 itself published?

    May have to try on a test / expendable site.

    The ?p=#### links will automatically redirect to their permalink counterpart however you have that defined.

    Thread Starter psybertron

    (@psybertron)

    I see now, the actual query link remains real whatever form of permalink you choose. (I was thinking terms of changing links). And I’ve experimented on a couple of less massive sites, all seems to work fine.

    Ready to activate WP-Super-Cache on my main site. Thanks.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Cacheing with default ?p=nnnn permalinks?’ is closed to new replies.

Tags