Closed Bug 732772 Opened 13 years ago Closed 10 years ago

Copying recurring event from copy protected calender results in null event

Categories

(Calendar :: Provider: GData, defect)

Lightning 1.2
x86_64
Windows 7
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: sshmedom, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20100101 Firefox/10.0.2 Build ID: 20120215223356 Steps to reproduce: Goto google.com/calendar create one calender: "Test". Login on another google account create: "Test copy protected". Make "Test copy protected" accessible to the other account but just "See all event details". Add both to Lightning. "Test copy protected" is read-only. Create an event (Recurring every week, Fr, 12:00, 12:30 2.3.2012 to 30.6.2012). Copy event from "Test copy protected" to "Test". Actual results: Creates an event that has the name "null". Starting at the correct time, lasts for 0min, and is not recurring. No entries in Error Console. The failure does not happen on the same calender when its a single event. Reloading works fine. Tried copying it to different calenders - always the same result. Expected results: Should copy the event.
OS: All → Windows 7
Hardware: All → x86_64
Copy and paste of repeating events is known to be not working. See e.g. Bug 536796.
There has been a major rewrite of the Provider for Google Calendar between version 0.32 and 1.0. A vast number of bugs have been fixed during this rewrite, therefore I am closing lots of old bugs that I think might either be fixed or no longer apply to the latest version. Please read the updated FAQ [1] for details on known issues. If you can reproduce your issue with the latest version of the Provider for Google Calendar and you can't find an existing bug that handles your case, please reopen this issue. Thank you for your understanding. [1] https://wiki.mozilla.org/Calendar:GDATA_Provider
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.