activation-issue to public-instance with user, versioning
---------------------------------------------------------
Key: MAGNOLIA-3235
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3235
Project: Magnolia
Issue Type: Bug
Affects Versions: 4.3.2
Reporter: Hans Tobler
Assignee: Boris Kraft
User-activation
we have a strange issue and we are not shure if this is because of a wrong
configuration or a magnolia-bug.
We did enable the workflow-module (simply not deployed in pom) in the instance
because it is not used in the project.
When an author on the author-instance activates a page it does not work.
Only if exactly this user is also on the public-instance it works. And the user
on the public must have the same password (so if a user on the author change
his password he can not activate anymore)
I think this is not the normal behaviour, or is it?
Versioning
Another issue is that versioning does not work on the author-instance. There
are no version of the activated page.
The config.server.version is correctly (active=true, and maxVersionIndex=10)
and we have the magnolia-licence from our customer (this should disable the
restriction to more than 1 version, but also then it should work)
Maybe this is also related to the missing workflow?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
