I did a fresh install with the renamed folder, but the public instance
now requires login by default
that's because you copied an author repository to public ? :)
You can configure this from admin pannel, go to configuration ->
server -> secureURIList
and remove "root" if you want an unrestricted access to /*
please note that there are other differences between author and
public configuration so I would rather bootstrap or deploy
webapps as delivered with the magnolia release.
Sameer Charles
Magnolia International Ltd.
------------------------------------------------------------------------
---------
[EMAIL PROTECTED] http://www.magnolia.info
Magnolia® - Simple Enterprise Content Management
------------------------------------------------------------------------
---------
On Jan 4, 2007, at 3:23 PM, Ben Brock wrote:
I did a fresh install with the renamed folder, but the public instance
now requires login by default. I seem to remember running into this
before. Is this a Tomcat configuration change?
Regards,
Ben
-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED]
Sent: 03 January 2007 18:05
To: [email protected]
Subject: Re: [magnolia-user] correct way to mask "magnoliaPublic"
in url
On Jan 3, 2007, at 18:59 , Ben Brock wrote:
Incredible! I can't believe it was as easy as renaming the folder.
I had
to reactivate the pages to change the cached context root paths, but
it worked otherwise. I thought I read that "magnoliaPublic" was
hardcoded into some configurations previously, so I didn't think to
try it.
On the top of my head, the subscriber of the author instance is by
default configured to go to magnoliaPublic but that's obviously
editable, and I assume you've done so ;)
Cheers,
g
-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED]
Sent: 03 January 2007 17:38
To: [email protected]
Subject: Re: [magnolia-user] correct way to mask "magnoliaPublic"
in url
Ben,
That's one correct way to do it, but i would advise to move the
webapp
outside of the webapps directory to avoid that tomcat deploys it
twice; something along the lines of <Context path="/information"
docBase="${catalina.home}/ deployedwebapps/magnoliaPublic"/>
... however, why don't you simply rename the magnoliaPublic war or
directory ?
HTH,
g
On Jan 3, 2007, at 18:32 , Ben Brock wrote:
Hey everyone.
In order to use www.mydomain.com/information instead of
www.mydomain.com/magnoliaPubic, I added the following line to my
Tomcat conf/server.xml. If I understood Sameer correctly, this is
incorrect and could cause memory issues. How have others
accomplished
this in Tomcat (not Apache mod_rewrite)?
<Context path="/information" docBase="magnoliaPublic"
allowLinking="true"/>
Thanks in advance,
Ben Brock
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
