You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you have important birthdays and anniversaries that you never want to miss then it is a good idea to save/copy those contacts to a local address book "On This Computer". This is why:
The Birthday calendar is virtual. It gets reconstructed every time e-calendar-factory is started (e.g. when you first-time start Evolution and switch to Calendar). Birthdays and anniversaries from local calendars will always get checked and shown in the calendar. e-calendar-factory also "remembers" (in session memory, not file cache) any new birthdays saved - regardless of whether the contact is local or remote, until you log out. But existing remote contacts (from LDAP) do not just get "automatically scanned" for birthdays on first startup. I am guessing there are multiple reasons for this: performance, credentials, filter selection, etc much of which is user-configured and first used when you select an LDAP address book. Bottom line: if you want to see calendar birthdays from a remote LDAP addressbook you need to "read" the LDAP contacts in an Evolution session before e-calendar-factory is started. You can also quit evolution and stop the e-calendar-factory executable - either from task manager - or run from command prompt: taskkill /IM "e-calendar-factory.exe" /F
.. but DO NOT stop e-addressbook-factory, then restart evolution and all of those LDAP birthdays will be visible in the calendar. It's doable if you don't mind the hassle.
This also explains why birthdays and anniversaries in LDAP never display if evolution-alarm-notify autostarts at login. It might be possible in a future patch to trigger a full calendar refresh after a user views a remote addressbook. But for now, that's why important birthdays and anniversaries should probably be kept/copied to a local address book contact.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
If you have important birthdays and anniversaries that you never want to miss then it is a good idea to save/copy those contacts to a local address book "On This Computer". This is why:
The Birthday calendar is virtual. It gets reconstructed every time e-calendar-factory is started (e.g. when you first-time start Evolution and switch to Calendar). Birthdays and anniversaries from local calendars will always get checked and shown in the calendar. e-calendar-factory also "remembers" (in session memory, not file cache) any new birthdays saved - regardless of whether the contact is local or remote, until you log out. But existing remote contacts (from LDAP) do not just get "automatically scanned" for birthdays on first startup. I am guessing there are multiple reasons for this: performance, credentials, filter selection, etc much of which is user-configured and first used when you select an LDAP address book. Bottom line: if you want to see calendar birthdays from a remote LDAP addressbook you need to "read" the LDAP contacts in an Evolution session before e-calendar-factory is started. You can also quit evolution and stop the e-calendar-factory executable - either from task manager - or run from command prompt:
taskkill /IM "e-calendar-factory.exe" /F
.. but DO NOT stop e-addressbook-factory, then restart evolution and all of those LDAP birthdays will be visible in the calendar. It's doable if you don't mind the hassle.
This also explains why birthdays and anniversaries in LDAP never display if evolution-alarm-notify autostarts at login. It might be possible in a future patch to trigger a full calendar refresh after a user views a remote addressbook. But for now, that's why important birthdays and anniversaries should probably be kept/copied to a local address book contact.
Beta Was this translation helpful? Give feedback.
All reactions