| Has anyone gotten the Mailer Behavior to work on dreamhost? I am trying to get an app up and running there and it is important that the forms work. Right now, I just have a "protected method `get_class_name' called for #" error. I am on a pretty tight schedule so any help would be appreciated...
Keith Bingman On Aug 25, 2006, at 8:22 PM, Adrian Madrid wrote: Guido,
Mailer does not work for me. On the logging I always use:
RAILS_DEFAULT_LOGGER.debug "xyz"
That always work on rails. I still can't get it to redirect and using that logger I can say that the process method never gets called in my behavior.
Sincerely,
Adrian Madrid
On 8/25/06, Guido Sohne <[EMAIL PROTECTED]> wrote: On 8/16/06, Adrian Madrid <[EMAIL PROTECTED]> wrote:
> The only real problem I faced was that I could not get the behavior to
> respect process() (it would not run by any means). So I moved to using a
> before filter to process the POST but I still cannot redirect after
> processing. I'm sure I am missing something but the original Mailer bahavior
> would not send emails either or bark about it. BTW, I'm running this on
> 0.5.2 unpacked. For me redirecting sometimes is a requirement so if anybody
> has any ideas on why it is not working please let me know.
I have run in to the same issue (Mailer not sending mail, or not
redirecting to thank you page). I have stopped using it for now (until
I have time to take care of that - I want to also build feedback into
my 404 page, so people can tell me about broken links with just a
click or so.).
I had trouble too with getting filters to run. In the end,
process(request, response) did the trick, whereas the other's just
refused to do anything. I wonder why.
How do people debug the behaviors, especially when it is running as a
plugin? I didn't find a logger object to use within the behavior
(maybe there is one, who knows?), Doing print statements only works
inside the test runs, and not under tail -f development.log, or even
the Webrick screen. I had some serious time burnt due to this, until I
resorted to using ./script/breakpointer. Sometimes too, you get an
error message trapped nicely for you by Radiant and you just want to
know what line caused it, but it's not so easy as it could be.
What's the secret sauce? And does Mailer work for everyone, except maybe me? :-)
-- G.
_______________________________________________
Radiant mailing list
[email protected]
http://lists.radiantcms.org/mailman/listinfo/radiant
--
Adrian Esteban Madrid_______________________________________________ Radiant mailing list |
_______________________________________________
Radiant mailing list
[email protected]
http://lists.radiantcms.org/mailman/listinfo/radiant
