Ben Balter
Forum Replies Created
-
This is just a matter of CSS. I would take a look at adjusting the margin and padding of the
li. Any general (non-Document Revisions specific) CSS tutorial should be able to help you here.Please make sure the documents are public. You can verify this by also navigating to
/documents/which should list the same documents there as in the[documents]shortcode.Yes. You would edit your theme’s
archive.phpor copyarchive.phptoarchive-documents.phpand edit it there.Forum: Plugins
In reply to: [WP Document Revisions] [Plugin: WP Document Revisions] Standard descriptionTake a look at the plugin Edit Flow (specifically editorial metadata) which should do this. (or alternatively Advanced Custom Fields).
Unfortunately, that functionality does not currently exist, but you could create it using the shortcode API and the function
get_documents()(coding required).Forum: Plugins
In reply to: [WP Document Revisions] [Plugin: WP Document Revisions] Last updatedForum: Plugins
In reply to: [WP Document Revisions] [Plugin: WP Document Revisions] Work with a CDN?I’ve used it both with W3TC and behind a CDN without any problem.
Great find. Would you mind posting that to the FAQ wiki? Would be good to include in the readme.
https://github.com/benbalter/WP-Document-Revisions/wiki/Frequently-Asked-Questions
The problem is above WordPress in the stack. That’s an Nginx 404 page, meaning it’s not even hitting the rewrite system. Compare
http://crescentridgehomeowners.com/documents/2012/03/crescent-ridge-owasso-welcome-packet.pdf
with
http://crescentridgehomeowners.com/documents/2012/03/foo
It could be that nginx is seeing the extension and thus not using WordPress/php.
WordPress can read the file fine… http://crescentridgehomeowners.com/?document=crescent-ridge-owasso-welcome-packet
I’d open a ticket with WP Engine. I know it’s possible to run the plugin on there.
– Ben
Forum: Plugins
In reply to: [WP Document Revisions] Issue: WP Document Revisions on a NetworkSounds like a permissions issue. Have custom roles? Use the members plugin to define who has what capabilities, and menu, etc. should respond accordingly.
The problem appears to be related to a bad build (a missing dependency). Please try upgrading to 1.5.3 to resolve the issue.
If you are unable to access your site, simply delete (or rename) the
/wp-content/plugins/twitter-mentions-as-comments/folder.Sorry for the trouble.
The problem appears to be related to a bad build (a missing dependency). Please try upgrading to 1.5.3 to resolve the issue.
If you are unable to access your site, simply delete (or rename) the
/wp-content/plugins/twitter-mentions-as-comments/folder.Sorry for the trouble.
The problem appears to be related to a bad build (a missing dependency). Please try upgrading to 1.5.3 to resolve the issue.
If you are unable to access your site, simply delete (or rename) the
/wp-content/plugins/twitter-mentions-as-comments/folder.Sorry for the trouble.
It looks like
$post_pre = $postis actually just assigning a reference, not cloning the post object. I’ve opened an issue on GitHub, and will be sure to get a fix out in the next version.In the mean time there are two options:
1) In your function, set
post_statusback to draft manually2) remove document revisions
make_privatefilter after the plugin adds itMarking the post as resolved (development version) and look for a stable release soon.