Extensions have caused issues for people in the past because they can interfere with underlying cookies and/or code. The fact that everything worked before doesn’t prove that it’s an issue with Glide or the extensions.
My career is based on debugging and fixing code every day, and 90% of the battle is knowing how to reproduce an issue. Fixing issues is easy when you know what you are fixing. I recall an issue we had at my company in the past where we had a particular user that disabled javascript and things didn’t work when they used our website. We didn’t know they had javascript disabled because who would and who would ever expect that to be an issue most of the time. It took our support team a long time and several screen sharing calls to figure out that the user had javascript disabled and the only fix was for the user to turn it back on. We didn’t know how to reproduce it until we figured out that tidbit. As a developer, if it works on my end, I won’t know what to fix.
Before jumping the gun, it would at least be helpful if you can please
try to eliminate some rogue extension as the source of the problem by disabling them at least temporarily. If that doesn’t work, then I would clear cache and cookies in the browser. If there is still an issue, then open a support ticket. My guess is that if you submit a ticket now, they may not be able to reproduce the issue or know how to reproduce it to fix anything…if it’s even a Glide issue.
Glide support is available on Pro plans and above.