Are you saying that when you access a page using some GET params, the page renders with those params missing in any embedded links? Some more concrete code/HTML could help clear this up, since I think I'm missing something. There is Helpers.appendParams, but I'm not sure if that's what you're talking about.
Derek On Thu, Mar 26, 2009 at 1:06 PM, Tim Perrett <[email protected]>wrote: > > Guys, > > I have a catalogue of products that essentially have a bunch of meta- > data attached to them and the user can dynamically drill down into to > get a relevant list of products. Because of this query type operation, > im using the query string like so: > > /catalogue?filter=marin > > I know some people don't agree with this, but IMO, its the most REST > approach with the rest of the ROA I have in this application (i.e. > there is no meaningful relationship between the filter options so it > makes no sense to use resource paths) - anyway... to the problem at > hand. > > I have a function def that calculates links etc taking into account > all the various filters and things, and i want a simple "results on a > page" type drop-down select. Now, this is fairly simple as i already > have the function defined to calculate the url and yes, i know i could > calculate the new URL in javascript, but i dont really want to do that > as its two lot of code to maintain. When I write a form with lift and > bind(...) the action="catalogue" with a post so my server side > function bones because the S.params call cant find anything (there are > no longer any params). > > Any ideas on how one could work around this? > > Cheers, Tim > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
