Bug #6356
open
Should Subscribe2 be deprecated?
Added by Luke Waltzer about 8 years ago.
Updated over 7 years ago.
Category name:
WordPress Plugins
Description
We might want to investigate the Subscribe 2 plugin... these users -- https://jitp.commons.gc.cuny.edu/wp-admin/admin.php?page=s2_tools -- don't look real.
Don't think it causes much harm, but we might look to see if this plugin is being utilized on the Commons and deprecate if not. Could be part of a larger effort to identify best methods for facilitating notification of new posts and push users towards that solution.
- Status changed from New to Assigned
- Assignee set to Boone Gorges
- Subject changed from Subscribe2 to Should Subscribe2 be deprecated?
- Assignee changed from Boone Gorges to Luke Waltzer
- Target version set to Future release
It looks like JITP may have had a Subscribe2 public widget at some point, and it got some spam registrations.
Subscribe2 is active on 46 sites on the Commons. It's hard to tell without some deep dives into mail logs whether the plugin is working, though we haven't heard bug reports, so I'm guessing that it's at least functional. I'm strongly in favor of eliminating redundant plugins, but we'd need to have an alternative subscription workflow on offer. I think we have a couple (like the group blog setup) but perhaps we need more refinement of that process, and the surrounding documentation, before we start forcing people into it.
Let's consider this sometime in the future.
- Assignee changed from Luke Waltzer to Tahir Butt
Tahir, can you do some tests with Subscribe2 on a test blog on the Commons? I haven't looked closely at the plugin in a few years, and I'm no longer sure what it's supposed to do or whether it's working. I'd welcome your recommendation about whether it's worth keeping.
- Assignee deleted (
Tahir Butt)
Subscribe2 isn't working for me. Do we have an alternate? Thanks!
- Status changed from Assigned to Reporter Feedback
Marilyn, can you give more details on how Subscribe2 is not working? I'd like to distinguish between total plugin failure (in which case we should definitely remove/deprecate) and certain configs/features not working.
Also available in: Atom
PDF