Publish to Remove Live fails with no message to the user when the staging user does not exist on the live site

Description

The way the UI redirects the user after performing an operation doesn't allow error messages to be viewed.

Environment

Any

Activity

Show:

Cynthia WilburnMarch 12, 2012 at 2:12 PM

Reopening to add 6.1.1 CE GA2. Close as Fixed.

Tammy FongFebruary 23, 2012 at 12:51 AM

PASSED Manual Testing using the following steps:

1. Activate staging
2. Create a member with Administrator role
3. Sign in as created member
4. Make changes to the staged site (Add pages/portlets)
5. Publish to live

Reproduce on:
Tomcat 7.0.25 + MySQL 5. 6.1.x GIT ID: 23e8e46a9e3221ae8e14609bacdb5b0da0d61fb0.

Member created during staging can publish changes to live successfully but the changes are not seen in the live pages.

Fixed on:
Tomcat 7.0.25 + MySQL 5. 6.1.x GIT ID: 54a4346e9e0b170721cbb60b3f81d03f85912b40.
Tomcat 7.0.25 + MySQL 5. 6.2.x GIT ID: d6f0e2abb8add5eeb20551d5b24a2dbd070036a4.

Member created during staging can publish changes to live successfully and the changes can be seen in the live pages.

Michael SaechangJanuary 31, 2012 at 11:46 AM

Committed on:
6.1.x GIT ID: 570b102b99312dfa4b63e65df22a4b2b8dcb751a.
6.2.x GIT ID: 77b29d7283412567afe16c0eefc8f507b60c47b8.

Raymond AugéJanuary 30, 2012 at 9:43 AM

1. Your instance has staging already implemented.
2. You create a new user.
This user is not in the remote live server the user exists only in staging.
3. You sign in as this user.
4. As this user you make some changes to the pages in staging.
5. The user "Publishes to Live"

no error message appears.

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Branch Version/s

6.1.x

Backported to Branch

Committed

Fix Priority

None

Git Pull Request

Affects versions

Priority

Zendesk Support

Created January 30, 2012 at 9:42 AM
Updated June 24, 2023 at 3:48 PM
Resolved October 1, 2012 at 12:40 PM
Loading...