The browser should not be redirected to the calendar view screen after one saves the content of the calendar edit screen

• Type: Bug
• Status: Closed
• Resolution: Fixed
• Affects Version/s: 6.2.0 CE M5
• Fix Version/s: 6.2.0 CE M6
• Component/s: Calendar, Collaboration
• Labels: None
• Epic/Theme:
  • Collaboration_Calendar
• Similar Issues: Show 5 results ; ;

  LPS-43733	Calendar's event view screen displays contents in inputs and HTML code in description
  LPS-35356	The calendar edit screen does not show form if accessed after going to the resources tab
  LPS-42648	On an iPad or mobile view (768 - 979 pixels), the mini calendar remains static for different screen widths and overlaps with the larger calendar
  LPS-40524	Repeat screen not correctly aligned on screen
  LPS-45626	After editing calendar, reload calendar list without reloading entire page

When one clicks on the "Calendar Settings" link on a calendar menu, edit the contents of the presented forms and click in "Save", the browser is redirected to the view of the calendar. It made some sense when the configuration of a calendar was pretty small; now, however, the calendar configuration is considerably heaver than before, so one can want to review one's saved edition, or one may want to save part of the configuration and continue configuring it. So, I believe the action of saving the calendar configuration should not redirect to the calendar view anymore; instead, the browser should stay in the configuration window.

[Adam Brandizzi]

If the user creates a new calendar, it will be redirected back to the calendar portlet display view.
If one edits an existing calendar, it will stay in the calendar configuration view.

[Sharon Choi]

PASSED Manual Testing following the steps in the description.

Fixed on:
Tomcat 7.0 + MySQL 5. Portal 6.2.x GIT ID: a1a1eb16189f149a1d29fa5511251e52cd813c4c.
Plugins 6.2.x GIT ID: 4d03a80247681175fe502cc447c3a726e69eb966.

The browser no longer redirects the user to the calendar view after saving edits in the calendar settings screen. No errors are thrown in the console and everything seems to be working correctly.