- contact e-mail recipients were incorrectly set resulting in the e-mails landing at the wrong recipient
- disabled users were not excluded from certain e-mails
- also removed an expensive lookup of sharing group permissions required for event views utilising the pagination from being run on actions that do not make use of it
- proposals to attributes didn't adhere to the visibility of the attribute
- users that were allowed to see an event but not a specific attribute could see proposals to the attribute
- proposals were not synchronised during pulls due to a bug
- affects both 2.3 and 2.4, the bug comes from the switch to json
- missing JSON view for proposal interface
- Also, 2.4->2.4 the organisation objects were incorrectly ommited from the sync
- Fixes:
- reverted back to XML for the old style proposal exchange
- 2.3->2.4 is now fixed
- 2.4->2.4 below 2.4.7 version will still not synchronise proposals on pull
- Proposal pull reworked
- requires 2.4.7 on both ends or higher
- proposals are now synced in one go
- massive increase in speed and reduction of log entries
- Proposal e-mailing reworked
- tied into the new 2.4 e-mailer, which was left out on 2.4's release by accident
- triggers correctly now when a proposal is added (also on pull)
- Fixed a typo that prevented the event level parameters to be used in the CSV export
- Fixed an issue where adding the contextual info in a CSV could lead to an invalid CSV if an event info field had a linebreak in it
- Tuned the performance of time based filtering (until now it would lookup events that should have been excluded in the first place, only to throw them away after the lookup again)
- Running a stix export for a specific ID that doesn't exist results in a full STIX export for the user (events visible to the user)
- This leads for an unnecesarily long export process when a quick export is expected
- publishing an event when push is enabled to a 2.3 instance failed with an error instead of blocking
- publishing an event wth the remote instance blocking it due to a sync user sharing group conflict resulted in an exception, handled gracefully now
- Added mangle-sync towards 2.3
- gracefully push non sharing group events in a 2.3 format
- timestamps downgraded by 1 second - upgrading the 2.3 instance should automatically allow a resync of mangled events
- corrected the edit access rights for sync users with sharing groups
- Various fixes to the organisation sync and how creation / modification dates are transmitted
- Internal format differences compared to 2.3 causing mismatched field lookups fixed
William Robinet