Hi Will,
incidentally I've done the same today and ran into the same problem.
Flushing the cache on a server solved the problem.
I think what happens is following:
Key for the cache entry is the url without webapp context, after you
change the webapp context and restart the server, incoming request is
compared against the key which is the same, file is not modified so the
cache entry is served. And of course the entry in the cache contains
links with the context name in them hence the 404 you see.

HTH,
Jan

On Mon, 2008-10-13 at 09:26 +0200, Will Scheidegger wrote:
> Dear Magnolians
> 
> I've setup a Mag 3.6.3 magnoliaAuthor instance and published the  
> content from a 3.6.1 author instance named "cms" to it. Afterwards I  
> renamed the "magnoliaAuthor" instance to "cms" and the old "cms"  
> instance to "magnoliaAuthor". Everything seemed to work fine... until  
> I turned of the old "magnoliaAuthor" instance. Now I got a 404 in the  
> content area of AdminCentral of the new "cms" instance. When I tried  
> to figure out what the problem was, I noted that the "cms" instance  
> was trying to load the content from the "magnoliaAuthor" instance. So...
> 
> -> Does Magnolia now store the context path it was bootstraped with  
> somewhere?
> -> Is this related to the fix of this bug:
>       http://jira.magnolia.info/browse/MAGNOLIA-2064
> 
> Thanks for the help!
> 
> Regards,
> Will
> 
> ----------------------------------------------------------------
> for list details see
> http://documentation.magnolia.info/
> ----------------------------------------------------------------
-- 
Best regards,

Jan Haderka
Magnolia International Ltd.

----------------------------------------------------------------------
[EMAIL PROTECTED]                  http://www.magnolia.info
Magnolia®  - Simple Open Source Content Management
----------------------------------------------------------------------


----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------

Reply via email to