WordPress.org

Making WordPress.org

Opened 7 months ago

Last modified 3 months ago

#2627 new enhancement

Closed plugins should still have a public page

Reported by: tellyworth Owned by:
Milestone: Priority: high
Component: Plugin Directory Keywords: ui-feedback needs-patch
Cc:

Description

Currently, closed/disabled plugins show a 404 error page for regular users.

It would be better to have at least a minimal public page for historical context. Perhaps with download links etc disabled.

Attachments (3)

2627-make-disabled-page-visible.diff (1.2 KB) - added by tellyworth 7 months ago.
Make closed plugins visible from its slug page only.
2627-theme-disable-download-button.diff (1.0 KB) - added by tellyworth 7 months ago.
Disable the download button for public users on closed plugin pages.
2627-add-noindex-meta.patch (4.7 KB) - added by jipmoors 4 months ago.
Adding meta robots noindex to disabled plugin page

Download all attachments as: .zip

Change History (13)

@tellyworth
7 months ago

Make closed plugins visible from its slug page only.

@tellyworth
7 months ago

Disable the download button for public users on closed plugin pages.

#1 @tellyworth
7 months ago

  • Keywords has-patch added

The two initial patches give a minimal implementation to start with.

Closed (disabled) plugins are visible from the slug page - https://wordpress.org/plugins/wpclef/ for example. They don't appear in search results or other list contexts.

The theme patch hides the Download button on closed plugins. There are probably other things that should be disabled or hidden, and the message should be better - perhaps "This plugin has been closed and is no longer available for download."

#2 @Ipstenu
7 months ago

Historically disabled and closed plugins have not been displayed because they're usually done so for pejorative reasons.

Ill or nill, unless we're documenting WHY things are closed, I don't think it's wise to show closed plugins except to say "This plugin is closed..." as it would just cause the same FUD we have today (which I don't like, and yes, I'd like us to tackle in phase 2 :D )

Instead of showing the readme, I would recommend we display a simple message.

Closed: This plugin has been closed and is no longer available for download.

Disabled: This plugin has been closed for new installs.

In both cases for owner/admin: If you did not request this change, please contact plugins@… for a status. All developers with commit access are contacted when a plugin is closed, with the reasons why, so check your spam email too.

Then we can start considering how to properly flag things as 'closed by developer request' and 'closed for guideline infraction' (though I don't want to dog-shame developers and publicize their mistakes if I can help it...)

This ticket was mentioned in Slack in #meta by tellyworth. View the logs.


7 months ago

@jipmoors
4 months ago

Adding meta robots noindex to disabled plugin page

#4 @jipmoors
4 months ago

My new patch is doing the following:

  • refreshing the template file
  • removing JSON LD
  • adding meta robots: noindex to the page

#5 @jipmoors
4 months ago

Related #2860

Last edited 4 months ago by SergeyBiryukov (previous) (diff)

#6 @Ipstenu
4 months ago

FYI #2860 is intended to _eventually_ be incorporated into this, but step one is to record why :) Then I have to figure out how we go back through the thousands of closed plugins and record things properly. Bad data is as useless as no data, after all. That's the phase 2 I mentioned before.

This ticket was mentioned in Slack in #meta by ipstenu. View the logs.


3 months ago

#8 @melchoyce
3 months ago

  • Keywords ui-feedback added

#9 @melchoyce
3 months ago

@tellyworth Can you add some screenshots of your patch?

#10 @SergeyBiryukov
3 months ago

  • Keywords needs-patch added; has-patch removed

The latest patch does not address comment:2.

Note: See TracTickets for help on using tickets.