I switched to make sure it wasn't the database.
On Thu, Mar 8, 2012 at 5:49 PM, Dennis Lee Bieber wrote:
> On Thu, 8 Mar 2012 13:59:02 -0500, Scott Macri
> declaimed the following in gmane.comp.python.django.user:
>
>
>> The strange thing is if I manually update the fields in the database
>> wit
I think the issue is that there is some sort of minimum character
limit for the message field in the send_email and send_mass_email
functions. I was not able to find anything in the docs pertaining to
this, but when I use a string like 'test1' the message never gets
sent. When I use something lik
OK, I ran the debugger and here is what I came up with:
-> print "CHECK MESSAGE :"
(Pdb) repr(email_message)
"u'test1'"
(Pdb)
It looks like it is unicode text.
The strange thing is if I manually update the fields in the database
with SQL from the PostGres command prompt the email then works. Th
Nope, I guess that only fixed it for a minute.
On Thu, Mar 8, 2012 at 1:21 PM, Scott Macri wrote:
> I'm very new to python and django. Thanks for the tip. I was trying
> to figure out how to set break points.
>
> I figured out what the problem was.
>
> In views.py I was calling the following fu
I'm very new to python and django. Thanks for the tip. I was trying
to figure out how to set break points.
I figured out what the problem was.
In views.py I was calling the following function to save the data in
the database, which was in a different .py file:
HealthData.saveHealthData(HealthD
On Thu, Mar 8, 2012 at 4:58 PM, Scott Macri wrote:
> I've come to the conclusion that send_mail and send_mass_mail cannot
> be used with sqlite due to a but with the message text.
>
> Attempting to pull a string from the sqlite database and putting it
> into the message field on either of the abov
I've come to the conclusion that send_mail and send_mass_mail cannot
be used with sqlite due to a but with the message text.
Attempting to pull a string from the sqlite database and putting it
into the message field on either of the above mentioned functions
causes the message sending to fail with
UGH, I guess that wasn't the issue. Its back again. I don't know
what the deal is.
On Wed, Mar 7, 2012 at 9:29 PM, Scott Macri wrote:
> I just figured this one out:
>
> Basically in the view I had the following just before calling the save
> method on the database:
> object.email_template = for
I just figured this one out:
Basically in the view I had the following just before calling the save
method on the database:
object.email_template = form.cleaned_data['email_message']
instead of
object.email_message = form.cleaned_data['email_message']
The strange thing is that the data was actua
This one never sends the message:
print object.email_message
some test text
mailer.sendMessage('subject3',object.email_message,user.email,[person.email])
This one works fine:
mailer.sendMessage('subject3','a test message here',user.email,[person.email])
On Wed, Mar 7, 2012 at 9:05 PM, Scott Ma
It appears to be an issue with the content for the message being
pulled from the database. I tried putting the text "text" in the
database, and pulling it out and for some reason it prevents the
message from being sent. The db field is configured as follows:
email_message = models.CharField(max_l
11 matches
Mail list logo
