CUNY Academic Commons

That screenshot looks like you're viewing the comments for a doc on which you are not the "admin" or "creator."

You don't see the edit links unless you have the permissions to edit the doc. That's why I created a new group and a new doc so I knew that I'd be the owner of everything involved.

That link to more or less options is just a toggle that turns the dropdown on and off. It isn't a setting that determines what edit options will or will not be seen. Are you the creator of the doc in the most recent screenshot?

No, I'm not the creator of the doc but I am the admin of the group in which it was created.

Then I assume only the creator of the doc can see the edit links.

I'm gonna create a new doc in my local env as a different user and see if I can confirm this.

OK, here's what it comes down to.

As the admin of the group I can see the large grey edit button and the edit links on any and all comments across all docs. Which kinda makes sense for an admin. I'm not sure why, as an admin, you aren't seeing the edit links on the comment in your last screenshot.

When logged in as a "normal" test user I can't see any edit links or buttons on any docs at all.

So there is definitely some Roles and Capabilities code involved here. I jumped on this issue cause I thought I could help Boone out and take some more off his plate. But since he's the author of this plugin I think we should wait to hear what he thinks once he's got a chance to look at his CAC issues again.

okay. Just looked at a doc with comments in another group and can confirm that I see what's in the other screenshot -- just an edit button.

Hi Boone - does that mean that users will no longer be able to edit their comments? I'm not sure that the issues I've identified here warrant the loss of that useful functionality.

I think they'll still be able to edit the comments, but it will happen in the dashboard instead of the front end. But, as I note above, this is happening now anyway, because the plugin is broken.

If we really need the front-end comment editing functionality back, we will have to find a new plugin or write it ourselves.

Okay. Can you create an action reminder to check this functionality after the change is made on production? I don't think we need to worry about front-end editing, just that people do have the ability to edit.

OK, I've made a note: https://github.com/castiron/cac/wiki/Release-ACTION_REQUIRED-list But again, I should underscore that removing the plugin will not affect normal WP comment editing one way or the other, since the plugin is currently non-functional.

Okay -- got it. thanks.

Boone, Matt,

Just wanted to update here quickly before I remove Ajax Edit Comments.

Aside from the Commons, there are 3 sites that have the plugin enabled:

http://globalization.gc.cuny.edu/
http://sciencestudies.gc.cuny.edu
http://keithmiyake.commons.gc.cuny.edu/

All three sites are running JetPack for commenting. I don't even see the Ajax Edit Comments script being loaded on their pages. Which leads me to believe that they've got the plugin enabled but aren't using it.

I wanted your feedback before yanking the plugin out from under them.

Thanks for checking, Dom. Sounds like the plugin's not doing anything on their sites, so we're clear to remove it.

Thanks, removing now for 1.4.11 release.