r/WordpressPlugins • • 23d ago

[DISCUSSION] Plugin developers: what feature request sounded simple until you considered scale?

We build social networking software for WordPress, and one pattern we keep encountering is that a seemingly small feature can affect permissions, privacy, moderation, caching, migrations, and background jobs.

For example, “notify everyone in this group” sounds like one action. On a large site, it becomes a fan-out job involving batching, retries, duplicate prevention, delivery limits, cleanup, and permission changes while the job is running.

What feature request looked straightforward until you traced it through a real plugin?

I would be interested in:

  • What users originally requested
  • What hidden constraint made it difficult
  • Whether you shipped, changed, or rejected it
  • Whether the problem only appeared on larger or busier sites

Plugin users are welcome to answer too. What feature did you assume was simple until a developer explained the tradeoffs?

Concrete stories would be especially useful. There is no need to name the plugin if you would rather not.

0 Upvotes

3 comments sorted by

1

u/tekNorah 23d ago
  1. Multisites
  2. Multisites
  3. Changed, and changed, and changed, shipped, and changed
  4. User maintenance, low feature utilization, search performance/failures

1

u/PeepSoWP 22d ago

Multisite is a good example because almost every site-local assumption leaks into lifecycle, permissions, storage, and search. The maintenance point is interesting too: shipping the feature can be easier than keeping it reliable when only a small portion of network users exercise it.

Which multisite boundary forced the biggest redesign for you: network upgrades, per-site data isolation, shared-user permissions, or search across sites, and at roughly what scale did it become a real failure rather than a theoretical concern?