Uploaded image for project: 'PUBLIC - Liferay Portal Community Edition'
  1. PUBLIC - Liferay Portal Community Edition
  2. LPS-47789 Moving first instance of a recurring event to a day in the future and choosing to update the following ones creates new events in the original day
  3. LPS-47811

The index of an event instance should be known on the client side

    XMLWordPrintable

    Details

      Description

      Currently, A.SchedulerEvent objects (which are JavaScript objects) do not know which instances of recurring events they represent. Without this information, we have to rely on their start time. However, this start time cannot point to the correct instance reliably since it's sometimes updated to another date, resulting in the wrong instance being retrieved. For solving that, the A.SchedulerEvent objects should know the index of their instance for they can send it to portlet class.

      Steps to reproduce

      • None: this ticket is not testable by QA.

        Attachments

          Issue Links

          is a dependency of

          Bug - A problem which impairs or prevents the functions of the product. LPS-47404 CalendarBooking dates are wrong for recurrent events

          • Closed

            Activity

              People

              Assignee:
              brian.chan Brian Chan
              Reporter:
              adam.brandizzi Adam Brandizzi
              Recent user:
              Esther Sanz
              Participants of an Issue:
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Days since last comment:
                7 years, 23 weeks, 1 day ago

                  Packages

                  Version Package
                  6.2.X EE
                  7.0.0 M1