Michael George

No response in a week, so I’m considering this closed. I haven’t done much testing, but everything appears to be working in 4.1 for me, so I updated the plugin readme file to list support for 4.1.

I’ve not tested a ton with 4.1, but I do have a server running 4.1 that seems to be running this plugin without issue. Have you found any issues with 4.1 that I need to double check before I give it the “official” stamp of approval on 4.1?

Oh, forgot to say that a new version has been uploaded, so let your WP download and install the update and you should be set for the fix. You can then modify the file and change your default permissions.

Yeah, there is no donate button. The plugin was written while I was work, for work purposes, so they “own” it, not me. This means I can’t take money for it. A by-product is that unless any problems come up with it at work, new versions are on my own time. :/

In the meantime, I setup a test this weekend and fixed the interaction with the wiki plugin. I imagine this would have also been an issue with any other plugin that provides an edit interface that isn’t calling the main WP edit page, but I don’t know of any plugins like that, so i can’t verify it. It does now work properly with WordPress Wiki Plugin at least.

As for default permissions, changing what is now line 158 to this:
$returnValue[] = array( "id" => 1, "name" => "logged in users", "permission" => "read" );
worked correctly for me.

Well, support is limited as this is purely a labor of love. That said, I think I can take a look at this sometime this week or possibly this weekend. Sorry for the delay. Of course, I can’t guarantee that it’ll work how you want, but I’ll do my best.

Pushed new version to fix issue. Problem was a hard-coded check for https, so if you used http, you were out of luck. Closing this thread, though there will be another new version soon to address some suggestions from WPHaider.

Would you be willing to shoot me an email? I’d like to get a see about doing a remote assist session. [email protected]

Yeah, you caught me on a morning when I was around my desk.:)

Last question before I say let’s do a remote assist: you aren’t seeing it on an actual post type of ‘post’? I can’t say I tested with any custom post types or anything, though I do seem to recall it works okay on the ‘page’ type.

I’d like to figure out what’s going on here. Can you provide a list of what plugins you have enabled, what theme you have, and what wp version?

Closing this thread due to lack of new activity.

That is definitely strange. No, there is no code you should need to add. No, there is currently no option for text rather than a button in post meta.

When editing a post, do you see the suggest review meta box at all?

You should be okay to upgrade. I had released one on Tuesday that had all the changes, but found a bug and fixed it yesterday. So snag 1.1.1 and you should be good to go.

Added new version to take care of all this, except for item 3, which is really not something that is a deal breaker. It’s more an issue of semantics. Still, if anyone ever has a suggestion for better wording, I’m listening.

Sorry for the delay, I was on vacation.

1) Yes, that does look a space in the username would cause the user to be discarded. I can’t say I’ve verified that, but it looks likely. I can switch out the regular express being used for one that only checks for the usual newline type characters instead of all white space characters. As wordpress doesn’t really support a space in the username, though, I’m not going to check it, so use at your own risk.

2) Yeah, the “public” things are a bit of a misnomer. I tried to think of a better way to say it, but gave up and settled on public. What that really means is that the user must be logged in and have a wordpress role that would normally allow them to edit that post. So a contributor, by default, wouldn’t be able to edit anyone else’s posts besides their own, whereas an editor would be able to edit everyone’s, as long as this plugin gave permission as well. Admins can still edit whatever, regardless of this plugin. I’m open to suggestions on wording to use instead of “public”, but I wanted to keep it short.

3) It should be that only someone who can edit a post via role and this plugin would be able to change the permissions. As this was originally an idea for use internal to my organization, there was enough trust that if you can edit it, you can edit permissions as well. I could add in an option to only allow permissions changes via administrators, but that would mean that an admin would have to be contacted for each change. Depending on the site, that could get tedious. Nevertheless, I can pop it in if you want.

4) Category limits. Interesting. I don’t see why this wouldn’t be possible. I think it could easily filter the categories before they appeared on the list on the edit page. I’ll start checking into it.

I’ll start incorporating items 1 and 4, which shouldn’t take too much time (this is an ‘as time allows’ project though, so please be patient). If you have thoughts on 2 and 3, let me know and I’ll see what I can do.

No reply in a week. Closing thread.