I dont think that Magnolia stores the "contextPath". The "contextPath" is the webapp-name and u can change it if u want to. I did this in the past and had no problems, but i guess it was in 3.5.
I dont know where the behaviour you described comes from... Maybe somebody else can give a hint? regards rainer PS. Do you / Did you use an Apache in your environment? Magnolia - User mailing list 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/ > ---------------------------------------------------------------- > > -- View this message in context: http://www.nabble.com/Mag-3.6.3%3A-context-path-stored-somewhere--tp19949963p19954707.html Sent from the Magnolia - User mailing list archive at Nabble.com. ---------------------------------------------------------------- for list details see http://documentation.magnolia.info/ ----------------------------------------------------------------
