| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Related to https://gitlab.gnome.org/GNOME/evolution-ews/issues/39
|
|
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/issues/88
|
|
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/issues/87
|
|
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/issues/86
|
|
|
|
|
|
|
|
| |
The POST to scheduling outbox expects text/calendar data, but CalDAV
had been using application/xml, which could be rejected by some servers.
This had been reported as part of:
https://gitlab.gnome.org/GNOME/evolution-data-server/merge_requests/7#note_437643
|
|
|
|
| |
Related to https://gitlab.gnome.org/GNOME/evolution-data-server/issues/81
|
|
|
|
| |
... by adding them into one common place.
|
| |
|
|
|
|
|
| |
Reported downstream as:
https://bugzilla.redhat.com/show_bug.cgi?id=1660257
|
|
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/merge_requests/8
|
|
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/merge_requests/7
|
|
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/issues/65
|
|
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/issues/63
|
|
|
|
|
|
|
|
| |
This runtime warning had been shown when running Evolution in Flatpak
with GNOME 3.30 runtime. It had been due to libical not finding
tzdata file in the expected directory. Let's relax the runtime
warning, because it can happen the time zone detection fails, even
in a corner case.
|
|
|
|
|
|
|
|
| |
When a component/contact is loaded from the server when it's not part
of the local cache (which can happen for example with meeting invitations),
then the fetched object was stored without the href in the local cache,
which made it impossible to edit the object later (it resulted
in an "Invalid Object" error).
|
|
|
|
|
|
| |
The only two parts using it were GDBus objects for address book and
calendar view, which could be easily transformed to use gdbus-codegen,
the same as the rest of the GDBus objects defined in src/private/.
|
|
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/issues/41
|
|
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/issues/49
|
|
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/issues/50
|
|
|
|
| |
Closes https://bugzilla.gnome.org/show_bug.cgi?id=606071
|
|
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/issues/48
|
|
|
|
|
|
|
| |
There had been logged only headers even when the user requested to
log everything due to use of SoupRequest. The added code logs also
the response body when requested. The order of the headers and
the body can be opposite, due to libsoup internals.
|
|
|
|
|
|
| |
Also introduce and use e_util_strcmp0(), which can avoid the most common mistake
of comparing a NULL with an empty string, which are equal after e_util_strdup_strip(),
but which caused a false property change notification.
|
|
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/issues/44
|
|
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/issues/43
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The 'parent' property of the GDataTasksTask object is exposed
through ICAL_RELATEDTO_PROPERTY, which matches the practices
of GNOME To Do and NextCloud and other ICal-based providers.
The position, however, is exposed through an X ICal property
named X-EVOLUTION-GTASKS-POSITION. This doesn't affect Evolution
in any form, but will still allow external consumers of EDS to
retrieve the position of the task. Since GData tasks themselves
aren't backed by ICal components, we have some creative freedom
to use X properties.
Updating the task position and parent requires [1], but a compile
check was added to not force EDS to bump the libgdata version.
[1] https://gitlab.gnome.org/GNOME/libgdata/merge_requests/4
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/merge_requests/2
|
|
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/issues/24
|
|
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/issues/19
|
|
|
|
|
| |
Addresses compiler warnings on 32-bit architectures:
warning: format '%lli' expects argument of type 'long long int', but argument 3 has type 'time_t' {aka 'const long int'} [-Wformat=]
|
|
|
|
|
|
|
|
|
| |
In case older version is run after the table had been altered can
cause another try to add the 'refs' column, which fails due to
duplicity and avoids opening the calendar. This change doesn't
alter table when the column is already there.
Related to https://bugzilla.gnome.org/show_bug.cgi?id=794108
|
|
|
|
| |
Related to https://bugzilla.gnome.org/show_bug.cgi?id=794874
|
|
|
|
|
|
| |
At least the EBookCache can store non-UTF-8 values into the database
within the INSERT statement, which require conversion to UTF-8,
otherwise an "[Invalid UTF-8]" error is shown on the client side instead.
|
|
|
|
| |
Related to https://gitlab.gnome.org/GNOME/evolution/issues/37
|
| |
|
|
|
|
| |
See https://developer.gnome.org/hig/stable/typography.html
|
|
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/issues/11
|
|
|
|
|
|
| |
the component
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/issues/10
|
|
|
|
|
|
|
|
|
|
|
| |
It could happen that one thread had been working with the connection
while another thread disconnected it, which could lead to a race
condition on the connection object, especially when the code execution
had been within that object.
The change makes sure to either add a reference on the connection
object while working with it or it adds a connection lock which is
acquired for the whole time when the connection object is used.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
I made a mistake when adding there these virtual methods. I'm not
bumping soname version, because it's unlikely that anyone is using
it, because it's a very new thing.
|
| |
|
| |
|
|
|
|
|
| |
Use virtual methods to open an ECalClient instance, to make it possible
to share the same ECalClient objects in an application between its parts.
|
| |
|
|
|
|
|
|
|
| |
Apart of the move itself, it also contains a UI change of the notification
dialog, the same as the changed way of dealing with the reminders:
a) reminders persist between sessions, until they are dismissed
b) snoozed reminders also persist between sessions.
|
| |
|
|
|
|
|
|
| |
This object can be used by applications which want to implement
their own notifications for scheduled reminders without a need
to implement the core functionality.
|
|
|
|
| |
whether writeable
|