Closed ctnadovich closed 4 months ago
Another possible mitigation for this would be for the app to open a dialog with any event_errors. I think right now the app simply says there are event_errors. Maybe just put them in the log.
There's now better listing of errors in future_events and eBrevet now opens a dialog that, I hope, clearly points people to the correct solution (fix the problems by editing RWGPS and Route Wizard).
If there are cue wizard errors, events still publish to ebrevet/future_events. This will cause eBrevet to choke and give a cryptic error.
Probably better if ebrevet/future_events did not list events with cue wizard errors. Then a FAQ answer could be added for the question "why don't my events publish on eBrevet?"