I've noticed if you make a change to a module at template level, upon save, the pop-up "There are XXX emails that are based on this template. Do you want to update all these emails?" appears, and I click Yes. However when I then go into an email that features the module I've updated, it is updated until a change to the email is made, which then reverts the changed content block back to the previous iteration. To force the change on the module, you have to go into the configuration window and click the refresh icon.
This is a flawed approach, for example, if a client is using a self-service email template / flexible framework, and they request updates to modules that could be in 100's of emails, the module won't refresh until that button is clicked.
Comment (1)