Move administration tools from wp-admin to front end

[tellyworth]

Most of the plugin administration tools currently located within wp-admin need to move to the front end. Specifically:

• Plugin Controls (Status and Tested With)
• Committers
• Stats
• Author plugins list
• Admin/reviewer tools

[mapk]

While there should be a link/button for the author's admin section right on the plugin page itself, I'm wondering if there should be a more generalized link someone else within the plugin directory to take the author to an admin overview of ALL their plugins?

Below are examples of where the individual plugin admin link could reside, and they would only be visible to Authors/Admins who are logged in.

v1 - Button under the 'Download' button
​https://cldup.com/2r9cLaqTvV.png

v2 - Link under the author's name
​https://cldup.com/b2QvF1Mhe2.png

v3 - Link under the 'Download' button
​https://cldup.com/uLCTIxlGg9.png

v4 - Link in sidebar under meta data (or above)
​https://cldup.com/a-mtRlbi-O.png

Clicking these would take the user to the admin panel for the specific Plugin.

[samuelsidler]

Thinking longer term, ideally everything could be edited on the front-end, which would automatically sync the changes to SVN for the plugin author. Thinking about it from that point of view, "admin" access is really equivalent to "edit" access for a given plugin. Would an edit button/link make more sense than something called "admin"?

[moonomo]

Replying to mapk:

v3 - Link under the 'Download' button
​https://cldup.com/uLCTIxlGg9.png

This placement and style looks better than the others.

[ramiy]

Replying to mapk:

v1 - Button under the 'Download' button
​https://cldup.com/2r9cLaqTvV.png

v4 - Link in sidebar under meta data (or above)
​https://cldup.com/a-mtRlbi-O.png

I like the button and the sidebar options.

[mapk]

Replying to samuelsidler:

Thinking longer term, ideally everything could be edited on the front-end, which would automatically sync the changes to SVN for the plugin author. Thinking about it from that point of view, "admin" access is really equivalent to "edit" access for a given plugin. Would an edit button/link make more sense than something called "admin"?

It would if it only concerned this plugin, but ideally the user would be able to jump from plugin to plugin within this view... and see an overview of all their plugins together, so in that sense it becomes more of an admin.

[dd32]

In 4212:

Plugin Directory: Remove wp-admin access and a bunch of code that's no longer needed.

See #2111.

[dd32]

In 4213:

Plugin Directory: Allow non-published plugins to be viewed on the front-end by reviewers and contributors/commiters/submitters of the plugin.

This also adds a notice on the top of plugin pages with the status of the plugin.

See #2111.

[dd32]

In 4214:

Plugin Directory: Add a plugin_committer taxonomy and sync it with the svn_access table.
The taxonomy is only used to ease querying, and allows for /author/$self to display both plugins you're listed as a contributor for and those you have commit access for.

See #2111

[mapk]

Just trying to get some content onto a page to review. This is a mockup of a layout idea for the edit screen of the plugin. Most information is pulled directly from the existing wp-admin section that we have up right now.

Notes:

1. Top header section stays visible.
2. Main content area shows a form for updating (fields copied from current wp-admin), and stats.
3. Sidebar keeps some meta data visible but now some of it becomes editable. Committers and Authors are also added.
4. Bottom section shows author's info and other plugins they developed. The dropdown would quickly jump the author to another plugin relating to this author.

[dd32]

In 4224:

Plugin Directory: Add the first foundations for the front-end admin/plugin-edit screen.

See #2111

[dd32]

In 4260:

Plugin Directory: Move the Stats from wp-admin to the front-end /$plugin/admin/ screen.
This also implements the capabilities required for access to the plugin admin screen for each plugin.

See #2111

[dd32]

In 4263:

Plugin Directory: Add no-js handling for JS-only sections and add the start of the admin sidebars.

See #2111

[ocean90]

#2157 was marked as a duplicate.

[pento]

In 4276:

Plugin directory: Fix a PHP warning introduced in [4260].

The return value of get_the_terms() needs to be tested to ensure it's an array.

See #2111.

[dd32]

In 4278:

Plugin Directory: Add some basic Committer/Contributor widgets for the plugin "admin" view.

See #2111

[dd32]

In 4301:

Plugin Directory: Add plugin committer management to the new plugin admin.

See #2111.

[Ipstenu]

Committers wraps funny...

[Ipstenu]

Looking at ​https://wordpress.org/plugins-wp/jetpack/admin/

Change the link from "Edit" to the old "Admin" link - we don't edit (yet) so it will confuse people.

Remove the link to "View the capabilities these users have" - they don't need to care, and if they did, we'd want to link it to something in ​https://developer.wordpress.org/plugins/wordpress-org/ so that's on me and @otto42 to document :)

The spacing between contributors could be bumped, though that's a LOT of people Jetpack. Sheesh!

I uploaded a screenshot of how the committers with long emails get weird wrapping for the remove link. Maybe we should change that to have remove after the display name and NOT the email?

We're missing the links section with this:

• SVN Repo
• Trac Browser
• Revision Log [RSS Feed]
• Support Forum [RSS Feed]
• Support Forums Tag [RSS Feed]

And yeah, I totally need that :)

Also these: ​https://wordpress.org/plugins/jetpack/developers/

Though that might be better off on a front-facing page for non-admins, as it lets people download older versions for debugging.

[dd32]

Change the link from "Edit" to the old "Admin" link - we don't edit (yet) so it will confuse people.

Agreed.

Remove the link to "View the capabilities these users have" - they don't need to care,

I disagree, I think they do need to care, and should be aware of what extra capabilities they've given people indirectly. It should totally be linking to a handbook page though, and probably be listed at the bottom of the list.
I don't care enough though, if/when that page gets added, we can add the link.

We're missing the links section with this: SVN repo.. etc..

That's buried at the bottom of Contributors & Developers

Also these: ​https://wordpress.org/plugins/jetpack/developers/
Though that might be better off on a front-facing page for non-admins, as it lets people download older versions for debugging.

I have no inclination to re-add those myself, it's extra fluff that doesn't matter to 99% of people.
I respect that reviewers probably fit into the 1% though, and there probably needs to be something like that at least for reviewers.

If we want to offer downloads of previous versions, it should probably be connected to the download button in some way.

[dd32]

We're missing the links section with this: SVN repo.. etc..

That's buried at the bottom of Contributors & Developers

I'm wondering if that would be better as a sidebar widget rather than being in the developers section, enforce that they're open-source plugins and the code is readily accessible.

[dd32]

In 4335:

Plugin Directory: Change the admin label to 'Admin' rather than 'Plugin Edit' and remove the Contributors priv note.

See #2111

[Ipstenu]

Also these: ​https://wordpress.org/plugins/jetpack/developers/
Though that might be better off on a front-facing page for non-admins, as it lets people download older versions for debugging.

I have no inclination to re-add those myself, it's extra fluff that doesn't matter to 99% of people.

Yeah and the 1% who needs it will have a hell of a time debugging :) They do need to be accessed so we can send people to them to 'roll back' when a plugin screws up. This is pretty common for debugging in the forums and elsewhere.

Replying to dd32:

We're missing the links section with this: SVN repo.. etc..

That's buried at the bottom of Contributors & Developers

I'm wondering if that would be better as a sidebar widget rather than being in the developers section, enforce that they're open-source plugins and the code is readily accessible.

That's fine :)

I'll write the handbook page for what the permissions/caps/etc are as soon as I can (this week). I meant to on Friday and things happened (™).

[Ipstenu]

Go me!

​https://developer.wordpress.org/plugins/wordpress-org/special-user-roles-capabilities/

[lukecavanagh]

@dd32

I am with @Ipstenu

As long as the previous releases of a plugin are still available easily enough and is not hidden than users can not easily download the last working version of the plugin zip. So they can manually revert a plugin if the current update causes an issue.

I think making it so hidden would be an issue for support.

[tellyworth]

Closing this as generally complete - anything missing or broken belongs in a new ticket please.

[obenland]

In 5117:

Plugin Directory: Clean up comitter widget

Separates JS and CSS from PHP and uses some more core functionality.

See #2111.

[obenland]

In 5121:

Plugin Directory: Fix display of plugin contributors

• Re-uses the contributor widget in the shortcode
• Displays committer-, contributor-, and code-browse-lists correctly
• Fixes the read-more link for contributor list in admin

See #2111.
Fixes #2567

[samuelsidler]

Milestone Plugin Directory v3 - M9 deleted

[dingo_bastard]

Replying to ramiy:

Replying to mapk:

v1 - Button under the 'Download' button
​https://cldup.com/2r9cLaqTvV.png

v4 - Link in sidebar under meta data (or above)
​https://cldup.com/a-mtRlbi-O.png

I like the button and the sidebar options.

Can we get the v4 instead of the unintuitive 'Admin' link under the Download button?

[obenland]

In 5210:

Plugin Directory: Move admin link into meta widget

It's pretty meta after all.

See #2111.

[dingo_bastard]

I was under the impression that the sidebar is created with React xD

Thanks for the quick change @obenland :)