Hi Saqib,
I just checked that I have got read/write permission to all those
pages which I am activating. Its looks fine but doesn't work.
What I meant was - Its not an activation error, you are using
magnolia enterprise edition and by default when you activate it
starts a workflow, so its not
related to the permissions you have on the pages you are trying to
activate.
Now, I had a look at the code base and its a bug that workflow
command (EnterpriseFlowDefinitionManager) tries to access
URI /.magnolia/pages/flows.html
without sending proper authentication headers.
To fix:
- Add "/.magnolia/pages/flows" as a string in Config->server-
>filters->cmsFilter->Bypass
Let us know if it works
Regards,
Sameer Charles
Magnolia International Ltd.
------------------------------------------------------------------------
---------
[EMAIL PROTECTED] http://www.magnolia.info
Magnolia® - Simple Enterprise Content Management
------------------------------------------------------------------------
---------
On May 9, 2007, at 12:28 PM, Hussain, S (Saqib) wrote:
Hello Sameer,
I just checked that I have got read/write permission to all those
pages which I am activating. Its looks fine but doesn't work.
Saqib.
-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED]
Sent: 09 May 2007 11:13
To: [email protected]
Subject: Re: [magnolia-user] Page Activate Problem
Hello Sameer,
Is it possible to tell me the solution that what I need to do this
work? Its not me even other members who have the same roles and
groups are not able to activate the page. So, I will thankful to
you if you can suggest any solution/
Thanks.
Saqib.
-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED]
Sent: 09 May 2007 11:05
To: [email protected]
Subject: Re: [magnolia-user] Page Activate Problem
Actually your log says that you dont have permissions on ./
magnolia/ pages/flows.html
Could not set workflow definition url:Server returned HTTP response
code: 403 for URL:
http://intranet2.diamond.ac.uk:80/.magnolia/pages/flows.html?
command=sho
wFlow&flowName=activation
It happend on Author instance before even sending activation
request to the live instance.
Hope this helps
Regards,
Sameer Charles
Magnolia International Ltd.
----------------------------------------------------------------------
--
---------
[EMAIL PROTECTED] http://www.magnolia.info
Magnolia® - Simple Enterprise Content Management
----------------------------------------------------------------------
--
---------
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
