[Seaside] Making generated links more understandable

Lawrence Kellogg mac.hive at me.com
Tue Mar 27 14:47:39 UTC 2012

On Mar 27, 2012, at 10:15 AM, Nick Ager wrote:

>  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…
> Hi Larry,
> I'm struggling to understand what the problem is here. How are you accessing your resources? Are you using relative paths? Other than inspecting the html created looking at the resource paths to understand why Nginx isn't serving them I'm afraid I don't have an idea.

Hello Nick, 
  I am also struggling to understand why everything breaks. My nginx.conf file redirects to /var/www/glass for files that I refer to in my code, so I only put 'picture.jpg' for an image, for instance, or 'bootstrap.css', and it all works great. Would you call that a relative path?

  If I put in that single addToPath line in updateUrl: 

> updateUrl: aUrl
> 	super updateUrl: aUrl.
> 	aUrl addToPath: self class name

  nothing is found. 

  I'm puzzled…..


> Cheers
> Nick
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20120327/4cabac64/attachment.htm

More information about the seaside mailing list