[Seaside] Making generated links more understandable
mac.hive at me.com
Tue Mar 27 12:53:25 UTC 2012
On Mar 26, 2012, at 1:06 PM, Lawrence Kellogg wrote:
> Thanks Lukas and Phillipe.
> It looks like this:
> updateUrl: aUrl
> super updateUrl: aUrl.
> aUrl addToPath: self class name
> will give me what I want. What do you think? Any drawbacks to doing this?
I'll respond to my own question. ;-) Well, the above change works ok in my local environment with Pharo, but when I apply this change to my GLASS instance, all of my CSS and images do not get served. Does this change somehow effect how Seaside with an nginx front-end finds resources in the /var/www/glass directory? I'm not sure what is going on…
> On Mar 26, 2012, at 11:41 AM, Lukas Renggli wrote:
>> Hi Larry,
>> See this FAQ entry: http://www.seaside.st/documentation/faq/how-to#229642197.
>> Then you can use #updateUrl: and #addToPath: to generate path segments
>> that are picked up by GA
>> For pure AJAX applications a slight different approach is needed. That
>> is, everything is done programmatically. Have a look at
>> TextLint-Seaside (http://www.squeaksource.com/textlint) for an
>> On 26 March 2012 17:33, Lawrence Kellogg <mac.hive at me.com> wrote:
>>> I am running Google analytics on my site and the page information is
>>> useless because it just shows the generated links which do not bear any
>>> relationship to the components being called. I thought I read about some way
>>> to name all of the pages but I can't seem to find that information. Is it
>>> possible for me to name all of my pages so that I can see where users are
>>> going on my site?
>>> seaside mailing list
>>> seaside at lists.squeakfoundation.org
>> Lukas Renggli
>> seaside mailing list
>> seaside at lists.squeakfoundation.org
> seaside mailing list
> seaside at lists.squeakfoundation.org
More information about the seaside