13 Mar
2007
13 Mar
'07
9:02 p.m.
Is it possible to place javascript in a pier page?
--
brad fuller
http://www.Sonaural.com/
+1 (408) 799-6124
13 Mar
13 Mar
9:15 p.m.
Is it possible to place javascript in a pier page?
Certainly, you can put any HTML into a page:
<div onClick="new Effect.Shake(this)">Click Me</div>
For example this wiki-line should shake the text when you click it
(you need to have the Scriptaculous libraries loaded).
Cheers,
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
9:34 p.m.
Lukas Renggli wrote:
I have the Scriptaculous library loaded, but this does nothing in a Pier
page. I wonder if this is the same issue I had with search: if I load
the scriptaculous library the search component does not work. If I
unload it, it does work.
Ideas where to look?
--
brad fuller
http://www.Sonaural.com/
+1 (408) 799-6124
Is it possible
to place javascript in a pier page?
Certainly, you can put any HTML into a page:
<div onClick="new Effect.Shake(this)">Click Me</div>
For example this wiki-line should shake the text when you click it
(you need to have the Scriptaculous libraries loaded).
10:01 p.m.
Brad Fuller wrote:
Lukas Renggli wrote:
I have the Scriptaculous library loaded, but this does nothing in a Pier
page. I wonder if this is the same issue I had with search: if I load
the scriptaculous library the search component does not work. If I
unload it, it does work.
Ideas where to look?
BTW: The scriptaculous tests all work from the dispatcher. So, I would
think it's something to do with Pier and javascript.
--
brad fuller
http://www.Sonaural.com/
+1 (408) 799-6124
Is it
possible to place javascript in a pier page?
Certainly, you can put any HTML into a
page:
<div onClick="new Effect.Shake(this)">Click Me</div>
For example this wiki-line should shake the text when you click it
(you need to have the Scriptaculous libraries loaded).
10:47 p.m.
Is it possible to place javascript in a pier page?
Certainly, you can put any HTML into a page:
<div onClick="new Effect.Shake(this)">Click Me</div>
For example this wiki-line should shake the text when you click it
(you need to have the Scriptaculous libraries loaded).
11:02 p.m.
Lukas Renggli wrote:
I have the Scriptaculous
library loaded, but this does nothing in a
Pier
page. I wonder if this is the same issue I had with search: if I load
the scriptaculous library the search component does not work. If I
unload it, it does work.
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)
Is it possible
to place javascript in a pier page?
Certainly, you can put any HTML into a page:
<div onClick="new Effect.Shake(this)">Click Me</div>
For example this wiki-line should shake the text when you click it
(you need to have the Scriptaculous libraries loaded).
11:09 p.m.
Ideas where to look?
FireBug is the only answer I know to any problem related to
JavaScript:
http://www.getfirebug.com/
11:29 p.m.
Lukas Renggli wrote:
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)
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)
Ideas where to
look?
FireBug is the only answer I know to any problem related to
JavaScript:
http://www.getfirebug.com/
14 Mar
14 Mar
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)
15 Mar
15 Mar
4:13 a.m.
Brad Fuller wrote:
Brad Fuller wrote:
Ok, so I don't get it. Why would apache look for these files? These
javascripts are in the image. In fact, all I have is css in my own
library. Is this something about the back and forth of rewrite rules
that I don't understand?
Someone know?
--
brad fuller
http://www.Sonaural.com/
+1 (408) 799-6124
Lukas Renggli wrote:
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)
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?
8:03 a.m.
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?
4:52 p.m.
Lukas Renggli wrote:
Ok, so I don't get it. Why would apache
look for these files? These
javascripts are in the image. In fact, all I have is css in my own
library. Is this something about the back and forth of rewrite rules
that I don't understand?
Someone know?
Yes it looks to me as if the files do not get rewritten correctly.
Try adding the following line to your rewrite rules:
RewriteRule ^/seaside/files/(.*)$ http://localhost:9999/seaside/
files/$1 [proxy,last]
Make sure it is the first rule to be applied, so that it looks
somehow like:
ProxyPreserveHost On
RewriteEngine On
RewriteRule ^/seaside/files/(.*)$ http://localhost:9999/seaside/
files/$1 [proxy,last]
RewriteCond /home/web/mmiki/%{REQUEST_FILENAME} !-f
RewriteRule ^/(.*)$ http://localhost:9999/seaside/mmiki/$1
[proxy,last]
Thanks Lukas. I'm learning more about rewrite rules than I ever wanted
to! That almost works. It now doesn't accommodate css files served from
apache. Why it worked before, I don't know, but I'll find out. I'm
investigating it now and I'll post my results. Hopefully, others might
find it useful.
--
brad fuller
http://www.Sonaural.com/
+1 (408) 799-6124
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?
16 Mar
16 Mar
4:42 a.m.
Brad Fuller wrote:
Believe it or not, I worked on this all day. The rewrite rules you have
are correct and work for me... at the end of the day. I do not know why
they didn't work right off the bat. When I tried them and they didn't
work, I tried various other tricks and studied the rewrite rules and
conditions on the apache page and elsewhere. Nothing really worked well.
Then, the seaside image started hanging by the end of the day (don't
know why, I didn't touch it much) and I finally had to just kill it. At
that point I was actually back to where I started but I didn't know I
had re-written the rules back to Lukas's original suggestion! After I
restarted seaside, it just worked. Go figur.... What a day. (hey, I know
more about rewrite rules...)
Now... my next problem is the timeout problem. When the page time's out,
I get an error. At least I think that's the reason. I'll create another
thread for that discussion.
Everyone, thanks for your help!
brad
Yes it looks
to me as if the files do not get rewritten correctly.
Try adding the following line to your rewrite rules:
RewriteRule ^/seaside/files/(.*)$ http://localhost:9999/seaside/
files/$1 [proxy,last]
Make sure it is the first rule to be applied, so that it looks
somehow like:
ProxyPreserveHost On
RewriteEngine On
RewriteRule ^/seaside/files/(.*)$ http://localhost:9999/seaside/
files/$1 [proxy,last]
RewriteCond /home/web/mmiki/%{REQUEST_FILENAME} !-f
RewriteRule ^/(.*)$ http://localhost:9999/seaside/mmiki/$1
[proxy,last]
Thanks Lukas. I'm learning more about rewrite rules than I ever wanted
to! That almost works. It now doesn't accommodate css files served from
apache. Why it worked before, I don't know, but I'll find out. I'm
investigating it now and I'll post my results. Hopefully, others might
find it useful. 
13 Mar
13 Mar
9:23 p.m.
Have a look at:
http://spielverderber.seasidehosting.st/spielwiese
that embeds several JavaScripts components into a page
Philippe
2007/3/13, Brad Fuller <brad(a)sonaural.com>om>:
Is it possible to place javascript in a pier page?
--
brad fuller
http://www.Sonaural.com/
+1 (408) 799-6124
_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
14 Mar
14 Mar
4:13 a.m.
Philippe Marschall wrote:
Have a look at:
http://spielverderber.seasidehosting.st/spielwiese
that embeds several JavaScripts components into a page
simply cool... I gotta figure out how to create javascript modules!
6513
days inactive
6516
days old
14 comments
3 participants
participants (3)
-
Brad Fuller -
Lukas Renggli -
Philippe Marschall