Making WordPress.org

Opened 14 months ago

Closed 3 months ago

Last modified 7 weeks ago

#6880 closed enhancement (fixed)

Persistent plugin author notifications

Reported by: dd32's profile dd32 Owned by:
Milestone: Priority: low
Component: Plugin Directory Keywords: has-patch
Cc:

Description

Sometimes plugins get closed without plugin authors being aware - such as when their email bounces, or their email address goes to a place where the author doesn't monitor. The plugin author usually then emails with a "Huh? Why didn't I get told?" or "Sooo I just found out my email was broken.. what do I do?", requiring plugin reviewers to then explain it to the author.

In those cases, and many others, it would be beneficial to to be able to add a persistent notification at the top of their plugins page explaining it to them.

This could be used both when the plugin is closed, or as a not-so-gentle reminder of "Please stop doing XYZ".

In the future, it could be extended to also be actionable alerts, but the PR I'm about to attach is a one-way communication method.

Change History (8)

This ticket was mentioned in PR #135 on WordPress/wordpress.org by @dd32.


14 months ago
#1

  • Keywords has-patch added

#2 @dd32
14 months ago

  • Resolution set to fixed
  • Status changed from new to closed

Let's see if this gets any useful feedback from plugin authors, whole bunch of plugins are going to be closed due to bouncing emails from the WP 6.2 emails.

Typo'd it in r12492


Plugin Directory: Add ability to define a 'Plugin Author Notice' for plugins.

This is a notice that plugin reviewers can set, that is then visible on the plugins page by plugin authors/committers.

The intent is that this can inform plugin authors why their plugin has been closed when they miss the email.

Fixse #6880.
Closes https://github.com/WordPress/wordpress.org/pull/135.

#3 @dd32
14 months ago

In 12497:

Plugin Directory: Author Notice: Ensure that it always has a <p> element.

The notices look bad without at least one wrapping block element, and when copy-pasting from other sources contentEditable isn't always perfect.

See #6880.

#4 @dd32
14 months ago

In 12506:

Plugin Directory: Author Notice: Enforce a smaller set of HTML tags.

This results in <span>'s and various hidden styles from being saved.

See #6880.

#5 @dd32
14 months ago

  • Resolution fixed deleted
  • Status changed from closed to reopened

Improvements:

  • Being able to clear the alert without having to both clear it and set to no-show. (Currently clearing it will also turn it off, but that's not obvious)
  • Templates for common responses

#6 @dd32
10 months ago

In 12756:

Plugin Directory: Author Notice: Style ordered lists and pre tags better. Add a set() method for other code to set the notice.

See #6880.

#7 @dd32
3 months ago

  • Resolution set to fixed
  • Status changed from reopened to closed

Noting, that any warnings generated during the import process (which includes Readme warnings, and a few other things that cause the import process to bail) are now presented similarly to author notices.

[13238]

I'm closing this ticket for now as fixed, future iterations may get a future ticket.

This ticket was mentioned in Slack in #forums by jordesign. View the logs.


7 weeks ago

Note: See TracTickets for help on using tickets.