WordPress.org

1. cartemd
   Member
   Posted 6 months ago #
   

   We are currently running on a dedicated server. The problem we are having is that when we update a document it correctly posts to the revision log, but some people on other areas of the network try to pull a document it shows the old doc. Currently we have corrected this by clearing our cache on the individual computer. We are an organization of over 300 employees and we need to ensure that the information is up-to-date. Thanks for your help!

   http://wordpress.org/extend/plugins/wp-document-revisions/

2. Christoph
   Member
   Posted 5 months ago #
   

   We are facing the same issue here. I think it's not particularly related to WP Document Revisions but is a problem with Internet Explorer (9) or IIS. See e.g. PDF's not updating. Did you find a solution?

3. Christoph
   Member
   Posted 5 months ago #
   

   I believe appending a unique query string value (like the pdf generation timestamp) to cause the url to be different would prevent caching. Maybe that's a good idea for a plugin!?

4. cartemd
   Member
   Posted 5 months ago #
   

   We have IE 8 and we are still having trouble.

5. P3air
   Member
   Posted 5 months ago #
   

   check your wordpress cache (W3TC, Quick Cache, Supercache, ...); if installed, you should exclude your docs/files;
   check your wordpress theme - certain themes run their elements (and pages) within an 'internal' cache

   $.02

6. Ben Balter
   Member
   Plugin Author
   Posted 5 months ago #
   

   Yes, sounds like a caching issue. There are two possible points at which this can happen.

   Persistent object/database cache via W3TC, etc., which should be cleared when the post is updated.

   Browser cache, which again, could be coming from W3TC, etc. or from your .htaccess file putting expiry headers (or related, via a proxy cache, if any).

   The plugin places the proper last-modified header on the file before serving ( https://github.com/benbalter/WP-Document-Revisions/blob/master/wp-document-revisions.php#L752) , but perhaps a revisit of the expiration is in order?

   The original code was taken form ms-files which was designed to serve static files. It's hard to say what the expires header should be. It sounds like your use case is updated frequently while others may update rarely if ever. I believe this would be best implemented as a filter.

   I've created a issue on GitHub to track the feature. https://github.com/benbalter/WP-Document-Revisions/issues/38. Pull requests are always greatly appreciated if you are able to take a stab.

   For the time being, linking to the specific version of the document (e.g., ?revision=X) or apending a query string (e.g., ?break_cache=1234) should solve the problem until the plugin is updated.

7. Christoph
   Member
   Posted 5 months ago #
   

   We don't use any plugins for caching. In our case it seems to be an issue with IE9 only. Firefox and IE8 always show the current document.

   Maybe it's network-related behavior. We run IIS7 on Windows Server.

   As workaround i appended the unix timestamp to the document url:
   href="<?php the_permalink(); ?>?<?php echo time() ?>"

Reply

You must log in to post.