hueyo

Q: new entries revert to "new event"

Just within the last few days, Calendar has begun consistently misbehaving. I create a new event, assign it to a calendar, fill in information such as time and notes. I close the editing window, the new title displays (I'm using Month View) for just a second, and then it reverts to "New Event," and everything I've entered is lost. Oddly, when I enter all the information a second time, it always seems to stay.

 

As far as I know, I haven't made any changes to my OS (10.9.5) or to Calendar (7.0), neither via their settings nor any other way. FYI, I'm using iCloud to sync between the calendars on my MBPro and my iPhone (4S, running 7.1.2).

MacBook Pro (13-inch Early 2011), OS X Mavericks (10.9)

Posted on May 15, 2015 5:45 PM

Close

Q: new entries revert to "new event"

  • All replies
  • Helpful answers

first Previous Page 8 of 19 last Next
  • by hueyo,

    hueyo hueyo Jun 12, 2015 10:40 AM in response to deebec
    Level 1 (11 points)
    Jun 12, 2015 10:40 AM in response to deebec

    I just realized it might be a good idea to search my own Calendar for "new events," and I found half a dozen spread over the last decade. That's not too bad, and it's even possible that they might all be actual New Events that didn't get filled in with any info... although I doubt that. Obviously, it's distressing to find that data may have been lost, without any way of knowing what it was.

     

    One thing I noticed, is that now Calendar is showing those dates from long ago, when I lived in a different time zone, with "CDT" and "CST" appended to the times. I don't remember Calendar ever doing that before. I wonder if that might be related to this problem we're having? Somebody suggested turning off the local time zones setting seemed to help, although as I recall someone else popped up pretty soon thereafter and said it didn't...

     

    I wonder if we're gonna have to go down and start picketing our local Apple Stores to get the "geniuses" there to fix this!

  • by Gian70,

    Gian70 Gian70 Jun 14, 2015 1:06 AM in response to George Mattingly
    Level 1 (0 points)
    Jun 14, 2015 1:06 AM in response to George Mattingly

    Yes, upgrading to Yosemite didn't solve the problem (tried on a clone HD, i'm on mavericks now).

    Maybe a clean install from scratch can do, hadn't tried.

     

    Upgrading to Yosemite won't solve this. We've been running OS X 10.9.5 for months & this problem just started happening (within the past month). But we might have found a solution: got to Preferences > Advanced, and deselect "Turn on time zone support." For us the problem stopped immediately. Knock on wood.

  • by Gian70,

    Gian70 Gian70 Jun 14, 2015 1:10 AM in response to hueyo
    Level 1 (0 points)
    Jun 14, 2015 1:10 AM in response to hueyo

    Btw sometimes the bug didn't happen (like now, just tried to add 2-3 events).

    So maybe it's possibile to find a workaround...

  • by mrchntmarine,

    mrchntmarine mrchntmarine Jun 15, 2015 3:25 PM in response to hueyo
    Level 1 (7 points)
    Jun 15, 2015 3:25 PM in response to hueyo

    is there anyone out there that has upgraded to yosemite and had this problem resolved?  If so, when did you do the update?  I just had a conversation with a senior rep. bc the last one i talked with has refused to schedule a call back and we keep playing phone tag.  This last rep. told me the official apple fix is to update to yosemite even though he could not point me to any official apple info. on the fix and could not guarantee that it is a 100% fix and could not tell me how I could revert back to mavericks if the fix did not work.  on top of that, he basically said that the info on this site is not apple approved or supported.  also, mid way through our conversation, after I of course had given them my call back no., etc, the line went dead and I received no call back nor did the rep give me his contact no or contact info.

  • by brookewood,

    brookewood brookewood Jun 15, 2015 4:11 PM in response to mrchntmarine
    Level 1 (0 points)
    Jun 15, 2015 4:11 PM in response to mrchntmarine

    Do not upgrade to Yosemite if you plan or want the option to go back to Mavericks. I upgraded last Fall and there was a bug that caused a "leak" from my email which caused my RAM to continually max out  making the computer inoperable. I'm sure the problem is corrected by now but through the fiasco of trying to restore my Yosemite back up to Mavericks with no success I learned that Yosemite repartitions the hard drive so I could not go back. The only solution was to buy a used iMac with Mavericks installed on it and I was  somehow able to restore my Yosemite back up to that one. I was told however that when I'm ready to upgrade to Yosemite, to stop my backups from running until I'm completely satisfied with Yosemite.   The idea is you should be able to restore your Mavericks back up and go back to Mavericks.  So check into this idea before you upgrade!

  • by acmac,

    acmac acmac Jun 16, 2015 12:49 AM in response to mrchntmarine
    Level 1 (14 points)
    Mac OS X
    Jun 16, 2015 12:49 AM in response to mrchntmarine

    I had a similar battle with Apple Tech and we came to the conclusion that upgrading the Yosemite would solve this. This was at great expense as we had to upgrade other software that was not compatible to Yosemite. I am not convinced that it has completely fixed the problem but we do have less issues. However there are a whole new set of bugs Yosemite brings. 

     

    It seems Microsoft (whoops apple) can't even stop the screen saver reverting back to the original picture every couple of weeks.

     

    We upgraded 2 weeks ago and all machines that use the ICAL network need to be upgraded. 

     

    Good luck

  • by mrchntmarine,

    mrchntmarine mrchntmarine Jun 16, 2015 10:36 AM in response to hueyo
    Level 1 (7 points)
    Jun 16, 2015 10:36 AM in response to hueyo

    is there anyone out there that has upgraded to yosemite and had this problem resolved?  If so, when did you do the update?  I just had a conversation with a senior rep. bc the last one i talked with has refused to schedule a call back and we keep playing phone tag.  This last rep. told me the official apple fix is to update to yosemite even though he could not point me to any official apple info. on the fix and could not guarantee that it is a 100% fix and could not tell me how I could revert back to mavericks if the fix did not work.  on top of that, he basically said that the info on this site is not apple approved or supported.  also, mid way through our conversation, after I of course had given them my call back no., etc, the line went dead and I received no call back nor did the rep give me his contact no or contact info.

  • by akicats,

    akicats akicats Jun 16, 2015 12:34 PM in response to hueyo
    Level 1 (0 points)
    Jun 16, 2015 12:34 PM in response to hueyo

    With "it always keeps the second entry" in mind, i'm surprised that nobody mentions the copy-paste workaround .

    When i close the edited event, i immediately press cmd-c, afterwards i delete the annoying "new event" and paste.

    It's all there, and it's gonna stay there.

  • by rigelusesapple,

    rigelusesapple rigelusesapple Jun 16, 2015 1:46 PM in response to hueyo
    Level 1 (0 points)
    Jun 16, 2015 1:46 PM in response to hueyo
    I just realized it might be a good idea to search my own Calendar for "new events," and I found half a dozen spread over the last decade.

     

    An exceptionally good call, hueyo!  I did the same, and found about a dozen tracing back to 2008.  I was able to amend some of them through a backup and memory, and am glad to have done so.

  • by thomaslb,

    thomaslb thomaslb Jun 17, 2015 11:17 AM in response to hueyo
    Level 1 (0 points)
    Jun 17, 2015 11:17 AM in response to hueyo

    I have read through a lot of the posts but not all. This has happened to me too. I find it completely unacceptable and no, I will not 'upgrade' to Yosemite (for all of the good reasons listed in previous posts). So, not sure if this option has been mentioned. I simply FIRED my Apple Calendar (see ya!) and replaced it with BusyCal. No issues. Gone. And, as often happens in these situations, I end up with a LOT more capability than I was stuck with previously. BusyCal syncs across all of my devices, it is stable, more robust and capable (icons, banners, lots more command options, far more sophisticated interface, etc.). And it is a complete work around to the ApplCal problems we have been having. I'm sure there are other options out there too.

     

    Highly encourage you folks to move on to a better Mac calendar option. It works. Learning curve is light. You won't be sorry. And you'll be back in the command chair with your own solutions.

  • by rkpdavid,

    rkpdavid rkpdavid Jun 17, 2015 11:32 AM in response to thomaslb
    Level 1 (0 points)
    Jun 17, 2015 11:32 AM in response to thomaslb

    Does BusyCal work on the iphone as well?  The website talks about it synching, but can you make appointments/ edits through the mobile device?  It looks like a good alternative - thanks!

  • by thomaslb,

    thomaslb thomaslb Jun 17, 2015 11:40 AM in response to rkpdavid
    Level 1 (0 points)
    Jun 17, 2015 11:40 AM in response to rkpdavid

    Yes. BusyCal works very well with the iOS stock calendar (fortunately we are not having iOS problems right now!). Thoroughly tested it for more than a week now and like most of you my flag raises or falls around my calendar. It HAS to be rock solid. Run my business off it. BusyCal even works well with other iOS add-on calendars/replacement calendars according to their documentation but to be honest I haven't bothered to try. It syncs through your iCloud account and completely bulldozes through this issue. I picked BusyCal mainly because it's website gave me the distinct impression that they were not about forcing you to upgrade. (Meaning the stated they supported Lion, Mavericks, etc.). Others out there will say "Yosemite."

     

    But to answer your question - yes, works perfectly fine with the iOS cal.

  • by thomaslb,

    thomaslb thomaslb Jun 17, 2015 11:53 AM in response to thomaslb
    Level 1 (0 points)
    Jun 17, 2015 11:53 AM in response to thomaslb

    So you can edit on the iOS device and it appears in BusyCal. You can also manually push a sync on BusyCal by hitting 'Command R' but I haven't found the need to. Your license is to you as an individual so if you are like me and work off a MacMini and a MacBook Air (or more Apples) you get to install on all of them.

     

    And for some reason I just feel like the folks over at BusyMac have my back. I don't feel that way about Apple right now. That's a shame.

     

    EDIT - PS - In case you were wondering, yes, it grabs your iCal data and copies it into BusyCal so NO, you are not doing any initial re-entering of appts.

  • by ddelcourt,

    ddelcourt ddelcourt Jun 17, 2015 3:01 PM in response to hueyo
    Level 1 (0 points)
    Jun 17, 2015 3:01 PM in response to hueyo

    I tried creating an event while monitoring both my iCloud calendar (on iCloud.com) and my iphone.

     

    The event is dispatched on all linked machines as "New event" as soon as a time range is selected in Calendar.

    It's already stored and dispatched as this, even before you start typing.

    Apple, need to investigate this. Why don't you store the event only after the creation process is done?

     

    There's a bug in the calendar assignement process that creates a mismatch in the iCloud database.

  • by ddelcourt,

    ddelcourt ddelcourt Jun 17, 2015 5:23 PM in response to acmac
    Level 1 (0 points)
    Jun 17, 2015 5:23 PM in response to acmac

    You are not going to like this:

     

    I have just had confirmation from Apple Tech that Apple can't/won't fix this problem. The only thing we can do is to upgrade to Yosemite which will fix the issue. This is costing our business a great deal as we have to upgrade other software to be compatible with Yosemite.

     

    acmac, did they mention what the bottom-line is?

    What causes the problem to arise?

    Personaly, I don't buy it. Upgrading for what reason?

    I'd rather do a clean install of Mavericks first.

first Previous Page 8 of 19 last Next