Marius,

David was able to help me out.  In the future, I will have to dig
myself out of the situation.  For those Lift developers that are not
'committers' it is harder to know how to proceed.  Perhaps in the
future,  the breaking changes should include a little more detail on
which signatures have been changed and how they can be transformed.

In any case, I am happy there is this group to ask for help!

Thanks.


Dan

On Dec 15, 12:08 am, Marius <marius.dan...@gmail.com> wrote:
> Sorry Dan ... There were too many changes  in LiftRules. You should be
> able to determine real quick what changed in LiftRules since the
> variables naming is more or less the same.
>
> If you can not fix your code can you please copy-paste it here ? ...
> in this way I may be able to help.
>
> Br's,
> Marius
>
> On Dec 15, 1:55 am, Dano <dan_ole...@yahoo.com> wrote:
>
> > Marius,
>
> > Is there someway you can communicate what the 'from' and 'to' changes
> > are so that I can have a chance at being able to fix my now broken
> > code?
>
> > Dan
>
> > On Dec 13, 12:31 pm, Marius <marius.dan...@gmail.com> wrote:
>
> > > All,
>
> > > I committed a bunch of changes inLiftRules. In a previous thread
> > > Jorge suggested the abstraction ofLiftRulesvariables. Lists of
> > > functions are now abstracted by RulesSeq trait, which contains prepend
> > > and append functions. Note that if you're calling prepend/append
> > > functions after boot they will throw an exception. If there are
> > > compelling reasons not to do this please let us know. This is just a
> > > mechanism to enforce the use of these functions on startup.
>
> > > Br's,
> > > Marius
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Lift" group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to