You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Adding an image (or presumably any other related object) to a Page that has just been added to a Campaign will prevent that Campaign from being published until the user reloads the CMS.
Steps to reproduce
(Ensure devtools are open)
Create a Campaign
Create a Page, save but do not publish it
Add the Page to the Campaign
Navigate to the Campaign admin, observe that the Page is listed in the Campaign
Navigate back to the Page editor, add an image and save
Navigate to the Campaign admin, observe that the new Image is not listed in the Campaign
Attempt to publish the Campaign, observe no reaction in UI (and observe a 403 response in the Network tab of the devtools with error "ChangeSet does not include all necessary changes and cannot be published.")
I believe the issue may be occurring at Step 3, where the Page is added to the Campaign, as it seems like that state of the Campaign is 'sticking'. The Campaigns API sensibly refuses to publish when the user can't see everything that will be changed, but it also doesn't warn the user of the issue (better messaging is likely outside the scope of this issue - see #131.)
The text was updated successfully, but these errors were encountered:
Tested version: 1.6.x-dev
Outline
Adding an image (or presumably any other related object) to a Page that has just been added to a Campaign will prevent that Campaign from being published until the user reloads the CMS.
Steps to reproduce
(Ensure devtools are open)
I believe the issue may be occurring at Step 3, where the Page is added to the Campaign, as it seems like that state of the Campaign is 'sticking'. The Campaigns API sensibly refuses to publish when the user can't see everything that will be changed, but it also doesn't warn the user of the issue (better messaging is likely outside the scope of this issue - see #131.)
The text was updated successfully, but these errors were encountered: