Local backend breaks and gets notification when remote backend "is experiencing a major incident"

[josineto]

As I write this issue, GitLab (my remote backend) has a specific problem, and thus Sveltia CMS warns me that "GitLab is experiencing a major incident" (which is very nice, by the way). As I'm working on a local server, Sveltia CMS offered me to use local or remote backend (as of v0.35.0). But when I connect to local, the same notification appears: "Local Repository is experiencing (...)", with a link to about:blank. Worse: I can't edit any item of any collection, be it file or folder collection (although I can change between collections, trying to enter the editor does nothing, and JS Console is empty).

[josineto]

(Sorry, I was eager to test v0.35.0, but (perhaps luckily) faced this problem...)

[kyoshino]

Thanks for catching this. Will fix.

[kyoshino]

Worse: I can't edit any item of any collection, be it file or folder collection (although I can change between collections, trying to enter the editor does nothing, and JS Console is empty).

Hmm, I’m not able to reproduce the problem. Sveltia CMS could disable editing functionality in case of a major incident, but I haven’t implement it; instead, it just shows a notification as you see. Not sure why this happens 🤔

[kyoshino]

The incident notification is now hidden with the local backend as of v0.35.1. Let me know if the editing issue still happens.

[josineto]

The editing issue has gone as well. Sorry for not having more evidences of it, the console was empty when it happened. Anyway, thank you for the fast correction!

[kyoshino]

No worries, thanks for verifying the fix!