Closed (fixed)
Project:
ecard
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
28 Sep 2011 at 19:43 UTC
Updated:
5 Nov 2011 at 23:30 UTC
Both the notification and confirmation emails contain just the first character of the default messages.
Comments
Comment #1
kars-t commentedI know this bug and thought I already fixed it. Could you please check if you have the latest version and if that not helps if ecard.mai.inc line 57 looks like this:
Comment #2
fultonchain commentedYes, they are the same. This is what I have on line 57:
Comment #3
kars-t commentedOkay thanks for confirming this.
Comment #4
kars-t commentedI finally found some time. I can't reproduce this and it currently doesn't make much sense to me. This did occure because the theme() function expects an array as parameter. If I give a string and use that as array the result will be the first character from the array.
If you please could tell me how you did configure E-Card maybe I can reproduce this. Otherwise we have to wait for the simpletest and see if that uncovers some bugs.
Comment #5
fultonchain commentedThanks for the time you've spent on this.
I'm not sure what configuration info I can provide but I have created an administrator account for you. You are more than welcome, as time allows, to look things over for yourself.
Comment #6
jsloan commentedI encountered the same error with a fresh install of 7.8 using the 7.x-1.x-dev(2011-Sep-28) release of ecard using all the defaults.
In ecard.mail.inc I discovered that the
$paramsentity object passed tofunction ecard_mail()did not have an array element named['value'].$params['ecard']->mail['letter']['ecard_letter']is as far as it goes.When I removed reference to it on lines 58, 63, 68 the email messages were fine.
Also, there was a typo in ecard.module in the
function _ecard_copy()as the token[ecard:card_url]should be[ecard:ecard_url]thanks
jim
Comment #7
fultonchain commentedJsloan, thanks so much!
That seems to have done the trick.
Comment #8
kars-t commentedOkay I thought I did test that and will test it again asap.
Comment #9
kars-t commentedFixed the typo. But I still do not understand why my local drupal seems to behave differently...
Comment #10
kars-t commentedWeird weird weird. Now as I did save the field again I suddenly could reproduce and verify the bug. And than I removed ['value'] just as suggested. Now it works... submitted to dev.
Comment #11
fultonchain commented+1