다운로드

Blizhost CloudCache Purge

작성자: Blizhost

설명

Blizhost CloudCache Purge sends a request to the Blizhost servers clear the cache every time the content of your site is modified. This occurs when publishing, editing, commenting or deleting a page or post, and when changing themes.

Our plugin will also make your WordPress site completely compatible with CloudCache!

This plugin is exclusive to Blizhost customers, and will have no results if used outside of our hosting.

클라우드캐시란?

CloudCache is an HTTP accelerator designed for high traffic websites. Your website is delivered directly from the RAM of the server, making loading 300x more faster and dramatically increasing access capacity to the site.

In contrast to other web accelerators, such as Squid, which began life as a client-side cache, or Apache and nginx, which are primarily origin servers, CloudCache was designed as an HTTP accelerator. CloudCache is focused exclusively on HTTP, unlike other proxy servers that often support FTP, SMTP and other network protocols.

Technologies like CloudCache are used by high-profile, high-traffic websites including Wikipedia, online newspaper sites such as The New York Times, The Guardian, The Hindu, Corriere della Sera, social media and content sites such as Facebook, Twitter, Vimeo, and Tumblr. Among the Top 10 thousand sites in the web, around a tenth use this technology.

플러그인 세부정보

Our plugin in addition to making your site compatible with our system will clean your site cache automatically whenever you publish/update a post or page.

Not all pages are purged every time. When a post, page, or custom post type is edited, or a new comment is added, only the following pages will be purged:

  • The front page
  • The post/page edited
  • Any categories or tags associated with the page
  • The pagination pages

그 밖에 사용자의 모든 캐시는 다음 작업으로 제거됩니다.

  • 퍼머링크 변경
  • 테마 변경
  • 알림판에서 ‘클라우드캐시 제거’ 버튼을 누르세요
  • Press the ‘Blizhost CloudCache > Purge Entire Cache’ button on the toolbar

참고: 하위 폴더를 사용하는 멀티사이트 네트워크에서 네트워크 관리자 만 메인 사이트를 제거할 수 있습니다.

스크린샷

  • 대시보드 "지금 바로" 에서 '클라우드캐시 제거' 버튼

설치

No WordPress configuration needed.

요구사항

  • Pretty Permalinks enabled
  • Blizhost 계정에서 클라우캐시 활성화

언어

  • 영어
  • Portuguese-BR

FAQ

모든 워드프레스 플러그인과 테마는 클라우드캐시와 호환이 가능한가요?

CloudCache is designed to be compatible with most plugins and themes, it works with the same basic principle of other caching systems, and many developers are concerned with creating cache-compatible plugins.

But unfortunately they are not all, a minority does not care about performance. Because most sites are small and do not get much traffic, this is not a concern for these developers.

So we recommend that you always use well-known plugins and themes.

After all, if you care about speed and performance, it’s not a good idea to have a plugin on your site that is not suited for high-traffic sites!

새 게시물을 작성할 때 왜 모든 페이지를 지우지 않나요?

The only pages that should purge are the post’s page, the front page, categories, and tags.

When building out this plugin, there were a couple pathways on how best to handle purging caches and they boiled down to two: Decisions (the plugin purges what it purges when it purges) and Options (you decide what to purge, when and why). It’s entirely possible to make this plugin purge everything, every time a ‘trigger’ happens, have it purge some things, or have it be so you can pick that purges.

내 테마를 편집할 때 왜 캐시가 제거되지 않나요?

Because the plugin only purges your content when you edit it. That means if you edit a page/post, or someone leaves a comment, it’ll change. Otherwise, you have to purge the whole cache. The plugin will do this for you if you ”change” your theme, but not when you edit your theme.

If you use Jetpack’s CSS editor, it will purge the whole cache for your site on save.

어떻게 모든 캐시를 수동으로 제거할 수 있나요?

Click the ‘Purge CloudCache’ button on the “Right Now” Dashboard (see the screenshot if you can’t find it).

There’s also a “Blizhost CloudCache > Purge Entire Cache” button on the admin toolbar.

버튼이 보이지 않아요!

If you’re on a Multisite Network and you’re on the primary site in the network, only the network admins can purge that site

On a subfolder network if you flush the site at example.com, then everything under that (like example.com/site1 and example.com/siten and everything else) would also get flushed. That means that a purge on the main site purges the entire network.

In order to mitigate the destructive nature of that power, only the network admins can purge everything on the main site of a subfolder network.

클라우드플레어와 같은 프록시 서비스와 이용할 수 있나요?

Of course! Feel free to use with any proxy or CDN service.

어떻게 클라우드캐시를 비활성화하나요?

You can open a support ticket on the client panel requesting the removal of CloudCache. But it’s important to note that this technology makes your site up to 300x faster and with support for high traffic.

후기

이 플러그인에 대한 평가가 없습니다.

기여자 & 개발자

“Blizhost CloudCache Purge”(은)는 오픈 소스 소프트웨어입니다. 다음의 사람들이 이 플러그인에 기여하였습니다.

기여자

“Blizhost CloudCache Purge”(이)가 2(으)로 번역되었습니다. 기여해 주셔서 번역자님께 감사드립니다.

자국어로 “Blizhost CloudCache Purge”(을)를 번역하세요.

개발에 관심이 있으십니까?

코드 탐색하기는, SVN 저장소를 확인하시거나, 개발 기록을 RSS로 구독하세요.

변경이력

4.0.4

  • Fixed an incompatibility bug that was preventing the execution of the current page when clicking on ‘clear cache’ and then performing actions with other plugins
  • Fixed a bug where ‘after_purge_url’ was not obtaining the result of the request

4.0.3

  • Fix bug that enabled CDN for external domains
  • Enable CDN for PNG images

4.0.2

  • Improved CDN resource compatibility with various themes and caching plugins
  • Support for PHP version 8.1

4.0.1

  • 보안상 이유로 슬라이더 레볼루션을 제거

4.0.0

  • Fixed bug that removes URL from styles and scripts due to hashed version security

3.9.9

  • Remove version of WordPress from rss and header for security reasons
  • 워드프레스 보안 개선

3.9.8

  • Fixed non-existent is_plugin_active function error

3.9.7

  • Fixed compatibility issues with the super-cache plugin and similar

3.9.5

  • Require Jetpack-connected plugin to use WordPress Image CDN feature

3.9.4

  • Fixed bug where CDN did not work for http protocol
  • Improved CDN url regex, filtering content through output buffer
  • Added option where you can disable CDN by DISABLE_WP_CDN

3.9.3

  • Improved http protocol of WordPress CDN for more compatibility

3.9.2

  • Improved WordPress CDN

3.9.1

  • WordPress CDN implemented

3.9

  • Plugin renamed for better understanding of this tool
  • Button on the admin toolbar has been improved

3.8

  • Purge the pagination pages of cache when a post is created or edited

3.7

  • Ignore “DONOTCACHEPAGE” on homepage and posts
  • Fixed bug where it was not possible to clear the cache outside the administrative area in some situations
  • Prevents requests sended to servers if the site is not hosted on Blizhost

3.6

  • Fixed bug that “DONOTCACHEPAGE” was not defined under certain circumstances

3.5

  • Fixed compatibility bug on sites hosted outside Blizhost (even without any effect)

3.4

  • Several enhancements to make Blizhost CloudCache compatible with various WordPress plugins and themes
  • Now the CloudCache can be skipped at the backend level
  • Added “DONOTCACHEPAGE” constant so plugins can specify pages that should not be cached
  • Forced cache cleanup now works for the entire domain

3.3

  • Improves plugin security when creating an API key if it does not exist
  • Support for WP-CLI commands and PHP > 5.5
  • Fix typo (on -> one)
  • Correct permissions on Multisite
  • Correct weird merge error
  • Fix formatting in Changelog
  • Allow filter for home_url()
  • Added wp-cli commands to flush specific URLs and wildcards
  • Requires wp-cli 0.25+ to work for WP 4.6+
  • Update purgePost() to validate page_for_posts
  • Add check for AMP
  • Purge ‘default’ AMP URL as well

3.2

  • Fix bug in permalinks notice
  • Sends the plugin version in the request to the Blizhost server to avoid conflicts

3.1

  • Fix infinite redirect loops when loading WordPress sites under CloudFlare

3.0

  • Automatic purge of sitemaps implemented

2.9

  • Checks if session was initialized before loading CSS

2.8

  • Change purge notice so it can be dismissed
  • Fix purging of deleted posts
  • Fixing i18n which wasn’t working and threw a error on sites without pretty permalinks

2.7

  • Fixed Blizhost logo on admin bar

2.6

  • Some language fixes
  • Fixed font style on admin bar

2.5

  • Minor fixes
  • Some language fixes
  • Blizhost logo changed from png to font style

2.4

  • Retain query params on purge
  • Do not use query part for regex purging
  • Allow CloudCache IP to be filtered.
  • Improve flushing for cases when there’s no Post ID
  • Add filter so other plugins can add events to trigger purge when they have no post ID
  • Add compatibility with Autoptimize so it flushes CloudCache when you flush their cache

2.3

  • Fixed language directory.
  • New tags.
  • Fixed Domain Path.

2.2

  • Translated to Portuguese-BR.

2.1

  • Fixed compatibilities issues.

2.0

  • Several performance upgrades, security and new filters added.

1.0

  • The code was clean, getting more consistent and adopting best code practices.

기초

평점

이 플러그인은 평가가 아직 없습니다.

평가를 제출하기 위해 로그인합니다.

기여자

지원

지난 2개월 동안 해결된 문제:

1 중 1

지원 포럼 보기