Closed (fixed)
Project:
Token
Version:
6.x-1.x-dev
Component:
Token Actions
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
17 Jul 2009 at 15:13 UTC
Updated:
1 Dec 2010 at 23:00 UTC
Jump to comment: Most recent file
Comments
Comment #1
kenorb commentedCould be related to: #357131: Internal Server Error on adding the comment
Comment #2
kenorb commentedIt's because 'Recipient:' is not required field as in normal 'Send email...' action.
If you leave it empty, it generates Internal Server Error.
Comment #3
kenorb commentedThis could be done by hook_validate as it's done already in system module.
Comment #4
kenorb commentedComment #5
gregglesKenorb - does this fix the issue for you?
Also, I tried to duplicate the steps and couldn't get the error as you describe. Can you clarify the full steps to repeat?
Comment #6
kenorb commentedYes, it solved my issue.
When first I saw this error, I used Workflow.
I've created Workflow, with state 'new'. Added permission to create this state for Anonymous, and then assigned action when specified content is created and when it have a 'new' state, then send tokenized e-mail.
So I started to diagnose the problem, so I've disabled Workflow module and assigned action directly on Node creation, so I still had a problem on submitting this form.
So I edited tokenized e-mail action, and I thought before that if I leave Recipient empty it will be set to my site_mail. But when I set Recipient to some non-empty e-mail then it worked - no error anymore.
I don't know why you can't reproduce it. Try to create two tokenized e-mail actions, I had two of them, but only one was assigned.
Internal Server Error could depends on the server configuration, maybe some other connection or some conflicts between some modules.
Basically the problem was Internal Server Error on submitting content when "Send tokenized e-mail..." action was assigned, and it was solved when I've put some e-mail in Recipient field.
So the question is, if you allow it to be empty, so to what address it will send the e-mail?
Comment #7
kenorb commentedI'll try to reproduce it on the other website and somebody will have similar problem.
Comment #8
gregglesAll I needed was the advice as you gave in #6 to reproduce the error in a very simple way. I don't have time for this right now, but will try to test soon.
Comment #9
dave reidIs this still an issue?
Comment #10
gregglesI imagine it is.
Comment #12
dave reidComment #13
dave reidSimple patch for review.
Comment #14
dave reidNote we just have to do #required => TRUE on the form element itself rather than validation seeing as the recipient may be any token possible.
Comment #15
dave reidCommitted #13 to CVS. Thanks all!
http://drupal.org/cvs?commit=452416