When attempted changes are being made to an event, those changes are not being reflected or displayed on the customer-facing side.
It is likely you are attempting to update an event's details from a corporate level, when the fields were not locked when the event was first created.
For clarification, if you do not lock the fields of an event, a separate event entry is created in the Brickwork database for each store the event is assigned to. This separation allows the event to be edited later on at the store level instead; but since it is separate from the initially created event on the corporate level, changing the corporate level details will not update the event at each store level if left unlocked. Going back in and retroactively locking these fields will not amend the issue.
In the future, if you know that you might want to change an event later on, the best practice would be for you to lock the fields by clicking on the little lock button (thus turning it green) in each box. This will prevent the events from being created and tied separately to each store you are assigning this event to and allow you to globally edit the settings if you need to later on.
- The current solution to this issue would be to go to the event on the store level, and edit it from there. If this event is tied to multiple stores, you will have to go to each store individually to edit them. You can do so by going to the store and clicking on Events > Manage.
- A secondary solution would be to delete the events and re-input one, this time locking all fields.
Separately, it could be that the changes did save, but you must wait for the cache to clear. Please see the linked article for more information here.