fix(imip): dont compare events for the reply message

[hamza221]

• Resolves: Changes by attendee propagating to organiser calendar#6701

Summary

TODO

• ...

Checklist

• Code is properly formatted
• Sign-off message is added to all commits
• Tests (unit, integration, api and/or acceptance) are included
• Screenshots before/after for front-end changes
• Documentation (manuals or wiki) has been updated or is not required
• Backports requested where applicable (ex: critical bugfixes)

[SebastianKrupinski]

Hey, you can't just pull the event by the recipient, This will fail, for external organizers

[hamza221]

@SebastianKrupinski would it make sense to keep this even that it only works if the organiser is a local user?
I mean check if he is and search for the event. Sent potentially wrong message in the other case? Would be better than nothing no ?

[SebastianKrupinski]

@SebastianKrupinski would it make sense to keep this even that it only works if the organiser is a local user? I mean check if he is and search for the event. Sent potentially wrong message in the other case? Would be better than nothing no ?

I don't think having different code paths for internal and external attendees is a good idea, just makes it too complex, the only thing I would keep is the separate method for the reply message, as the reply does not need event comparison, and all the extra information that is normally generate

[st3iny]

Tested and works.

[st3iny]

/backport to stable30

[st3iny]

/backport to stable31

[backportbot]

The backport to stable31 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable31
git pull origin stable31

# Create the new backport branch
git checkout -b backport/51131/stable31

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick ed1bfe70

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/51131/stable31

Error: Failed to push branch backport/51131/stable31: remote: Invalid username or password.
fatal: Authentication failed for 'https://github.com/nextcloud/server.git/'

---

Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.

[st3iny]

/backport to stable31