Thanks for flagging this. This has been resolved in Breeze 2.5.16 — please update to the latest version and let us know if you still run into this afterward.
Thanks for flagging this. This has been resolved in Breeze 2.5.16 — please update to the latest version and let us know if you still run into this afterward.
Thank you both for reporting this, and for the detailed information you’ve shared — it’s very helpful.
The Breeze team is aware of this issue and is actively investigating it. The team understands how disruptive this can be, especially on multisite setups, and is treating it as a priority.
In the meantime, rolling back to Breeze 2.5.14 and temporarily disabling automatic updates for Breeze should help avoid this until a fix is released.
The Breeze team appreciates your patience, and will share an update here as soon as a fix is ready. Thank you again for taking the time to report this in such detail.
