[wp-trac] [WordPress Trac] #44198: add "Multisite support" readme header to plugin directory

[WordPress Trac]

#44198: add "Multisite support" readme header to plugin directory
-------------------------+----------------------
 Reporter:  littlebizzy  |       Owner:  (none)
     Type:  enhancement  |      Status:  closed
 Priority:  normal       |   Milestone:
Component:  Plugins      |     Version:
 Severity:  minor        |  Resolution:  wontfix
 Keywords:               |     Focuses:
-------------------------+----------------------
Changes (by jeremyfelt):

 * keywords:  reporter-feedback =>
 * status:  new => closed
 * resolution:   => wontfix
 * milestone:  Awaiting Review =>


Comment:

 Replying to [comment:4 littlebizzy]:
 > By not having such a notice/warning, one could argue the plugin
 directory is insinuating Multisite support as being the norm, when in fact
 the majority of plugins are not tested by their author in a Multisite
 environment.

 I agree that most plugins are likely not tested by their authors in a
 multisite environment. However, I don't think most of these plugins are
 incompatible with multisite. Many of the APIs used by plugins work exactly
 the same in both environments and there is no reason to expect a
 difference.

 Adding a header for multisite compatibility would likely leave most
 plugins reporting as incompatible with multisite. Plugin authors would not
 really have a compelling reason to test in a multisite environment and
 manually confirm.

 In the rare case where a plugin is compatible with single-site and not
 with multisite, I would rather find a way to document an alternate
 approach or address any underlying bugs in core so that it doesn't remain
 a compatibility problem.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/44198#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform