With all of the upgrades being done, there is something that I noticed that is causing some grief.
When I upgraded to 2.7.X after the bugs had settled down, I lost a lot of the work I had done on custom fields. Names had changed, and default values for being a mandatory field changed.
This has become a problem as we missed it in the initial release and now one of the mandatory fields is missing data and we have no way on contacting our customers!
I figured out that what I had to do was go to the FIELDS setup in the control panel and make the field mandatory again. However, once I did this, it did not appear as mandatory on the events until I opened the event and then simply saved it. That process fixed the problem.
The issue is that I have a LOT of events that I now need to open and save, just to make this work.
Is there any way you could create a script or process like you did for the JEvents Sync button, that says SAVE ALL EVENTS. There would then be a selection that users had to allow them to pick either unpublished, published or all and then initiate the process. This would have the same effect as opening each individual event and saving it so that it picks up the new default information from the configuration setup.
This would help both during upgrades and if a bulk change needs to be made due to a new field being added or a current field being changed for events that are already created.