On Wed, Jan 19, 2011 at 8:39 AM, Richard Hirsch <[email protected]> wrote: > You are right - that is the same issue. We forgot to create a ticket > for lift, so the problem was never corrected. > > Could you create a ticket in lift for this issue? This will solve the > problem in the long-term. A short-term solution is probably to > reinsert the character strings. >
Done https://www.assembla.com/spaces/liftweb/tickets/855-non-scoped-localized-strings Thanks, Eric > On Wed, Jan 19, 2011 at 3:34 PM, ejc <[email protected]> wrote: >> Does the e-mail thread I referenced relate to this? If so, I don't >> see that anyone submitted a >> ticket for lift, as David suggested, but the S.? in that case was removed. >> >> Thanks, >> Eric >> >> >> On Wed, Jan 19, 2011 at 6:53 AM, Richard Hirsch <[email protected]> >> wrote: >>> I just had a quick look at the Sendmail problem: >>> >>> The problem is here: >>> >>> Mailer.sendMail(From(S.?("custom_mail_from_adress")), >>> Subject(S.?("custom_mail_subject")), >>> To(who), body) >>> >>> I've updated the Jira issue accordingly. >>> >>> The easiest solution would be to put the strings back in. But it would >>> be better to find a way to allow the user configure these values via >>> property file. >>> >>> D. >>> >>> >>> >>> On Wed, Jan 19, 2011 at 1:37 PM, ejc <[email protected]> wrote: >>>> I can at least do some more research to pinpoint the problems. If >>>> anyone else says "oh I know that answer" feel free to jump in, >>>> otherwise I'll take them. >>>> >>>> Thanks, >>>> Eric >>>> >>>> On Wednesday, January 19, 2011, Ethan Jewett <[email protected]> wrote: >>>>> Thanks a lot! I've put these both in the "Backlog" for now, but if we >>>>> can get them fixed for the 1.2 release then I think we'll all agree to >>>>> include them. >>>>> >>>>> Are you planning on looking into the problem more or are these open >>>>> for someone else to work on? >>>>> >>>>> Ethan >>>>> >>>>> On Tue, Jan 18, 2011 at 7:22 PM, ejc <[email protected]> wrote: >>>>>> On Tue, Jan 18, 2011 at 11:04 AM, Ethan Jewett <[email protected]> >>>>>> wrote: >>>>>>> Hi Eric, >>>>>>> >>>>>>> These both look like bugs. Thanks for the effort on your >>>>>>> investigations. Would you be able to create Jira issues at >>>>>>> https://issues.apache.org/jira/browse/ESME ? >>>>>>> >>>>>>> Thanks, >>>>>>> Ethan >>>>>> >>>>>> Sure thing >>>>>> >>>>>> https://issues.apache.org/jira/browse/ESME-324 -- login message >>>>>> https://issues.apache.org/jira/browse/ESME-325 -- mailto: failure >>>>>> >>>>>> Thanks, >>>>>> Eric >>>>>> >>>>>> >>>>>>> On Tue, Jan 18, 2011 at 5:33 PM, ejc <[email protected]> >>>>>>> wrote: >>>>>>>> On Tue, Jan 18, 2011 at 9:14 AM, Richard Hirsch >>>>>>>> <[email protected]> wrote: >>>>>>>>> On Tue, Jan 18, 2011 at 3:55 PM, ejc <[email protected]> >>>>>>>>> wrote: >>>>>>>>>> I now have actions working on my installation. There were a couple >>>>>>>>>> of >>>>>>>>>> things I ran into. >>>>>>>>>> The login message doesn't seem to be generated unless I log in via >>>>>>>>>> openID, hence my >>>>>>>>>> confusion about login messages. >>>>>>>>> >>>>>>>>> Try and login as a normal user and then set the open-id url via the >>>>>>>>> user profile. >>>>>>>> >>>>>>>> It is set, and login via open-id works fine and generates the login >>>>>>>> message. Logging >>>>>>>> in via username/password works, but doesn't generate login message. I >>>>>>>> don't see >>>>>>>> any errors, just no login message. >>>>>>>> >>>>>>>>> The mailto: action doesn't appear to >>>>>>>>>> work, either on >>>>>>>>>> stax, or locally. I plan to debug this today. I probably have >>>>>>>>>> something mis-configured. >>>>>>>>> >>>>>>>>> Haven't tried that in a while. I just looked at the stax log and I >>>>>>>>> didn't find any exceptions. >>>>>>>>> >>>>>>>>> Are you using the correct action syntax? >>>>>>>>> "mailto:[email protected]"; >>>>>>>> >>>>>>>> Yes, I've noticed it will not accept incorrect syntax (including a >>>>>>>> space between : and email address) >>>>>>>> I get the following when I try a mailto: action. This is running >>>>>>>> from sbt: >>>>>>>> >>>>>>>> ERROR - Actor threw an exception >>>>>>>> java.lang.IllegalStateException: Attempted to use resource bundles >>>>>>>> outside of an initialized S scope. S only usable when initialized, >>>>>>>> such as during request processing. Did you call S.? from Boot? >>>>>>>> at net.liftweb.http.S$.resourceBundles(S.scala:722) >>>>>>>> at net.liftweb.http.S$.$qmark(S.scala:748) >>>>>>>> at >>>>>>>> org.apache.esme.actor.HttpSender$.org$apache$esme$actor$HttpSender$$send(HttpSender.scala:58) >>>>>>>> at >>>>>>>> org.apache.esme.actor.HttpSender$$anonfun$messageHandler$1.apply(HttpSender.scala:41) >>>>>>>> at >>>>>>>> org.apache.esme.actor.HttpSender$$anonfun$messageHandler$1.apply(HttpSender.scala:39) >>>>>>>> at >>>>>>>> net.liftweb.actor.LiftActor$class.execTranslate(LiftActor.scala:371) >>>>>>>> at >>>>>>>> org.apache.esme.actor.HttpSender$.execTranslate(HttpSender.scala:38) >>>>>>>> at >>>>>>>> net.liftweb.actor.SpecializedLiftActor$class.net$liftweb$actor$SpecializedLiftActor$$proc2(LiftActor.scala:261) >>>>>>>> at >>>>>>>> net.liftweb.actor.SpecializedLiftActor$$anonfun$net$liftweb$actor$SpecializedLiftA >>>> >>> >> >
