Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Riot is reluctant to reload config.json #7241

Closed
lampholder opened this issue Aug 29, 2018 · 2 comments
Closed

Riot is reluctant to reload config.json #7241

lampholder opened this issue Aug 29, 2018 · 2 comments
Labels
P2 T-Task Tasks for the team like planning

Comments

@lampholder
Copy link
Member

lampholder commented Aug 29, 2018

It seems really keen to rely on the cached version, which is a PITA when you make a change and wonder why it hasn't worked, and could also be a problem if we're hoping for changes made to hosted riot instances to propogate out without advising users to press whatever key chord is sufficiently refreshy to actually pull the fresh config.

@lampholder lampholder added T-Task Tasks for the team like planning P2 labels Aug 29, 2018
@mrdrogdrog
Copy link

mrdrogdrog commented Nov 20, 2018

I had the same problem just a minute ago.
My "solution" is a quick & dirty fix:

<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
</head>
<body>
<button onclick="localStorage.clear(); window.location='https://myriothost/#/login'">Click here to reset Riot and delete your loginsession</button>
</body>
</html>

It's a helper that deletes the browsers local storage for the current origin.
I placed it in the riot directory so it runs under the same subdomain as my riot instance.
A clean local storage triggers the download of config.json.

@t3chguy
Copy link
Member

t3chguy commented May 7, 2022

Closing in favour of #9784

@t3chguy t3chguy closed this as completed May 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P2 T-Task Tasks for the team like planning
Projects
None yet
Development

No branches or pull requests

3 participants