You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To replicate our content, a 4 eyes workflow is necessary. This also applies to the context aware configurations. For this, we have removed the replication rights from the authors. As far as I can see, this also works for the ca config, because the request for publication workflow
is started automatically. However, if the user simply presses the Publish button without having created or changed a configuration beforehand, a rather ugly error message appears. This is a bit confusing for the users. Especially because the "Request for publication" workflow is still started in the background. I also have the feeling that the publish button was greyed out in previous versions if there was no modification (but maybe I'm wrong).
Not to forget, thank you for these great tools.
The text was updated successfully, but these errors were encountered:
stefanseifert
changed the title
ugly error message appears
Ugly error message appears when using "Quick Publish" for users that do not have replication permission
Mar 24, 2023
To replicate our content, a 4 eyes workflow is necessary. This also applies to the context aware configurations. For this, we have removed the replication rights from the authors. As far as I can see, this also works for the ca config, because the request for publication workflow
is started automatically. However, if the user simply presses the Publish button without having created or changed a configuration beforehand, a rather ugly error message appears. This is a bit confusing for the users. Especially because the "Request for publication" workflow is still started in the background. I also have the feeling that the publish button was greyed out in previous versions if there was no modification (but maybe I'm wrong).
Not to forget, thank you for these great tools.
The text was updated successfully, but these errors were encountered: