I see the following javascript on each of my pages in my site:
//
I don't think its necessary for what I'm doing, is there a way to turn
off this feature?
Thanks!
- Alex
--
You received this message because you are subscribed to the Google Groups
"Lift" group.
To post to this group, send em
> Are you using any Comet or Ajax or any Lift generated form elements? If you
> are using any of these (anything where Lift is storing a function on the
> server-side and presenting the function as a GUID on the client side), then
> it is strongly advised that you enable GC.
We're not using Comet
Hi David, is there a way to turn off the output of this javascript
code?
On Dec 16, 8:51 am, David Pollak
wrote:
> On Wed, Dec 16, 2009 at 5:47 AM, Alex Black wrote:
> > I see the following javascript on each of my pages in my site:
>
> > //
>
> > I don't think
Hey Dave, great site, beautiful photography.
If you had time you might add some URL rewriting, so that galleries
had nice urls like:
http://briccettiphoto.com/show/galleries/kenya
- Alex
On Dec 13, 1:44 am, Dave Briccetti wrote:
> For a lightning talk at Bay Area Scala Enthusiasts at Twitter H
I found this in another thread:
LiftRules.enableLiftGC = false
On Dec 16, 12:55 pm, Alex Black wrote:
> Hi David, is there a way to turn off the output of this javascript
> code?
>
> On Dec 16, 8:51 am, David Pollak
> wrote:
>
> > On Wed, Dec 16, 2009 at 5:
cool, thanks for the info. We're not using those features yet, so
we'll leave this off for now.
On Dec 16, 4:03 pm, David Pollak
wrote:
> On Wed, Dec 16, 2009 at 5:56 AM, Alex Black wrote:
> > > Are you using any Comet or Ajax or any Lift generated form elements? If
>
ews that web servers should be as
stateless as possible - using state for callbacks doesn't sit well
with me, yet.
- Alex
On Dec 16, 4:35 pm, David Pollak
wrote:
> On Wed, Dec 16, 2009 at 1:30 PM, Alex Black wrote:
> > cool, thanks for the info. We're not using those features y
Can someone point me in the right direction to get tooltips (title
attributes) rendered in my sitemap?
I'd like to add text to each link, so they get rendered like this:
some page
thx
- Alex
--
You received this message because you are subscribed to the Google Groups
"Lift" group.
To post to
s such as
title.
- Alex
> You could add MetaData 'title' by Elem 's method '%'
> some page % ("title" -> "what will happen when you click
> on this
> link")
>
> or use { }
> some page
>
>
>
> On Mon, Dec 21, 2009 at 10:
I've got a large response I'd like to send out, and I'd like to chunk
it up.
http://en.wikipedia.org/wiki/Chunked_transfer_encoding
Does Lift provide any built in support for this?
I've explored using StreamingResponse, but it expects a dataLength,
which I don't have. I had hoped to provide it
Hi David,
Its a huge-ass google sitemap, so I'm forming XML for it, and its
really large, and I thought I'd send chunks of it out at a time rather
than composing all of it in RAM before sending it out.
- Alex
On Dec 22, 5:56 pm, David Pollak
wrote:
> On Tue, Dec 22, 2009 at 2:38 P
That could definitely work.
I'd still (even for curiosity's sake) be interested in lower level
access to the response, e.g. response.write that goes right out to the
client.
On Dec 22, 7:36 pm, David Pollak
wrote:
> On Tue, Dec 22, 2009 at 4:28 PM, Alex Black wrote:
> > Hi
ad of
>
>
>
> On Tue, Dec 22, 2009 at 11:29 AM, Alex Black wrote:
> > Hi Xuefeng,
>
> > I'm using the default Lift Sitemap, so I don't think I can use either
> > of your suggestions, or, I don't see how to use them. The sitemap
> > renders
I've got this xhtml in my template:
Also known as:
with this snippet code:
def alsoKnownAs( xhtml: NodeSeq, product: Product): NodeSeq = {
def list( xhtml: NodeSeq, product: Product): NodeSeq = {
product
.alternateLabels
.flatMap( l =>
I missed a bit of code, probably not relevant, but just in case
someone notices the issue:
def loserAlsoKnownAs( xhtml: NodeSeq ): NodeSeq = {
alsoKnownAs(xhtml, loser)
}
--
You received this message because you are subscribed to the Google Groups
"Lift" group.
To post to this group, se
I've got some xhtml blocks in one of my templates that are basically
identical, and I'd like to avoid the duplication, by either writing
the block once in my template and using a snippet to write it out
twice (with different values) or put it in its own template.
Items
First
Second
Slick, thats perfect, thanks.
On Dec 23, 4:16 pm, Ross Mellgren wrote:
> bind("alsoKnownAs", in, "list" -> { (ns: NodeSeq) => bind("list", ns,
> "label" -> ... ) })
>
> -Ross
>
> On Dec 23, 2009, at 3:59 PM, Alex Black wrote:
ch {
> case Full("first") => loadFirstListOfPoints()
> case Full("second") => loadSecondListOfPoints()
> case _ => error("missing item attribute or has incorrect
> value")
> }
>
> bind(...
=> foobar(item)(ns)
> case _ => error("could not find item -- itemId attribute
> not given or invalid")
> }
> }
>
> def foobar(item: ItemModel)(ns: NodeSeq): NodeSeq =
Yeah that looks like exactly what I'm looking for.
I'm just debating the two options: 1. Use many snippets and pass the
current item down through a request var. 2. Use one snippet (composed
of many internal function calls) and pass the current item down as a
parameter.
I'll give both a shot, tha
I'd like to handle 404s on my site in such a way that:
- there is no redirect, e.g. if you type in a url like mysite.com/
foobarme, you'll stay at that url, so maybe you can correct it
- the status code returned is 404 (not 200 OK)
See stackoverflow:
http://stackoverflow.com/bob
So I tried somet
nk", MyLink("path" :: "to" :: "link" :: Nil, "title
> goes here"), "Some Link", ...))
>
> Thanks, Chris
>
> On Wed, Dec 23, 2009 at 2:25 PM, Alex Black wrote:
> > Hi Xuefeng, I think will produce 1 tooltip for the entiresite
In my effort to handle 404s without a redirect (see
http://groups.google.com/group/liftweb/browse_thread/thread/4a9806a63419644f),
I am wondering if there is a way to add an item at the end of a
sitemap which matches every url?
E.g. Lift would look through the sitemap for a match, and always match
In my snippet I'd like to change the response status code from the
default 200 to something else, say 201, or 404. (see
http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html).
I see there is a method on S to change the doctype, but I don't see
one to change the status code.
Thanks,
- Alex
--
d in homepageTemp1.
This *almost* works for 404 handling, except you still get a 200 OK
response when you would expect a 404. I am hoping there is some
mechanism in lift to let me change the status code to 404 for this
menu.
- Alex
On Dec 29, 11:10 am, Alex Black wrote:
> In my effort to ha
render, but I wasn't able to
use that since I'm still on 1.0, it looks like it was added later. (I
am considering moving to 1.1-M6).
- Alex
>
> Cheers, Tim
>
> On 29 Dec 2009, at 15:23, Alex Black wrote:
>
> > But of course RewriteResponse is not a LiftResponse.
Is M8 pretty stable? A little while back DavidP recommended M6 as being the
most stable of the milestones.
On Tue, Dec 29, 2009 at 1:07 PM, Ross Mellgren wrote:
> Switch to 1.1-M8, if you can.
>
> -Ross
>
> On Dec 29, 2009, at 1:04 PM, Alex Black wrote:
>
> >
> >
this:
val node404 =
Not Found
LiftRules.uriNotFound.prepend {
case (req, _) => XhtmlResponse(S.render(node404, req), _,
headers, cookies, 404, false)
}
>
> Cheers, Tim
>
> On 29 Dec 2009, at 15:23, Alex Black wrote:
>
> > But of course RewriteR
looking at
> > LiftResponse.
>
> > It depends what type of response you want, but at a base level,
> > InMemoryResponse will do what you want... as I said, you need to
> > look at LiftResponse subclasses and find the one that suits your
> > needs.
>
> >
de and
changes the url.
I'd offer to write the new wiki page - is there a way for me to get an
account on that wiki - or is it just for contributors?
- Alex
On Dec 29, 1:20 pm, Alex Black wrote:
> > If you want to display the contents of your 404.html, checkout
> > NodeResponse...
I've changed my sitemap from:
Menu(Loc("index", Pair("index" :: Nil, false), "Home")) ::
to
Menu(Loc("index", Pair("" :: Nil, false), "Home")) ::
So that my "Home" link goes to mysite.com/ instead of mysite.com/
index. But, I notice, when you're at mysite.com/ the sitemap doesn't
show
ponse you want, but at a base level,
> > > InMemoryResponse will do what you want... as I said, you need to
> > > look at LiftResponse subclasses and find the one that suits your
> > > needs.
>
> > > Cheers, Tim
>
> > > On 29 Dec 2009, at 17:07
e
> that code. To put Lift in production mode:
>
> mvn -Drun.mode=production jetty:run
>
> I would strongly recommend against a "catch-all" entry in SiteMap as it will
> expose every page on your site to access.
>
>
>
> On Tue, Dec 29, 2009 at 11:17 AM, Alex Bl
ellgren wrote:
> This is the production run mode thing dpp talked about. Try your app with
> -Drun.mode=production
>
> -Ross
>
> On Dec 29, 2009, at 7:39 PM, Alex Black wrote:
>
> > Thanks for pointing that out, the catch-all sounds dangerous.
>
> > I tried your
On Tue, Dec 29, 2009 at 1:40 PM, Alex Black wrote:
> > Hi Marius, I was trying to find a way to give a custom 404 response
> > without changing the url (e.g. using a redirect) and returning a 404
> > status code.
>
> > Before I found a solution, I found an almost solu
> > I've changed my sitemap from:
>
> > Menu(Loc("index", Pair("index" :: Nil, false), "Home")) ::
>
> Yes, the / directory will be rendered by Lift as /index There's no way
> around that one.
Can you explain? I don't understand. I'm not sure what "rendered"
means in this context, and I'm not
temap contains a number of entries.
On Dec 30, 12:14 am, Alex Black wrote:
> I emailed Ross directly and said I did run with -Drun.mode=production.
>
> Here's what I'm seeing:
> 1. If I run with -Drun.mode=production, and I access a not found url,
> say mysite.com/foobar, t
y (without a redirect, with 404 status code), and processed by
the template engine so it uses our default template with sitemap etc.
- Alex
On Dec 30, 12:22 am, Alex Black wrote:
> One more detail:
>
> notFoundNode is defined like this:
>
> val notFoundNode =
&
new request that has been rewritten
> > to seem as if it were a hit to /
>
> > I'm not sure if this is a good idea, but it seems to work for the site map
> > thing.
>
> > However, I can't find a way to make the head merge work properly. It looks
> > like
Google's opinion:
http://googlewebmastercentral.blogspot.com/2008/08/farewell-to-soft-404s.html
On Dec 30, 10:05 am, Alex Black wrote:
> I'll try out that solution Russ, thanks. Although as the solution
> gets a bit more complex, and taking into account Marius's advice,
101 - 140 of 140 matches
Mail list logo
