alf.io
alf.io copied to clipboard
Edit event dates displays error in dashboard but no info is provided
To Reproduce
After updating a pre-existig event with new dates, the following message appears in the dashboard but no indication of what the error is about is shown.

Expected behavior If some data validation shows issues, I'd expect to be displayed in the dashboard of the general event view.
Screenshots If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
- OS: Linux
- Browser: Firefox
- Version: 2.0-M2-SNAPSHOT
Additional context Basically, we want to update a past cancelled event (for COVID) with metadata for new event, keeping all sold tickets and other information for the current new. So far, other than this issue, the only other problem is we cannot update the url, but I think we can live with it.
Hi, thanks for letting us know.
Please double check for expired fixed-size (hidden or public) ticket categories. That's usually the case. We'll improve that warning message in the next versions (M4+).
2.0-M2 is an old and unmaintained version, so it doesn't make sense for us to fix the bug there. Instead, it would be great if you could try to run 2.0-M4.RC2 on a copy of the database, just to make sure that this issue has been fixed.
We migrated and after some ticket dates update we see this again. Is there some way to find a hint?
can you please do the following:
1. retrieve your event's id
select id from event where short_name = `<event slug>`;
2. share the output of the following queries
select id, is_containing_orphan_tickets, is_containing_stuck_tickets_count from events_statistics where id = `<insert the id of your event here>`;
and
select ticket_category_id, event_id, is_expired, is_containing_orphan_tickets, is_containing_stuck_tickets from ticket_category_statistics where event_id = `<insert the id of your event here>`;
I've excluded all the "sensitive" columns, so that you can share the results. You can find the code for these views here:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.