WordPress.org

Ready to get started?Download WordPress

Forums

W3 Total Cache
[resolved] CDN Origin setting doesn't modify permalinks (8 posts)

  1. Hubert Nguyen
    Member
    Posted 3 years ago #

    Hi,

    I'm using W3TC to basically modify all my urls to be something like "www.mysite.com", while the content is actually on "origin.mysite.com". The CDN loads the content from origin and serves it on www.

    It works well with the homepage, and I can access it via the "CDNed" name, but info retrived in the template via the_permalink() or get_bloginfo('url') still use the origin site.

    That said, the URLs for the theme have been replaced properly.

    What can I do to get all the URLs to show up as http://www.mysite.com/<something>? Also, is there a simpler way to perform this replacement and use W3TC only for the DB caching?

    Thanks,

  2. Frederick Townes
    Member
    Plugin Author

    Posted 3 years ago #

    Not sure I followed all of that. Can you please submit a bug submission form from the support tab of the plugin? It will include a report that helps me troubleshoot.

  3. Hubert Nguyen
    Member
    Posted 3 years ago #

    Hi Frederick,

    I'm not sure that this is a "bug". I remember that a previous version of the plug-in did modify the permalinks as well (can you confirm?). This might be a "missing feature" that I wish for. In any case, let me know and I can repro/submit/screenshot. Thanks!

  4. Hubert Nguyen
    Member
    Posted 3 years ago #

    In short, I'd like to install wordpress on origin.mysite.com and have all the permalinks rewritten as:

    http://www.mysite.com/yyyymmdd/my-article/

    instead of:

    origin.mysite.com/yyyymmdd/my-article/

    I thought that W3TC did it in the past.

  5. Frederick Townes
    Member
    Plugin Author

    Posted 3 years ago #

    I'm not understanding why you want to use W3TC in this way, so maybe that's not confused. Can you explain the objectives in more detail?

  6. Hubert Nguyen
    Member
    Posted 3 years ago #

    I simply wanted to "CDN" the whole site, including the pages which are mainly static.

    It looks like most people use http://www.mysite.com as the origin domain, then "CDN" non-critical files like themes files, css, and js. It makes sense. I just wanted to do something different.

  7. Frederick Townes
    Member
    Plugin Author

    Posted 3 years ago #

    There is no benefit to doing something different unless there's a specific problem you're trying to solve. :)

  8. Hubert Nguyen
    Member
    Posted 3 years ago #

    Can't argue against that, although being able to CDN the actual html pages, and the whole site in general was pretty cool. :)

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic