Switching from glitch-soc to vanilla makes MastoFE unusable #65

New issue

Closed

opened 2019-04-11 18:02:57 +00:00 by gitlab-ghost-3733 · 2 comments

gitlab-ghost-3733 commented

2019-04-11 18:02:57 +00:00

Member

Since the window is blank, I can't really switch back to glitch-soc. I tried flushing cookies and localstorage, it didn't work.

I updated Pleroma to commit 42d2c8d9 and tried MastoFE to see what was new in the update. I clicked on "Switch to Vanilla Flavour" to see what's the difference between glitch-soc and vanilla Mastodon, and the window is just blank. When I open the console in Firefox and Chromium (latest stable versions), it throws this error in Chromium ![image](/attachments/fa4bd532-87ea-4b96-8a3a-5d9056b7aa0a) and in Firefox ![image](/attachments/15d2c9af-1a5c-40cd-83ea-1d38f784862a) Since the window is blank, I can't really switch back to glitch-soc. I tried flushing cookies and localstorage, it didn't work.

image.png

13 KiB

image.png

10 KiB

lanodan commented

2019-04-12 04:37:10 +00:00

Owner

Yeah the flavour is stored in the backend, I wish it wouldn’t because of how vanilla is not supported.

In the meantime you can send a POST /api/v1/pleroma/flavour/glitch (I will add a GET one so it can be reset in the browser, even if that’s against what GET is for).

Yeah the flavour is stored in the backend, I wish it wouldn’t because of how vanilla is not supported. In the meantime you can send a `POST /api/v1/pleroma/flavour/glitch` (I will add a GET one so it can be reset in the browser, even if that’s against what GET is for).

lanodan commented

2019-04-12 05:18:02 +00:00

Owner

Wierdly if worked when I tested it before bundling… weird, should be fixed.

Commenting is not possible because the repository is archived.