Has a lot of PathNotFound exceptions. Maybe because I never activated
all my template and dialog config - mainly just pages. I didn't try
'including subnodes'. That might be all it needs.

Its not too critical. I don't really use deactivate much. I suspect they
will integrate this as a feature at some point.

Then the control will be bug free, right?

-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, March 29, 2006 12:49 PM
To: [email protected]
Subject: Re: [magnolia-user] Activation Button in mainBar

Don't know what to tell you.  I personally wish there was more effective
logging in the activation to diagnose issues like this.  What do the
logs in the other half get.  I mean if this is the author logs, what
does the public log show?

--David

Robert Van Overmeiren wrote:

>activatePage.jsp is unchanged other than the CSS link tags, and I took 
>"website" out of the call to 'activate'.
>
>It has the code for getting the path param.
>
>If I delete all the code, leaving just '<h1>Activation</h1>' in the 
>body, I still get HTTP 400.
>
>I went into mgnlActivation.js and added '/magnoliaAuthor' to
>'activationWindow.location':
>
>  activationWindow.location =
>"/magnoliaAuthor/.magnolia/activatePage.html?path=" + pageId + 
>"&action=" + actionType;
>
>
>Activation works. Deactivation works. When I re-activate, my content is

>gone. Activating the normal brings it back.
>
>
>
>Got some new log info:
>
>INFO   info.magnolia.cms.security.Lock Lock.java(setSystemLock:80)
>29.03.2006 10:13:41  New System lock created on Wed Mar 29 10:13:41 MST
>2006 )
>INFO   info.magnolia.cms.security.Lock Lock.java(resetSystemLock:89)
>29.03.2006 10:13:41  Resetting system lock created on Wed Mar 29
>10:13:41 MST 2006
>INFO   info.magnolia.cms.exchange.simple.Syndicator
>Syndicator.java(activate:215) 29.03.2006 10:13:41  Exchange : 
>activation request received by 0001
>INFO   info.magnolia.cms.security.Lock Lock.java(setSystemLock:80)
>29.03.2006 10:18:26  New System lock created on Wed Mar 29 10:18:26 MST
>2006 )
>INFO   info.magnolia.cms.security.Lock Lock.java(resetSystemLock:89)
>29.03.2006 10:18:27  Resetting system lock created on Wed Mar 29
>10:18:26 MST 2006
>INFO   info.magnolia.cms.exchange.simple.Syndicator
>Syndicator.java(activate:215) 29.03.2006 10:18:27  Exchange : 
>activation request received by 0001
>INFO   info.magnolia.cms.security.Lock Lock.java(setSystemLock:80)
>29.03.2006 10:19:10  New System lock created on Wed Mar 29 10:19:10 MST
>2006 )
>INFO   info.magnolia.cms.security.Lock Lock.java(resetSystemLock:89)
>29.03.2006 10:19:10  Resetting system lock created on Wed Mar 29 
>10:19:10 MST 2006
>INFO   info.magnolia.cms.exchange.simple.Syndicator
>Syndicator.java(activate:215) 29.03.2006 10:19:10  Exchange : 
>activation request received by 0001
>
>Thx,
>Bob V
>
>-----Original Message-----
>From: [email protected] [mailto:[EMAIL PROTECTED]
>Sent: Wednesday, March 29, 2006 10:01 AM
>To: [email protected]
>Subject: Re: [magnolia-user] Activation Button in mainBar
>
>Hmmm.....  The path attribute is the path to the page to be actived. 
>It's obvious that's being sent to Magnolia. 
>
>Can you post more of activatePage.jsp?  There should be a line above
>
>
>
>----------------------------------------------------------------
>for list details see
>http://www.magnolia.info/en/magnolia/developer.html
>----------------------------------------------------------------
>  
>


--
=======================================
David Smith
Network Operations Supervisor
Department of Entomology
College of Agriculture & Life Sciences
Cornell University
2132 Comstock Hall
Ithaca, NY  14853
Phone: 607.255.9571
Fax: 607.255.0939


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