Hyper Cache Version 2.6.6

This version is an attempt to find ad give advice to poeple who have some blog folder not writeable and deny Hyper Cache to save options.

This version does not solve the problem (that cannot be solved) but tries to make tests and print error messages.

Hyper Cache Version 2.6.5

This new version is an update for Windows systems. On Windows based hosting the PHP function filectime() cannot be used, so I changed it on filemtime().

The problem was discovered and solved by Sergey T.

Thank you Sergey!

Hyper Cache Version 2.6.4

This version has no new features or bugs fixed, it’s only a version to update the plugin compatibility infos. So, even if software is evil, this new version has to works as the previous one.

Hyper Cache And HTML Tidy For WordPress

Today Benjamin Wittorf wrote me and told me that now his plugin (HTML Tidy for WordPress) natively integrate with Hyper Cache.

The latest version of Hyper Cache gives an hook to other plugin to manipulate the HTML source before it is cached. HTML Tidy for WordPress does exactly that, and I’m very happy.

Other plugin can integrate with Hyper Cache, eg. plugins that manipulate the HTML source to make it optimized for search engines.

It would save a bit of resources on your hosting platform.

Hyper Cache version 2.6.2

This version only adds a new options to control if Hyper Cache has to send a special HTTP header: Last Modified. This header is used to inform browser about the last time the page has been modified. Browser cache that page anf the Last Modified time information.

When browser need to ask the page a second time, thay send the time information they received asking IF their copy is still valid. Hyper Cache intercepts this kind of requests and can answer with a “your copy is ok, use it”.

That protocol between browsers and servers can improve performances and bandwidth, but some users are reporting it creates problem with special hosting configurations.

Hyper Cache version 2.6.1

Hyper Cache 2.6.0 was wrongly reporting it is not able to write in the cache folder. It’s bug and you can see the files are there or via FTP or from the admin panel looking the the file count.

Solved in 2.6.1. The writable status of the cache folder is still in place, but the control has been moved to the admin panel instead of generate a general WordPress message.

Hyper Cache 2.6.0

This version is a simple fix only for people who experienced errors because Hyper Cache wasn’t able to write in the cache folder.

Now Hyper Cache creates its own cache folder ON ACTIVATION, so, I hope, there are no more problem with folder permissions.

Another important modification is about some header Hyper Cache sends to browsers that should solve the issues about browsers (Chrome and Safari) to not verify if a page has been modify since the latest download.

Hyper Cache Version 2.5.9

I’ve made a number of minor releases until today just to try to solve a “date” bug that was affecting the cache system of some browser (Chrome and Safari for sure).

I was a my fault when I rewrote partially the plugin to make it easy to install.

The latest update, I hope, will solve any problems. If there is no other bugs, I want to have a rest time over Hyper Cache development cause my regular job is making me really busy!

Hyper Cache 2.5.5

I know, I stopped to answer your precious questions. But my regular job overwhelmed me and I decided to do not release a new version, even if almost ready of Hyper Cache.

Today I had 30 minutes, I gave an look to all the code and decided to release.

Hyper Cache 2.5.5 has deep changes. To solve problem with not writable wp-content, with directory creation and so on, I moved almost all the hyper cache generated files in to the hyper-cache.

On installation and activation only one file will be written in wp-content, the advanced-cache.php which is a required file by WordPress. So now you can safely delete other hyper-cache related files or directories.

To do a clean job, you can disable hyper-cache, clean up (delete the advanced-cache.php too) and the reactivate. Now there is the “one click install mode”, so on activation hyper cache starts to work immediately.

The cache file count in the configuration panel is of all cache files, even if they are expired, so it doesn’t measure the real valid cache pages. Distinct counts will be available in a future release. Still, the new invalidation process do not remove expired cache files, but only store the invalidation time. Is more efficient specially with blog with a great amount of pages.

SO DOT NOT THINK THAT A PAGE IS NOT EXPIRED IF IT’S FILE IS IN THE CACHE FOLDER.

On auto update from WordPress, the cache repository is deleted which is the correct way to update: some people claim that after updating Hyper Cache the cache pages are lost: would you keep cached pages with a different format due to version change? I don’t believe so…

If you enable gzip compression, the cached page are stored compress. There is good reasons to do that, so do not ask me why you cannot use gzip compression and store uncompressed pages.

Autoclean: it’s better to leave it enabled. I don’t know why people want to disable it, but is not recommended. Leave for autoclean a time of 30-60 minutes otherwise your cache folder will explode.

My personal setting: timeout at 1440 minutes, autoclean 60 minutes, compression enables, redirects cached, invalidation “single post” with archive invalidation flag enabled (but for best performance can be left unchecked).

Hyper Cache Versions 2.5.0 and 2.5.1 Important Note

That two version suffer of a bug: if you have the html optimization flag enabled, even if it’s writtem it is no more supported, it make the cache to break the pages. Please, disable the option!

Next Page »