Closed troughc closed 1 month ago
@AbhishekPAnil @sahalali sorry the above event looks the same to me. I don't see a change. Let's revisit next time we meet.
@troughc Did you check this in staging or production?
I checked in staging and in the PR. Here are the issues:
List view both look like multiple dates:
Read only in staging (multi-date):
Read only in PR (date range):
Edit in staging (date range):
Edit form in PR (date range):
should be multi-date (custom).
Bug report : You are right ,the staging was showing the corrupt data as well.It was happening because the data in staging was replaced by the production data accidentally after it was fixed.
This is now updated in staging.Please check and let me know if you face anymore issues.
@AbhishekPAnil it looks okay to me now (looking at the one event). PASSED
I don't know what is causing this issue. After some investigation with Gregory we think that a migration script is needed to update old events. The reason is, we refreshed another event (re-saved) and it updated to reflect the correct data everywhere).
This event should be a multiple date event with (20 occurrences), as it is on the client site
TEST CASE: To check that the migration script is correct, make sure this event is a multiple date event with 20 occurences.
this event named "Exposition permanente « 4, 3, 2, 1... Santé! »" in Signe Laval has not been refreshed and:
Here are screenshots
List view of event with OCCURENCES
Read-only view of event's date type (multiple dates - CUSTOM)
Edit form view of event as DATE RANGE (THIS IS WRONG)
View of developer tool with subevents