Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Per-Site CDN Configuration (Multisite) #475

Closed
raamdev opened this issue Apr 29, 2015 · 6 comments
Closed

Feature Request: Per-Site CDN Configuration (Multisite) #475

raamdev opened this issue Apr 29, 2015 · 6 comments

Comments

@raamdev
Copy link
Contributor

@raamdev raamdev commented Apr 29, 2015

It would be great if the Static CDN Filters allowed for configuring a specific CDN pull zone for each domain in a WordPress Multisite installation, thereby allowing per-site CDN configuration within a WordPress Multisite environment.

Related: #439 #468

@raamdev raamdev changed the title Feature Request: Per-Site CDN Configuration Feature Request: Per-Site CDN Configuration (WP Multisite) Apr 29, 2015
@raamdev raamdev changed the title Feature Request: Per-Site CDN Configuration (WP Multisite) Feature Request: Per-Site CDN Configuration (Multisite) Apr 29, 2015
@isaumya
Copy link

@isaumya isaumya commented May 9, 2015

I really don't think this is necessary at all. Because in case of WP Multisite a single cdn pull zone can be used for all the sites through out the network. So even if you have 50 sites in your netwrk, a single cdn package will be enough for all site when CDN is activated from the network admin and the plugin is network activated.

I don't think when someone can use a single cdn pull zone for all sites in the network will ever consider paying extra for each individual site.

P.S.: This is how W3TC multisite cdn works too.

@raamdev
Copy link
Contributor Author

@raamdev raamdev commented May 12, 2015

I don't think when someone can use a single cdn pull zone for all sites in the network will ever consider paying extra for each individual site.

You're assuming that all of the sites in a multisite environment are owned by the same person. What if the sub-sites are part of a network where each individual site owner can choose if they want to pay the network admin for adding CDN caching via ZenCache? In that case, it would be desirable to configure a CDN Pull Zone on a per-site basis.

@isaumya
Copy link

@isaumya isaumya commented May 12, 2015

Yes you are absolutely right. But in that case, you can give the ease to the general admin to change the cdn url only. Just the way wo super cache works. If you activate cdn in super cache from the network admin then by default it activates the cdn only for the primary site though its been network activated. Then for the sub site you have to go to that sub site dashboard and on that dashboard you have to go to the super cache settings and then you have to put your cdn url that you want to use. Now if you are the owner of all the sites then you can just use the same cdn url in that case you don't have to pay extra for that site's cdn or you can use a different cdn url.
Hope this idea helps.

@raamdev
Copy link
Contributor Author

@raamdev raamdev commented May 12, 2015

@isaumya Yes, that is how I was thinking this feature would work in ZenCache Pro.

@raamdev
Copy link
Contributor Author

@raamdev raamdev commented May 21, 2015

Support for configuring CDN hostname(s) on a per-site basis in a WordPress Multisite environment has been implemented and this feature will go out with the next release:

2015-05-20_21-37-31

@raamdev
Copy link
Contributor Author

@raamdev raamdev commented May 21, 2015

Next release changelog:

  • Enhancement (Pro): Static CDN Filters now supports the ability to configure separate CDN hostname(s) for each domain (or sub-domain) that you run in a WordPress Multisite Network. Props @jaswsinc. See Issue #475.
raamdev added a commit that referenced this issue Jun 5, 2015
**RELEASE CANDIDATE**

- **New Feature!** The free version of ZenCache now supports several new options that were previously only available in the Pro version. You can now toggle the Auto-Clear Cache routines for the Home Page, Posts Page, Author Page, Category Archives, Tag Archives, Custom Term Archives, RSS/RDF/Atom Feeds, and XML Sitemaps. This gives you more control over exactly when ZenCache purges the cache for these parts of your site. See _ZenCache → Plugin Options → Clearing the Cache_ for further details.
- **New Feature!** URI Exclusion Patterns are now available in ZenCache Lite! This previously Pro-only feature is now available in the free version of ZenCache and allows you to exclude a list of URIs from being cached by ZenCache. See _ZenCache → Plugin Options → URI Exclusion Patterns_ for further details.
- **New Feature!** HTTP Referrer Exclusion Patterns are now available in ZenCache Lite! This previously Pro-only feature is now available in the free version of ZenCache and allows you to define a list of referring URLs or domains that send you traffic. When ZenCache sees a request coming from one of those URLs or domains, it will not cache that particular request. See _ZenCache → Plugin Options → HTTP Referrer Exclusion Patterns_ for further details.
- **New Pro Feature!**: HTML Compression now supports compressing JSON (in addition to the already supported HTML, JavaScript, and CSS compression). Props @jaswsinc. See [Issue #469](#469).
- **New Pro Feature!**: Static CDN Filters now supports multiple CDN hostnames. This allows you to configure more than one CDN hostname, also referred to as Domain Sharding. This makes it possible for site owners to work around web browser concurrency limits, allowing the browser to download many resources simultaneously, which increases overall speed. Props to @isaumya and @jaswsinc. See [Issue #468](#468).
- **Enhancement** (Pro): Static CDN Filters now also apply to any static files that are referenced inside CSS files. Props @jaswsinc. See [Issue #461](#461).
- **Enhancement**: Completed a major restructure of the entire codebase to improve modularity and dependency management. Props @jaswsinc.
- **Enhancement** (Pro): Static CDN Filters now supports the ability to configure separate CDN hostname(s) for each domain (or sub-domain) that you run in a WordPress Multisite Network. Props @jaswsinc. See [Issue #475](#475).
- **Enhancement** (Pro): Static CDN Filters now support sub-domains when ZenCache is running inside a WordPress Multisite Network. Props @jaswsinc. See [Issue #439](#439).
- **Bug Fix** (Pro): Static CDN Filters were not being applied to the primary site on WP Multisite installations that used subdomains. (While subdomains are not currently supported by Static CDN Filters, the primary site can still use this feature.) Props to @isaumya for discovering this bug. See [Issue #470](#470).
raamdev added a commit that referenced this issue Jun 27, 2015
- **Restructured Codebase**: The entire ZenCache codebase has been restructured to improve performance, enhance flexibility, and make it easier to build in new features!
- **New Feature!** The free version of ZenCache now supports several new options that were previously only available in the Pro version. You can now toggle the Auto-Clear Cache routines for the Home Page, Posts Page, Author Page, Category Archives, Tag Archives, Custom Term Archives, RSS/RDF/Atom Feeds, and XML Sitemaps. This gives you more control over exactly when ZenCache purges the cache for these parts of your site. See _ZenCache → Plugin Options → Clearing the Cache_ for further details.
- **New Feature!** URI Exclusion Patterns are now available in ZenCache Lite! This previously Pro-only feature is now available in the free version of ZenCache and allows you to exclude a list of URIs from being cached by ZenCache. See _ZenCache → Plugin Options → URI Exclusion Patterns_ for further details.
- **New Feature!** HTTP Referrer Exclusion Patterns are now available in ZenCache Lite! This previously Pro-only feature is now available in the free version of ZenCache and allows you to define a list of referring URLs or domains that send you traffic. When ZenCache sees a request coming from one of those URLs or domains, it will not cache that particular request. See _ZenCache → Plugin Options → HTTP Referrer Exclusion Patterns_ for further details.
- **New Pro Feature!**: HTML Compression now supports compressing JSON (in addition to the already supported HTML, JavaScript, and CSS compression). Props @jaswsinc. See [Issue #469](#469).
- **New Pro Feature!**: Static CDN Filters now supports multiple CDN hostnames. This allows you to configure more than one CDN hostname, also referred to as Domain Sharding. This makes it possible for site owners to work around web browser concurrency limits, allowing the browser to download many resources simultaneously, which increases overall speed. Props to @isaumya and @jaswsinc. See [Issue #468](#468).
- **Enhancement** (Pro): Static CDN Filters now includes proper support for WordPress Multisite Networks, including support for subdomains (full support for Domain Mapping coming in the next release). If you're running a WordPress Multisite Network and want to configure a CDN, see [this KB Article](http://zencache.com/kb-article/static-cdn-filters-for-wordpress-multisite-networks/) for further details.
- **Enhancement** (Pro): Static CDN Filters now also apply to any static files that are referenced inside CSS files. Props @jaswsinc. See [Issue #461](#461).
- **Enhancement**: Completed a major restructure of the entire codebase to improve modularity and dependency management. Props @jaswsinc.
- **Enhancement** (Pro): Static CDN Filters now supports the ability to configure separate CDN hostname(s) for each domain (or subdomain) that you run in a WordPress Multisite Network. Props @jaswsinc. See [Issue #475](#475).
- **Enhancement** (Pro): Static CDN Filters now support subdomains when ZenCache is running inside a WordPress Multisite Network. Props @jaswsinc. See [Issue #439](#439).
- **Bug Fix** (Pro): Static CDN Filters were not being applied to the primary site on WP Multisite installations that used subdomains. Props to @isaumya for discovering this bug. See [Issue #470](#470).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants