The /1 is the web app context. Change it to ../ breaks it on the pages that were working before.
One thing I noticed is that if I deploy this to a server which has mod_proxy set up to hide the /1 it seems to work fine. j On Dec 3, 2007 4:10 AM, Johan Compagner <[EMAIL PROTECTED]> wrote: > and /1/ is your servlyet path? > what happens if you put "../css/style.css" in your markup? > > Because from the normal page that is the css you want i guess? > > johan > > > > On Dec 2, 2007 11:08 PM, Jeremy Levy <[EMAIL PROTECTED]> wrote: > > > I just upgraded to Wicket 1.3, it was remarkably smooth. It took about > 6 > > hours overall. Every single thing was explained very well in the > > migration > > guide and the things i was looking forward to in 1.3 are working > > perfectly. > > > > The only issue I am having is if I have a page this is not mounted as a > > bookmarkable page the relative paths for my stylesheet and other > resources > > are written out incorrect. Below are examples for the same page if I > > mount > > the page versus not. > > > > > > *Bookmarked Page URL (works):* > > http://localhost/1/gettingstarted > > > > <link rel="stylesheet" type="text/css" href="../css/style.css"/> > > > > > > *Nonbookmarked Page URL (doesn't work): > > * > > > > > http://localhost/1/?x=5uwbo6kafiblurBY3bq1UEFwOyXneRheYz2FfwYwMiQAxP5GPHI1HfUHBUhydOCe > > > > <link rel="stylesheet" type="text/css" href="css/style.css"/> > > > > > > *As it's written in my base page html:* > > <link rel="stylesheet" type="text/css" href="css/style.css"/> > > > > Is this something I missed in the migration, or a left over, bug maybe? > > > > Jeremy > > >
