[ http://jira.magnolia.info/browse/MAGNOLIA-614?page=all ]
Philipp Bracher resolved MAGNOLIA-614:
--------------------------------------
Fix Version: 3.0 RC1
Resolution: Fixed
> going from edit page to admincentral results in inability to activate content
> -----------------------------------------------------------------------------
>
> Key: MAGNOLIA-614
> URL: http://jira.magnolia.info/browse/MAGNOLIA-614
> Project: magnolia
> Type: Bug
> Components: admininterface
> Versions: 2.1.1
> Environment: FF 1.0.5 on OSX 10.3
> Magnolia 2.1.1 Build: 1665 October 13. 2005
> Reporter: Boris Kraft
> Assignee: Philipp Bracher
> Fix For: 3.0 RC1
> Attachments: dump.snapshot.zip
>
>
> * Browse on the public site to a page
> * change prefix so you can edit the page (e.g. from www to cmsadmin)
> * makes some changes
> * click on admincentral button in main bar
> * try to activate the page
> this results in http error 400 and inability to activate the page
> I have not tested this on newer versions of Magnolia, but did not see it
> documented in jira either.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia.info/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
