On Tue, Apr 20, 2010 at 12:41 PM, Stephen Gallagher <
step...@gallagherhome.com> wrote:
> On 04/20/2010 03:37 PM, Christian Hammond wrote:
>
>> I'm not sure whether mod_wsgi would be somehow different or not.
>> initialize is called in reviewboard/urls.py, which should definitely be
>> invoked reg
On 04/20/2010 03:37 PM, Christian Hammond wrote:
I'm not sure whether mod_wsgi would be somehow different or not.
initialize is called in reviewboard/urls.py, which should definitely
be invoked regardless. If you're seeing the "Log file for Review Board
..." in the log files, then you should be
I'm not sure whether mod_wsgi would be somehow different or not. initialize
is called in reviewboard/urls.py, which should definitely be invoked
regardless. If you're seeing the "Log file for Review Board ..." in the log
files, then you should be seeing signal connections. That is, unless
something
On 04/20/2010 03:31 PM, Christian Hammond wrote:
It shouldn't work for just one or the other. Try running
./contrib/internal/prepare-dev.py.
That connect_signals should be happening on the first request to
Review Board. Are you running this using fastcgi or mod_python?
Might also be worth ch
It shouldn't work for just one or the other. Try running
./contrib/internal/prepare-dev.py.
That connect_signals should be happening on the first request to Review
Board. Are you running this using fastcgi or mod_python?
Might also be worth checking to make sure that the following points are also
On 04/20/2010 02:48 PM, Christian Hammond wrote:
Good question... Can you run the test suite from a source tree and see
if anything fails? (./reviewboard/manage.py test)
Christian
Getting a traceback trying to run the tests. I'm using the
contrib/conf/settings_local.py.tmpl as the settin
Good question... Can you run the test suite from a source tree and see
if anything fails? (./reviewboard/manage.py test)
Christian
On Tuesday, April 20, 2010, Stephen Gallagher wrote:
> On 04/20/2010 11:26 AM, Stephen Gallagher wrote:
>
> Sorry, maybe I was unclear. By putting that log message
On 04/20/2010 11:26 AM, Stephen Gallagher wrote:
Sorry, maybe I was unclear. By putting that log message where Scott
recommended, I proved that send_review_mail() was not being called at
all (the log message never printed). So I'm trying to figure out how
to track down the misconfiguration.
I have some more ideas:
1) Check You can telnet to smtp server from machine where ReviewBoard
works
2) Try to use IP address instead host name
3) Ask someone is this isn't the problem of proxy or DNS server. If
You can telnet to server from command line (in Linux) check You have
not set variable HT
Sorry, maybe I was unclear. By putting that log message where Scott
recommended, I proved that send_review_mail() was not being called at
all (the log message never printed). So I'm trying to figure out how to
track down the misconfiguration.
On 04/20/2010 11:22 AM, Jan Koprowski wrote:
In my
In my case SMTP server doesn't provide TLS authentication but
information about this issue I found in Apache logs without any
problems.
On Apr 20, 5:01 pm, Stephen Gallagher
wrote:
> On 04/19/2010 05:25 PM, Scott Quesnelle wrote:
>
>
>
> > Here is what I did with V 1.0 when I had an email issue,
On 04/19/2010 05:25 PM, Scott Quesnelle wrote:
Here is what I did with V 1.0 when I had an email issue, in
reviewboard/reviews/email.py
In function
def send_review_mail(user, review_request, subject, in_reply_to,
extra_recipients, template_name, context={}):
I added the li
Here is what I did with V 1.0 when I had an email issue, in
reviewboard/reviews/email.py
In function
def send_review_mail(user, review_request, subject, in_reply_to,
extra_recipients, template_name, context={}):
I added the line:
logging.info("Sending e-mail with subject
13 matches
Mail list logo
