I updated from the TinyMCE module using TinyMCE 3x from Moxiecode.....and was dismayed when I went to crank up a new Newsletter issue...and all I could see was the HTML code from the Headers and footers I'd already entered.
But there was no Rich-Text editor available...but the "Input Format" dropdown was available that allowed me to select All of my Input Options.
After much searching I happend upon this posting here http://drupal.org/node/358316 and then opened up the simplenews_template_settings.inc and realized that it does not follow the guidelines in that post.
I'm sure I'm not alone so here are the changes I instituted to make it work....the key is in keeping the quotes as " and not ' in the right places.
I changed
$form['simplenews_template']['simplenews_template_header']["simplenews_template_header_$tid"] = array(
to
<code>$form['simplenews_template']['simplenews_template_header']["simplenews_template_header_$tid"]["simplenews_template_header_$tid"] = array(
And then under the actual header input format on line 55 I had rewrote how the array displays from
$form['simplenews_template']['simplenews_template_header']['simplenews_template_header_format_$tid'] = filter_form(simplenews_template_header_format($tid), 1, array("simplenews_template_header_format_$tid")).
To This
$form['simplenews_template']['simplenews_template_header']["simplenews_template_header_$tid"]['format'] = filter_form(3, NULL, array('simplenews_template_simplenews_template_header_simplenews_template_header_$tid_format'));
I replicated the same techniques for the footer sections as well. So far all seems to be working.
Three Things here:
1. Note the replication of the double " in both areas where the _header_$tid fields are specified.
2. Unlike the aforementioned example at http://drupal.org/node/358316 we were dealing with nested elements...so that all 3 of the fields had to be identified for the format to work.
3. The actual number "3" in my example denotes the 3rd radio button or 3rd input filter selection (which is my default) in this case full html.
I'd submit that making Simplenews Template compatible with the WYSIWYG module for us 5x users without access to all the fancy-shmancy FAPI stuff in D6 would be most helpful.
Comment | File | Size | Author |
---|---|---|---|
#6 | 531960.patch | 1.16 KB | lavamind |
Comments
Comment #1
sunSorry, but for 5.x, this probably won't fix, because that would be larger API change (i.e. any third-party or custom code relying on the current form structure of 5.x will break).
Comment #2
roball CreditAttribution: roball commenteddavedickens, could you please attach a patch against simplenews 6.x-2.x-dev?
Comment #3
muschpusch CreditAttribution: muschpusch commentedsubscribe
Comment #4
geerlingguy CreditAttribution: geerlingguy commentedSub.
Comment #5
franzCan anyone post a patch of these changes?
Comment #6
lavamind CreditAttribution: lavamind commentedHere's a patch that seems to fix the problem.
Comment #7
TajinderSingh CreditAttribution: TajinderSingh commented@lavamind
Thanks... it really fixes the issue.