Ben Balter

You need to increase your PHP Memory Limit:

http://www.dailyblogging.org/wordpress/increase-wordpress-memory-limit/

The page should contain the position title and description. If not, it would most likely be a templating issue, which you could make a template specifically for the position post type.

Good find. If you could package this into a pull request on GitHub, would love to include this in the plugin.

As for the backend, it sounds like another plugin is causing a Javascript conflict. I’ve seen this a few times before. Try deactivating all plugins, and then the sections should be draggable.

As for the changes, if you could package and submit a pull request to github, I’d love to include in the plugin.

Created a feature request on GitHub for this issue. If you are able to, a pull request would be greatly appreciated. (would be a matter of translating the string before looking for the order, I believe).

https://github.com/benbalter/WP-Resume/issues/16

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.

This error is usually thrown when wp-content is not writable (or any of its sub folders). You’ll want to chmod -r 0777 wp-content to recursively set permissions. Alternatively, verify that if you’ve moved your document upload directory, that that spot is writable as well.