You can't synchronize the subscription between sites because when the config importer goes to import it a second time, Brightcove fails with a 404 that the subscription already exists. This hard failure prevents further synchronization. When syncing the configuration or installing a new site, it exists from the previous configuration, and thus shouldn't be a hard failure. One possible solution, provided as a patch here, is just to remove the existing subscription endpoint before creating a new one. Another possible solution is to catch the 404 and fail more gracefully. I did not do that solution, because I'm not sure what else can cause a 404, and I didn't want to look at string text to find the exact error.
Comment | File | Size | Author |
---|---|---|---|
#4 | sync-sub-2902537-4.patch | 1.14 KB | douggreen |
Comments
Comment #2
douggreen CreditAttribution: douggreen at Appnovation for Pfizer, Inc. commentedpatch attached
Comment #3
douggreen CreditAttribution: douggreen at Appnovation for Pfizer, Inc. commentedCleaner patch attached (the last one built ontop of previous ones and applied with offsets).
Comment #4
douggreen CreditAttribution: douggreen at Appnovation for Pfizer, Inc. commentedUpdated to latest head
Comment #5
yce CreditAttribution: yce at Pronovix for BrightCove commentedIt should be fixed now in the 1.3 version, the subscriptions are no longer config entities.