subscribe to plugin update

  1. CodeAndMore


    The needed plugin(s) is not working with WP 3.3.1 is there anyway to subscribe and know immediately when plugin author updates it?

    Some types of subscribe function to a specific plugin (then got mail when it is updated) would be helpful I think.

    Posted: 4 years ago #
  2. Due to the fact that not all plugins are hosted on WP.org, it's difficult to provide that level of notification, and not possible today. However, this is something that has been discussed many times.

    Not right now, but it's under consideration :)

    Posted: 4 years ago #
  3. CodeAndMore


    If that is discussed many times, I can see that the community needs it.
    How about at least support for plugins that WordPress hosts?

    Posted: 4 years ago #
  4. It's being worked on, or rather, the best way to do that is being discussed. There are complications (such as not everyone WANTS email notifications, would RSS be better, how should we handle removed/no-longer-supported plugins, etc etc).

    We're looking at the whole picture :)

    Posted: 4 years ago #
  5. CodeAndMore


    OK thanks,
    not everyone WANTS email notifications: the subscribe feature could be just like subscribe to this topic, I got email when you reply.
    would rss be better: it is not better than email for specific plugin from what I can see.
    how should we handle removed / no longer supported plugins: removed => email subscribers about that, no longer supported plugins: same thing, perhaps will require either moderator action or automated process (1 year no updates for example).
    So I guess you know better, where is the main topic so I can join that discussion?

    Posted: 4 years ago #
  6. The code that runs this forum is a different animal :) This site is bbPress.

    This has been an off-and-on convo on IRC and something I've chatted with Otto and Mark about (okay, I nag them, I think it'd be a good idea too).

    I asked around for you about how core gets updates, and basically it takes all your plugin headers, sends it on the API and matches up as best it can. If a plugin's no longer on the repo, it treats it like it never exists. If we alerted users to plugins that were pulled, it would throw false positives.


    duck_ (who is a core contributor!) made this plugin: http://wordpress.org/extend/plugins/update-notifier/

    I would use that, since if it gets picked up, it's more likely to inch its way into core!

    (And right here is the perfect place to posit your ideas about the BEST way a plugin alerter would work)

    Posted: 4 years ago #
  7. CodeAndMore


    OK the logic for subscribing feature is still not too different.

    Assume each plugin would have an unique id in the system.
    We will create a table that connect subscriber user id with that plugin id
    - Subscribe to subversion updates: Each time subversion got new commit, trigger the function to query all subscriber ids along with plugin id, send them email just like email sending to developer.
    - Subscribe to plugin version updates: Each time we have commits, parse readme file and if the version is different from old one, send email, similar as above.

    We don't need to send emails when a plugin is pulled if that is not necessary.

    Posted: 4 years ago #

RSS feed for this topic


You must log in to post.

  • Rating

    6 Votes
  • Status

    This idea is under consideration