See the Attached file for messaging support for features which can store messaging template parts in code for each sending method. The nature of the messaging module means we don't want to write into the messaging API itself but merely check the existing database config and if its different to our feature code, change it.
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | messaging-features_exportables_messaging_store-800614-4-D6.patch | 2.31 KB | christianchristensen |
| messaging.features.patch | 2.01 KB | josh waihi |
Comments
Comment #1
Grayside commentedContrib modules generally support their own Features integration. Sending over to the Messaging queue.
Comment #2
Crom commentedJosh, great patch - thanks!
I've tested this on messaging 6.x-2.4 and can confirm it works.
The only trouble I had was that I needed to revert the feature with the message templates included, following activation. It appeared as overriden initially. Once done, sorted!
Thanks again,
Crom
Comment #3
Remon commentedWhat is holding this back? RTBC? should it be marked as a dupe to #678902: Make message templates exportable?
Comment #4
christianchristensen commentedUpdating this issue to target a specific version (2.4) and a drush make friendly patch.
Comment #5
christianchristensen commentedI would agree that this is a duplicate...