Closed (works as designed)
Project:
Mass Contact
Version:
6.x-1.x-dev
Component:
User interface
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
7 Oct 2010 at 05:02 UTC
Updated:
22 Aug 2013 at 00:51 UTC
Jump to comment: Most recent file
Comments
Comment #1
oadaeh commentedI don't use it myself, but I will look into it. Which one are you using?
I'm not sure I understand you here. Are you saying that you would like to be able to have WYSIWYG integration in the admin configuration pages where you can define the prepended and appended text? If so, then that should depend on the configuration of the module you are using, but the above might be affecting the admin area, also. If not, please restate what it is you are trying to tell me.
Comment #2
oadaeh commentedThis should be fixed here: http://drupal.org/cvs?commit=433560.
If not, please reopen with more information.
Comment #3
polskikrol commentedThis is exactly what I was referring to. However, looks like this also needs to be 'fixed' for the email composition text box as well (Message). Reopening as 'needs work'.
Comment #4
oadaeh commentedIf you expect me to fix anything, you're going to need to give me some information. I did say to "reopen with more information".
What exactly needs to be "fixed"? What exactly isn't working as you expect it? How do you expect it to work? How is it working for you now? Those are examples of questions you could answer. You could add more, if you think there is anything relevant to add.
It was working for me when I posted the code, so you need to be more specific and detailed so I know what you're referring to.
Also, it would help me if you told me which WYSIWYG module(s) you're using. I tested all three text fields with all the editor options available in the WYSIWYG module, except for the markItUp editor, which WYSIWYG did not detect.
Comment #5
polskikrol commentedLooking at this closely, realize that there is now an option to set the Input type for both the header/footer and HTML of the email. Set the HTML option to Full HTML and waiting for caches to clear to see if I get the wysiwyg integration as expected.
Mass Contact: 6.x-1.x-dev (2010-Oct-08)
WYSIWYG: 6.x-2.4
Editor: TinyMCE 3.3.4
Apologies for lack of information previously.
Comment #6
polskikrol commentedAlright, see the following text...
The message will be sent as HTML, using the Full HTML input format. More information about what is available is on the Compose tips page.
However, the WYSIWYG editor does not kick in. Please see screenshot.
Please note, it works fine for the header and footer with input filter set to Full HTML.
Comment #7
oadaeh commentedYour settings in the "HTML Settings" fieldset of the admin/build/mass_contact/settings/body page are set thusly:
"Send as HTML by default" is checked.
"Allow sender to override HTML setting." is not checked.
"Input format" is set to "Full HTML"
"Allow sender to override input filter setting." is not checked.
"Check HTML markup." is or is not checked and isn't of any importance in this matter, so it doesn't really matter what it's set to.
Set the last "Input format" on that page to "TinyMCE 3.3.4" and remove the check for the "Allow sender to override input filter setting." setting. That should fix your problem until I can resolve the code issues.
There are two problems: 1) you have selected the wrong input format for the HTML settings, and 2) I do not correctly apply the chosen input format when the admin does not allow the sender to change the input format.
It works fine as long as you allow the sender to select the input format, so I'll have to figure out what I'm doing wrong at that point.
(Also, the "needs work" setting is for when there is a patch attached to the issue. Since there is not, I'm resetting it back to "active".)
Comment #8
anonymous07 commentedSubscribe
Comment #9
polskikrol commentedCorrect, checking 'Allow sender to override input filter setting.' resolved the issue. Any idea why this setting would cause the issue?
Comment #10
ezeedub commentedSubscribe
Comment #11
jeffschulerThough not an ideal solution, the steps in #7 resolved this for me. Thanks!
Comment #12
oadaeh commentedClosing old issues.