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$SpecializedLiftActor$$processMailbox$1.apply$mcV$sp(LiftActor.scala:182) at net.liftweb.actor.SpecializedLiftActor$$anonfun$net$liftweb$actor$SpecializedLiftActor$$processMailbox$1.apply(LiftActor.scala:182) at net.liftweb.actor.SpecializedLiftActor$$anonfun$net$liftweb$actor$SpecializedLiftActor$$processMailbox$1.apply(LiftActor.scala:182) at net.liftweb.actor.SpecializedLiftActor$class.around(LiftActor.scala:196) at org.apache.esme.actor.HttpSender$.around(HttpSender.scala:38) at net.liftweb.actor.SpecializedLiftActor$class.net$liftweb$actor$SpecializedLiftActor$$processMailbox(LiftActor.scala:181) at net.liftweb.actor.SpecializedLiftActor$$anonfun$2$$anonfun$apply$mcV$sp$1.apply$mcV$sp(LiftActor.scala:145) at net.liftweb.actor.LAScheduler$$anonfun$9$$anon$1$$anon$2.run(LiftActor.scala:51) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) I think I saw something like this on either this list or liftweb list. I'm going to look into this today. Thanks, Eric
