14 Mar
2007
14 Mar
'07
3:58 a.m.
Brad Fuller wrote:
Lukas Renggli wrote:
That's odd. Are you using
Apache? Rewrite rules? Proxies?
Obviously it cannot find the JavaScript files. Locally they should be
reachable at http://localhost:8080/seaside/files/WAStandardFiles/
externalAnchors.js. Does that work?
Yep, it works locally - well not locally but direct and not thru apache
(I had to clear '/' in Server Path in config to be able to navigate
locally. Also, if I bypass apache and have '/' in the Server Path, icons
don't show up.).
I don't think my rewrite rules are anything special. This is my test
setup but I just checked on the other site and it operates the same with
the exact same error.
Here are my rewrite rules:
ProxyPreserveHost On
RewriteEngine ON
RewriteCond /home/web/mmiki/%{REQUEST_FILENAME} !-f
RewriteRule ^/(.*)$ http://localhost:9999/seaside/mmiki/$1 [proxy,last]
I think this is the same problem that I have when seaside times out. I
the path duplicated like: /seaside/miki/seaside/mmiki
Obviously, I've done something wrong with the image (unless you see
something wrong in the rewrite rules)
I think the rewrite rules are ok. I'm seeing this in the apache access log:
"GET /seaside/files/SULibrary/prototype.js HTTP/1.1" 404 82
I don't know why SULibrary is looking externally for the files. I didn't
tell it to do so. Is this the default?
> Ideas where to look?
FireBug is the only answer I know to any problem related to
JavaScript:
http://www.getfirebug.com/
Man, that's handy! In the Script tab it says:
<h1> Error:
"/seaside/mmiki/seaside/files/WAStandardFiles/externalAnchors.js" not
found. </h1>
I don't quite know what this means. Why would it be looking in this
path? (mmiki is the name of the pier kernel)