Mail Editor support

any news about this? I would also like to have this option. My use case is that I need to make Hebrew templates with the RTL writing directions.

What exactly is required to support Mail Editor? Is there something that Privatemsg does in a non-standard way that needs to be fixed? Otherwise, based on the Mail Editor maintainer's post, Privatemsg should be compatible.

Look at the mail_edit/modules directory for examples.

Ok, here's a tentative patch that adds a new submodule offering integration based on the logintoboggan example. Let me know if it works for you.

#5: privatemsg-mail-edit-integration-submodule-1878642-5.patch queued for re-testing.

I got the warning then I try to apply patch:

➤ git apply --index privatemsg-mail-edit-integration-submodule-1878642-5.patch
privatemsg-mail-edit-integration-submodule-1878642-5.patch:65: new blank line at EOF.
+
warning: 1 line adds whitespace errors.

+++ b/privatemsg_mail_edit/privatemsg_mail_edit.module
@@ -0,0 +1,46 @@
+function privatemsg_mailkeys() {
...
+function privatemsg_mail_edit_text($mailkey, $language) {
...
+function privatemsg_mail_edit_token_types($mailkey) {

Why do you use hooks from another module? O_o

+++ b/privatemsg_mail_edit/privatemsg_mail_edit.module
@@ -0,0 +1,46 @@
+  if (module_exists('privatemsg')) {

What is the reason to check module? This module is in dependencies.

+++ b/privatemsg_mail_edit/privatemsg_mail_edit.module
@@ -0,0 +1,46 @@
+    return user_mailkeys() + array(
+      'pm_email_notify' => t('Privatemsg e-mail notifications'),
+    );

privatemsg module has 'pm_email_notify' key only.

I guess that this patch will never works.

Ok, I don't really understand how to integrate with Mail Editor then. @mrded Please supply your own patch if you find a way to get it working.

Please, take a look my patch.

Any progress, guys?

12: privatemsg-1878642-12.patch queued for re-testing.

D7 is not yet outdated

Automatically closed because Drupal 7 security and bugfix support has ended as of 5 January 2025. If the issue verifiably applies to later versions, please reopen with details and update the version.