okay, now i understand the problem. thats realy a problem for us and we don't know how we can resolve it.
the day starts very bad ;(
thanks for youre help and for youre hint

so long

ingo

Markus Strickler wrote:

Hi Ingo-

yes the activation process works a bit counter intuitive. This has been discussed on this list several times, so you moight find some more info in the archives. Here's a short warpup: Basically Author sends a request to the public instance(s) to activate, then the public instances poll the data from author. Thus your public instances need access to your author instance. I'm not aware of any way around this. If I understand things
correctly, the next major release of Magnolia will change this. Until then, 
you'll probably have to punch a hole through your
firewall to let public through.

HTH,
-markus

-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 05, 2006 8:56 AM
To: [email protected]
Subject: [magnolia-user] activation process

hi together,

the problem yesterday was a incorrect sender url during the activation process. we are behind a firewall with the author instace. so, now some confusing here. why is a correct sender url nesessary if "requestConfirmation" is false? how does the activation process work exactly? is there a work around for activation pages if the author instace is behind a firewall? thx for help yesterday and sorry for stupid questions but the pressure was very high ... ;(

so long

ingo

----------------------------------------------------------------
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
----------------------------------------------------------------

Reply via email to