Hi Matt,
My initial thoughts (#3954-2) about the Futures Initiative BP group using the External Group Blogs plugin were wrong.
As in #459, activity items recorded by the External Group Blogs never sends email notifications. So what you mention in comment 4 (#3954-4) is not applicable at the moment, but we could look at this in a separate ticket.
Pertaining to this ticket, the following is what is actually happening:
- The Futures Initiative BuddyPress group uses BP Groupblog
- The Futures Initiative BP Groupblog is linked to the futures.commons.gc.cuny.edu site.
- On the futures.commons.gc.cuny.edu site, the FeedWordPress plugin is activated. The FeedWordPress plugin is a plugin that allows site admins to include RSS feeds, which are then added individually as WP posts.
- One of the FI site admins added the futures.gc.cuny.edu RSS feed to FeedWordPress.
- BP Groupblog, then, takes the RSS posts and records the post to the group activity feed.
- The BP Group Email Subscription plugin, then, sends out this post for those subscribed to "All Mail".
I got confused between what was happening with the External Group Blogs plugin vs. BP Groupblog / FeedWordPress.
For this ticket, I've added a fix so groupblog activity content with HTML entities are properly decoded for plain-text emails in commit 3a541a7cb7.
I would also recommend removing the External Group Blogs RSS feed for the Futures Initiative BP group because there is no reason to have two RSS feeds with the same content being used -- the first is from External Group Blogs and the other is from the Groupblog site via the FeedWordPress plugin.
One other thing to note is currently, HTML emails do not work outside the main Commons site as we have not network-activated the WP Better Emails / WP Better Emails for BP plugins. The reason why we probably didn't network-activate these plugins is this might interfere with sites that already have existing email solutions or that we do not want to force the main Commons HTML template on all sites. I'm not sure what we want to do regarding this, but since we haven't really received many tickets about this issue, it's probably best to leave things as-is for the time being.
I'm marking this ticket as resolved, but feel free to discuss the issues here or open new tickets for some of them.