7 Mar
2006
7 Mar
'06
8:44 p.m.
Hi
I made an image with Pier as the default application
(http://cdrick.seasidehosting.st) but when I want to access component I
have a problem because it tries to access them via another path...
cdrick.seasidehosting.st/mini-calendar instead of
.../seaside/mini-calendar
I change the default application after having made the image...
nevertheless, it's also impossible to add new pages, component and so
on... Is it because I made the image before changing the default path ?
Also I noticed there isn't the remove command ... How to remove an
existing structure ?
See you
Cédrick
*//*
--------------------------------
L'ENIT vous invite a sa journee portes ouvertes le 17 mars 2006 de 13h30 a 19h30
Enit , 47 avenue d'Azereix 65000 Tarbes
Bus N°1, arret ENI
7 Mar
7 Mar
9:43 p.m.
Hi Cédrick,
I made an image with Pier as the default application
(http://
cdrick.seasidehosting.st) but when I want to access component I
have a problem because it tries to access them via another path...
cdrick.seasidehosting.st/mini-calendar instead of .../seaside/
mini-calendar
Looks cool ;-)
Yes, this is a known problem of Seaside, making it impossible to
strip of the parts of the path not ment for Pier. The problem is,
that the WAApplication doesn't know how it is nested into
WADispatcher, and in your case this is not the same as the base-path.
You seem not to have loaded the latest code of Pier. In there there
is a ugly hack, fixing this particular problem by looking at the path
and trying to strip-off /seaside/pier if this makes sense. Well, only
a temporary solution, but it should solve your problem
Also I noticed there isn't the remove command ...
How to remove an
existing structure ?
I don't see any commands on your Pier instance? Did you install a
Security plugin? Else you can always delete a page by sending an URL
of the following form: "/mypage?command=PRRemoveCommand". This should
show clearly how important it is to properly setup one of the
available security frameworks for all public accessible pier sites ;-)
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
8 Mar
8 Mar
10:14 a.m.
Looks cool ;-)
Yes, this is a known problem of Seaside, making it impossible to
strip of the parts of the path not ment for Pier. The problem is,
that the WAApplication doesn't know how it is nested into
WADispatcher, and in your case this is not the same as the base-path.
You seem not to have loaded the latest code of Pier. In there there
is a ugly hack, fixing this particular problem by looking at the path
and trying to strip-off /seaside/pier if this makes sense. Well, only
a temporary solution, but it should solve your problem
uhmm I thought I had the latest one... what's funny is it work for
WACalendar in the environment and not in the content panel. Anyway, I'll
check or I'll provide the full web adress as I did for some to avoid to
load all scripts and style sheets for the ajax demos. That makes me ask
you if we have to load all of them in the main pier configuration if
needed in child components ?
Also I noticed there isn't the remove command
... How to remove an
existing structure ?
I don't see any commands on your Pier instance? Did you install a
Security plugin? Else you can always delete a page by sending an URL
of the following form: "/mypage?command=PRRemoveCommand". This should
show clearly how important it is to properly setup one of the
available security frameworks for all public accessible pier sites ;-)
6618
days inactive
6619
days old
2 comments
2 participants
participants (2)
-
Cédrick Béler -
Lukas Renggli