Style Plain Text Email Content

Hi @orientsee – Here’s how BPGES creates its plaintext content. It hooks to the bp_email_get_property filter https://github.com/boonebgorges/buddypress-group-email-subscription/blob/a3af650c3073cc8fd6d3822ea5cde16be912913d/bp-activity-subscription-functions.php#L804 with the ass_email_convert_html_to_plaintext callback https://github.com/boonebgorges/buddypress-group-email-subscription/blob/a3af650c3073cc8fd6d3822ea5cde16be912913d/bp-activity-subscription-functions.php#L1063

You could hook to bp_email_get_property, either before or after the BPGES function (probably after? say, priority 30), and then do some string manipulation.

If there’s a problem with the way that plaintext is generated – say, we’re too aggressive in deduplicating line breaks (see eg https://github.com/boonebgorges/buddypress-group-email-subscription/blob/a3af650c3073cc8fd6d3822ea5cde16be912913d/html2text.php#L51) – then perhaps its something we might address in BPGES itself.

Hi @orientsee – Sorry for the code-based answer – I wasn’t sure from your question what your level of skill was.

The fact remains that this is not a simple thing to implement. The text of the digest is built programatically, by taking different chunks of text and putting them together in code to create the email content. There’s no human intervention here, and as such there’s no straightforward way to inject additional characters.

I’ll do some testing in the upcoming weeks to figure out whether this is a problem that occurs in a vanilla installation of BPGES. If so, it’s a bug that should be fixed there.