Simon Backx 5657019e47 Fixed wrong newsletter used when sending scheduled post (#14734) ... refs https://ghost.slack.com/archives/C02G9E68C/p1651939076681719 Cause: - When a scheduled post was published via the post scheduler, no `newsletter_id` option is passed when editing the post. - When editing a post via the posts service, without the `newsletter_id` option, the `newsletter_id` option is automatically set to the default newsletter's id. - Inside the post model, this new `newsletter_id` was not saved, because it was already set, and changing it is prevented. - The `mega` service wasn't using the (unchanged) post's newsletter_id, but used the option instead, which contained the default newsletter's id. Fix: - Always using the newsletter_id from the post and requiring the newsletter associated with a post to exist. - This behaviour can be/is tested by publishing a scheduled post without any option. Also cleaned up some `Object.assign` usages.		2022-05-09 17:30:50 +02:00
..
post-scheduling-service.js	🔥 Removed versioned APIs	2022-04-28 15:37:09 +01:00
posts-service.js	Fixed wrong newsletter used when sending scheduled post (#14734)	2022-05-09 17:30:50 +02:00