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

FAQ added #51

Merged
merged 3 commits into from
Dec 29, 2016
Merged
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
52 changes: 46 additions & 6 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@
Smart, efficient cache solution for WordPress. Use DB, HDD, APC or Memcached for storing your blog pages. Make WordPress faster!

## Description ##
*Cachify* optimizes your page loads by caching posts, pages and custom post types as static content. You can choose between caching via database, on the web server’s hard drive (HDD), or—thanks to APC (Alternative PHP Cache)directly in the web server’s system cache. Whenever a page or post is loaded, it can be pulled directly from the cache. The amount of database queries and PHP requests will dramatically decrease towards zero, depending on the caching method you chose.
*Cachify* optimizes your page loads by caching posts, pages and custom post types as static content. You can choose between caching via database, on the web server’s hard drive (HDD), Memcached (only on Nginx) or — thanks to APC (Alternative PHP Cache)directly in the web server’s system cache. Whenever a page or post is loaded, it can be pulled directly from the cache. The amount of database queries and PHP requests will dramatically decrease towards zero, depending on the caching method you chose.

### Features ###
* Works with custom post types.
Expand All @@ -26,11 +26,6 @@ Smart, efficient cache solution for WordPress. Use DB, HDD, APC or Memcached for
* Settings for Apache and Nginx servers.
* Extendability via hooks/filters.

> #### Auf Deutsch? ####
> Für eine ausführliche Dokumentation besuche bitte das [Cachify-Wiki](https://github.com/pluginkollektiv/cachify/wiki).
>
> **Community-Support auf Deutsch** erhältst du in einem der [deutschsprachigen Foren](https://de.forums.wordpress.org/forum/plugins); im [Plugin-Forum für Cachify](https://wordpress.org/support/plugin/cachify) wird, wie in allen Plugin-Foren auf wordpress.org, ausschließlich **Englisch** gesprochen.

### Support ###
* Community support via the [support forums on wordpress.org](https://wordpress.org/support/plugin/cachify)
* We don’t handle support via e-mail, Twitter, GitHub issues etc.
Expand All @@ -45,6 +40,7 @@ Smart, efficient cache solution for WordPress. Use DB, HDD, APC or Memcached for
* Author: [Sergej Müller](https://sergejmueller.github.io/)
* Maintainers: [pluginkollektiv](http://pluginkollektiv.org)


## Installation ##
* If you don’t know how to install a plugin for WordPress, [here’s how](http://codex.wordpress.org/Managing_Plugins#Installing_Plugins).

Expand All @@ -55,6 +51,50 @@ Smart, efficient cache solution for WordPress. Use DB, HDD, APC or Memcached for
* Memcached in Nginx (optional)


## Frequently Asked Questions ##

### PHP Fatal error: Cannot use output buffering in output buffering display handlers in Unknown on line 0 ###
This error message may occur after commissioning the caching plug-in. The hint appears because there are no cache files on the HDD for output. This is probably due to the fact that Cachify could not store files in the cache folder. Please check the write-permissions for the cache folder (found in the WordPress directory *wp-content*) and set them if necessary.

### My Website looks in some parts broken after activating Cachify! ###
Please make sure there is no issue that caused by the Cache minify feature. Just deactivate it or use HTML only. If the issue still exist please feel free to report it at the [support forums](https://wordpress.org/support/plugin/cachify). With this feature any unnecessary characters such as breaks and HTML comments are removed from the source code.

### Cachify HDD: Character encoding does not work correctly ###
If you use Cachify to store the cache on HDD there is no PHP to run. In the case of misconfigured servers, this can lead to incorrect display of the special characters on web pages. The error can be corrected by an extension of the system file .htaccess: *AddDefaultCharset UTF-8*

### Cachify with CDN support? ###
Currently the caching plugin for WordPress has no connection to a CDN provider. Although the Buzzword CDN (Content Delivery Network) is praised as a performance factor, CDN makes little sense for WordPress websites with a national audience. In this case, a home host could provide the requested files faster than a worldwide CDN service provider because the next node could be far away.

### PHP OPcache as a caching method? ###
Compared to APC (Alternative PHP Cache), PHP OPCache is not able to contain content with custom keys and values. Because of this Cachify can not consider the PHP OPCache as a caching method.

### When does Cachify automaticaly flush its cache? ###
* After publishing new posts
* After publishing new pages
* After publishing new custom post types
* After publishing new sheduled posts (only Cachify DB)
* After updating WordPress
* If you confirm the trash button on the adminbar
* After saving Cachify and wpSEO settings

### Which parts of the website are not cached by default? ###
* Password protected pages
* Feeds
* Trackbacks
* Robots
* Previews
* Mobile-themes (WP-Touch, Carrington, Jetpack Mobile)
* Search
* Error pages

### The cache folder is indexed by search engines! ###
To ensure that Google and other search engines do not index the static contents of the cache folder (otherwise there could be duplicate content), the robots.txt file which is located in the main directory of a WordPress installation should be expanded by disabling the path to the cache file (disallow ). This issue should only happen if you use a *static robots.txt* or you changed the *wp-content* location. And so might look a robots.txt:

> User-agent: *
> Disallow: /wp-content/cache/cachify/
> Allow: /


## Changelog ##

### 2.2.4 ###
Expand Down