Offline cache plugin
Sorry, but there are better ways to do this now. This project has been deprecated and is no longer in development. This page will be kept online for archival purposes and in case anyone is still interested in the project despite being no longer maintained.
The manifest cache API used in this plugin has been deprecated, and therefore so has this plugin.
Websites typically require an internet connection to work. Modern browsers do however include offline caching functionality via their cache manifest functionality. It is possible to set a website to cache itself inside the browser when loaded, so that if you need to revisit the page when it is offline, you may do so.
The Offline cache plugin for WordPress allows you to easily implement this functionality on your own website.
Requirements: PHP Dom module
KZeni says:
It appears this is the most up to date offering for providing offline caching of a WordPress site, but it\’s a shame this isn\’t listed in the WordPress.org plugin repository. I just wanted to give a shout out that it might be worthwhile to add this plugin there so more people find it and use it (and would also tap into WordPress\’ plugin install/update/favorites interface).
Thanks!
May 14, 2015 at 8:38 pm # //
Ryan says:
Thanks. I’m concerned that if I post it there, that I may get inundated with people with silly support requests. By putting it on my own site, it tends to weed out the passer bys who just install it via the admin interface and expect it to magically work.
I’ll take your advice on board though and may upload it to the repository in the next few weeks.
Are you using it on a live website?
May 18, 2015 at 5:59 pm # //
zakur says:
Hello Ryan
I just recently downloaded your plugin, but I am getting this error can you help me to fix it
Parse error: syntax error, unexpected ‘TO’ (T_STRING) in /home/admin/web/site/public_html/wp-content/plugins/offline-master/offline.php on line 153
Thanks!
May 26, 2017 at 3:02 pm # //
Ryan says:
Thanks for noticing this. This plugin doesn’t serve any purpose now as the manifest cache API has been deprecated and is no longer supported by many (any?) browsers. I discovered that during a recent update, and probably failed to fix a bunch of bugs after realising that.
I will mark this page as being deprecated to save others from confusion.
May 26, 2017 at 3:28 pm # //