Ben Balter
Forum Replies Created
-
Forum: Plugins
In reply to: [WP Resume] [Plugin: WP Resume] Style wont override themeIf you can, please give the development version (zip) a try which should fix this.
Forum: Networking WordPress
In reply to: Upload limit increase breaks linksdocument_upload_directoryis actually going to be in yourwp_sitemetatable it turns out. If you delete that, it should fix the problem.I found the underlying issue (my apologies for the trouble), and will be pushing a new version of the plugin soon. I believe you will still have to delete that one option from your sitemeta table to fix the problem, but it will not recreate itself going forward.
Getting ready to release a new version (1.3), and could use some help kicking the tires. There are quite a few changes and several added strings if you would like to take a look.
If you find any issues, have any ideas/feedback, etc. please feel free to submit an issue on github
Thanks,
– BenAfter I posted (and began working on an option), I noticed the
documentsis stored in another method as well — apologies about that. I’ve roughed together the option in the development version which although buggy, seems to work (look for it under settings->media). There’s a link to the zip on that page and the development version should fix the permalink issue (you may have to hit save twice).As for translations, the purpose of GlotPress is to do exactly that — collaborate on developing the best translation. If there are some strings which you believe can more accurately reflect their intent, by all means, please feel free to submit them, and I will be sure both translators get credit. It’s not as if one translator “owns” the rights to translate, etc. I will also have additional strings (as a result of the option), which I will add to GlotPress soon.
Checked in should be the opposite of checked out, which would mean in this case, to make changes and upload a new version for others to edit/review, but could be published if the document is public. Does that make sense?
I’ve created tickets
https://github.com/benbalter/WP-Document-Revisions/issues/6
and
https://github.com/benbalter/WP-Document-Revisions/issues/7
I think it makes sense to make /documents/ an option in the UI… so look for that soon.
Also, regarding “Checked out” it should be checked out as in “I checked the book out of the library” (meaning nobody else can). Meaning temporary possession. Meaning I am editing the document, but nobody else can.
Last, my spanish is rough, but publication state make sense.
– Ben
First, regarding the Spanish translation — Thank you for taking the time to contribute. There’s actually a translation in the works by another user, which you can browse on glotpress. It sounds however, if your translation has been more thoughtful / purposeful / thorough, so if you create an account, you should be able to revise by adding your version where you think appropriate. I can upgrade your account so that you can commit directly from the web interface. (the link you provided seems to 404).
The rewrite rules (that create /documents/) are actually a custom set of rules to deal with revisions. There’s a filter, however, so you can modify the rules without editing the plugin (
document_rewrite_rules).So you could either create a standalone plugin, or add to your functions.php something along the lines of:
function bb_translate_document_slug( $rules ) { $output = array(); foreach ( $rules as $key => $value ) { $output[ str_replace( 'documents', 'documentos', $key ) ] = $value; } return $output; add_filter( 'document_rewrite_rules', 'bb_translate_document_slug' );Let me look into the missing translations (or your welcome to submit a pull request if you feel comfortable), and will be sure to update the glotpress install as well as the POT file of the development version. Last, I’ll check around and see if it makes sense to make the slug directly translatable.
Thanks again for taking the time to contribute.
– Ben
Forum: Networking WordPress
In reply to: Upload limit increase breaks linksFigured out what’s going on, and will have a fix out shortly.
In the mean time, if you delete the global option
document_upload_directorydirectly from the database (just remove the row completely), your documents should be accessible again (it will return to the default directory).My guess is that the location field auto propegated with a bad value, which hitting save on the page then stored. Will fix.
Forum: Plugins
In reply to: [WP Resume] WP Resume won't call the resume.php file in theme folderIf you can, please give the development version (zip) a try which should fix this.
Forum: Plugins
In reply to: [WP Resume] [Plugin: WP Resume] No Content DisplayingLooks like the plugin’s firing, but not finding your info. Not sure exactly what’s going on, but I’d start by deactivating all other plugins, and also explicitly passing the author.
Forum: Plugins
In reply to: [WP Resume] WP Resume won't call the resume.php file in theme folderThis is a known bug. In the mean time, you can put the file in the templates folder of the plugin (overwriting the default), and look for a fix soon.
Forum: Plugins
In reply to: [WP Resume] [Plugin: WP Resume] Display Parts of resume on a page…( This is now included as part of the plugin )
Take a look at either Members or Role Scoper Plugins. You’ll want to create a custom taxonomy for the departments and assign permissions accordingly. Not part of Document Revisions or Edit Flow itself, but pretty easy to do with WordPress.
Take a look at either the Members plugin, or the Role Scoper plugin. Regarding teams, you’ll want to make a custom taxonomy, and assign permissions accordingly. I suspect your documents are private and your other roles do not have the read_private_documents capability.
replace “w” with workflow_state and that should work. You may need to refer to the state by it slug, rather than ID, so “under-review” rather than “6”.