Summary | Track the Organizer of events |
Queue | Kronolith |
Queue Version | Git master |
Type | Enhancement |
State | Resolved |
Priority | 2. Medium |
Owners | Horde Developers (at) , mrubinsk (at) horde (dot) org, ralf.lang (at) ralf-lang (dot) de |
Requester | manoli.cano (at) upcnet (dot) es |
Created | 05/22/2006 (6933 days ago) |
Due | 02/14/2015 (3743 days ago) |
Updated | 07/16/2019 (2130 days ago) |
Assigned | |
Resolved | 12/18/2015 (3436 days ago) |
Milestone | |
Patch | No |
ticket 13664I 've to leave the Horde Groupware WebmailEdition solution because
this problem :(
I've approximately 300 users and this bug cause some spam issues with
the invites duplication.
prevented from using the calendar activity...
this is a new major version and includes changes to both our
development and release tools, we are not yet in the shape to make a
release.
is a new major version and includes changes to both our development
and release tools, we are not yet in the shape to make a release.
As we've seen on H5 master CHANGES [1], this bug has been solved, but
it has not been released yet. Have you thought about releasing this
version soon? It would be very interesting for us to have the
resolution of this bug in a stable version.
Thanks in advance!
[1] https://github.com/horde/horde/blob/master/kronolith/docs/CHANGES
Do you have some scheduled date to release it ?
The changing events owner kronolith bug is our main headache and new
version solves it.
the issues that have been holding it up.
issues that have been holding it up.
Thanks and regards,
Michael
set release date yet, but hopefully this year.
The above was almost 1 year ago.
Thanks for your time,
Michael
set release date yet, but hopefully this year.
The above was almost 1 year ago.
Thanks for your time,
Michael
or would it be possible for me to patch our current
lot of other changes in master that you will need to cherry pick
through. You will also run into issues with the database migrations
when it's time to actually upgrade in the future.
any plans when this is going to be released? This bugfix is much
appreciated.
set release date yet, but hopefully this year.
5.x releases or would it be possible for me to patch our current
installation? It's a real pain with Horde taking over the ownership of
foreign events.
any plans when this is going to be released? This bugfix is much appreciated.
set release date yet, but hopefully this year.
any plans when this is going to be released? This bugfix is much appreciated.
Thanks and regards,
Michael
welcome, though this seems to function well. Tested with meeting
requests from both external and local users using dynamic interface
and using ActiveSync. Could still use testing for the DAV
functionality, but it looks pretty straightforward.
Also, some minor changes to ActiveSync code to fix handling of the
response type values was done.
Assigned to Michael Rubinsky
State ⇒ Resolved
welcome, though this seems to function well. Tested with meeting
requests from both external and local users using dynamic interface
and using ActiveSync. Could still use testing for the DAV
functionality, but it looks pretty straightforward.
Also, some minor changes to ActiveSync code to fix handling of the
response type values was done.
very annoying.
Customers already started to apply filter rules to sort out false event mails.
I would very much appreciate a bugfix / patch for the 5.2 Releases.
patch shows some "Hunk #? FAILED at ???" messages, but it should not
to be hard to fix the patch for FRAMEWORK_5_2.
functionality, it won't be available in a stable release until Horde 6.
the patch and to remove event_organizer from table kronolith_events
(from kronolith/migration/26_kronolith_remote_organizer.php)?
organizers to events. Please try everyone if that patch works as
advertised and doesn't break anything else. Any testing and feedback
welcome. Please add your feedback to the pull request.
patch shows some "Hunk #? FAILED at ???" messages, but it should not
to be hard to fix the patch for FRAMEWORK_5_2.
After testing I may want to revert the patch. Is it enough to revert
the patch and to remove event_organizer from table kronolith_events
(from kronolith/migration/26_kronolith_remote_organizer.php)?
organizers to events. Please try everyone if that patch works as
advertised and doesn't break anything else. Any testing and feedback
welcome. Please add your feedback to the pull request.
https://github.com/horde/horde/pull/127 which has only few comments.
The last comment however "What I'm still misssing from this patch is
one of the key points of the original request: the attendees aren't
imported if I save a copy of this event.". First I couldn't find this
request in this ticket, secondly and most important, in the current
stable version of kronolith, the attendees are stored when copying the
event and also when importing it from an invitation in imp.
Why I ask: saving the attendees when adding an event from imp seems to
have been added within the last year. What seems to be an improvement
on the first glance, leads to a lot of trouble: accepting an event
makes me owner of that event. So if I change the event, I need to be
careful not sending an update. Or worse, if the actual organizer of
the event sends me an update on the event, and I accept that update,
all other attendees will receive an email from me, as I was the
organizer. Even worse, some colleagues use CalDAV with an external
calendar tool: if they disable the event's notification, the CalDAV
sync again leads to outgoing email notifications (no need to say, they
already ask for alternatives to Horde).
I recently accepted events scheduled for next week, which have more
than 40 attendees of different business partners. I don't dare to
touch that event even a little. If something goes wrong and everybody
receives an email, that for sure wont be a good advertisement for Horde.
be out of office for 3 weeks. Shall I wrap all the stuff into a
consolidated 1-commit PR for review or would you like to review the
PR as-is?
can be merged into the master branch.
Are there any written-down CODING_STANDARDS regarding the javascript
side of things? I tried to follow existing code as close as possible.
When you choose to send Itips, you actually send Itip Reply messages
regarding your attendance. You can change your attendance through a
new dropdown only shown when organizer is not creator.
be out of office for 3 weeks. Shall I wrap all the stuff into a
consolidated 1-commit PR for review or would you like to review the PR
as-is?
I'd like to make any final changes by end of march so the feature can
be merged into the master branch.
Are there any written-down CODING_STANDARDS regarding the javascript
side of things? I tried to follow existing code as close as possible.
When you choose to send Itips, you actually send Itip Reply messages
regarding your attendance. You can change your attendance through a
new dropdown only shown when organizer is not creator.
invitation? Is this the organizer's (tool's) task?
add new attendees and b) edit the event.
Don't know the mechanics behind this. Normally I would assume if I
edit my local copy of an event, that these are my notes on the event
and the changes should not be shared with everybody else.
current user?
may have different email addresses, and we should stick to the
original one. Internally created events shouldn't set, as long as we
don't have the option to pick an identity when creating an event.
app-generated content and Kolab as well?
that supports organizers.
And of course we need an UI for managing the organizer.
attendees when $organizer != $_creator while still allowing changes
in acceptance status to be emailed back to the $organizer. Also, do
we want to disallow any changes to an accepted invitation's details?
But how do other attendees notice that you have accepted the
invitation? Is this the organizer's (tool's) task?
Google Calendar has two checkbox options to a) allow attendees to add
new attendees and b) edit the event.
Don't know the mechanics behind this. Normally I would assume if I
edit my local copy of an event, that these are my notes on the event
and the changes should not be shared with everybody else.
but some calendar clients (especially on mobile) completely lock the
event (other than deleting it completely) when the current user is
not the organizer.
"description" part. If this is too tricky, locking might be an option.
against mails to anybody but the organizer. Due by Sunday night.
attendees when $organizer != $_creator while still allowing changes in
acceptance status to be emailed back to the $organizer. Also, do we
want to disallow any changes to an accepted invitation's details? For
me, if we disallow sending updates/cancellations this is enough, but
some calendar clients (especially on mobile) completely lock the event
(other than deleting it completely) when the current user is not the
organizer.
test as well. I've already got a fairly large number of ready-to-go
EAS testing setups :)
Once this is fully tested I can start looking at/testing turning on
allowing access to shared calendars for ALL EAS clients and not just
those that support multiple calendar collections.
I have a solution which sort of works for my scenario:
Google calendar invites horde user, horde user accepts via
thunderbird, thunderbird uses horde as caldav backend.
Previously, Horde dropped the ORGANIZER and used the CREATOR (the
accepting user) as the ORGANIZER when re-exporting the event to Caldav
-> thunderbird.
Also exports the ORGANIZER when exporting the event to ICS via
Kronolith Dynamic UI.
SHOULD also work for ActiveSync, but I have not done much testing on this.
The ORGANIZER attribute is currently not exposed in toJSON and it's
not displayed anywhere.
Please review.
ActiveSync users: Please test.
Assigned to Ralf Lang
Assigned to
Priority ⇒ 2. Medium
Due ⇒ 02/14/2015
really annoying.
I'll do it as a pull request though because of the review workflow.
I'm not sure how "core" I am these days.
Things to touch:
- Enhance db schema to include an organizer field
- Use the organizer field in Kronolith::sendItipNotification instead
of the creator field
- Use the organizer field in Event::toiCalendar, Fall back to creator
when no organizer value is present
- Use the organizer field in Event::fromiCalendar, leave blank if non set.
- Use the organizer field in Event::fromHash, leave blank if non set.
Open question: Set or don't set organizer field, if organizer is the
current user?
- Use the organizer field in Event::toASAppointment, fall back to
creator otherwise.
Open question: Do we need to handle this for Resources, app-generated
content and Kolab as well?
#13790, too. Besides, I don't think that thisis a low priority bug since it's kind of embarrassing when you'll make
yourself the organizer of a event with many invitees just because of a
bug. Every other attendee will then receive an email with another
invitation to an already processed event:
(copy&paste from
#13790)HOW TO REPRODUCE:
1. Get an invitation to an appointment where your email is set as attendee.
2. Accept the invitation using Outlook or Lightning (not the links in
the email but the buttons above).
3. Save the event to a calendar which is synchronized using Horde Kronolith.
4. Send out confirmation email.
5. The initial organizer will receive two mails. Note that the
organizer now isn't the initial creator, it will be you.
EXPECTED BEHAVIOUR:
The event will be accepted and the organizer won't change.
CURRENT BEHAVIOUR:
The event will be recreated with you as the organizer.
ticket 13664as it might be related.it. What we lack is developer time. If it's of great importance to
you, you should consider sponsoring the development.
file the organizer is not taken over/displayed in kronolith. E.g.
Lightning then assumes myself as organizer and this results in sending
myself a confirmation for an event organized by someone else. The
legit organizer however doesn't receive a confirmation.
Is there a fix planned?
Version ⇒ Git master
Summary ⇒ Track the Organizer of events
State ⇒ Accepted
events were from iCal invitations, not from someone creating the event
on a Kronolith shared calendar. Very important.
New Attachment: displayevent
The events are created in my calendar, not in a shared calendar. Two
other people have permission to 'show' and 'read' my calendar, but the
problem appears when anyone invites me to a event and I accept it.
Thanks in advance
Event delegation is when you create an event _as_ someone else. Is the
event in question on your calendar, or on a shared calendar?
New Attachment: display_event
by me) from my calendar.
I don't know how delegate and event. Where I can do it? or where I can
find information about this issue?.
Thanks in advance.
delegating an event to you?
a event not created by my in my calendar, then, the owner is my name
(Manoli Cano) not the real person that creates the event. So, If I
want to say anything to him I can't because I don't know who invites
me to the meeting.
I hope this clarify you the problem.
Thanks in advance.
own events is in the tooltips on event summaries. The event details
page always has the full name.
not created by my). Now, the owner are 'me' .
Type ⇒ Enhancement
State ⇒ Feedback
Priority ⇒ 1. Low
Version ⇒ HEAD
the event details screen?
State ⇒ Unconfirmed
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ Field Owner when I display the event
Queue ⇒ Kronolith
not created by my. I can't see who created the event, so, if I want
to send a mail or contact whit the real owner I can't because I don't
remember who vas him.
Thanks in advance.