This has now been fixed. Please confirm @skymaster200. One of our plugins clashed with another plugins recent changes, so had to make some adjustments.