A recent update added the Allow Lava block setting to Communication Entry, and defaults it to No. This caused us some headaches as emails were sent out to congregants using the usual templates, but all of the lava codes had been stripped from the text and broke the links.
This block should warn the user and/or prevent them from attempting to send an email with Lava in it if the Allow Lava setting is No, rather than just stripping out the Lava without any notification that it will happen. Many non-technical users select email templates that include Lava.
I would also suggest the default be changed to True for this setting, or add a migration to update all existing instances of the block, as this setting silently changed some important functionality.