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

Medusa doesn't start with release 0.2.7 #4767

Closed
Rwanou88 opened this issue Jul 27, 2018 · 9 comments
Closed

Medusa doesn't start with release 0.2.7 #4767

Rwanou88 opened this issue Jul 27, 2018 · 9 comments
Labels

Comments

@Rwanou88
Copy link

Rwanou88 commented Jul 27, 2018

Describe the bug
Medusa doesn't start

To Reproduce
Update Medusa with the last release 0.2.7.

Expected behavior
Since I have updated Medusa, I have a black screen when I want to access it.

Screenshots
error
ressources
warning

Medusa (please complete the following information):

  • OS: DSM 6.2-23739 Update 2
  • Branch: master
  • Commit: b733355

Logs:

``` ```

Additional context
Nop

@BaukeZwart
Copy link
Contributor

I found that when starting Medusa in Chrome's Incognito mode it works.
For now I use that as a workaround.

@p0psicles
Copy link
Contributor

@OmgImAlexis this seems to be an issue with the browser local storage. We really need to fix this. Can you look into this?

@medariox
Copy link
Contributor

Clearing the cache should fix this, see: #4754 (comment)

@Rwanou88
Copy link
Author

Rwanou88 commented Jul 27, 2018

It's seems to be a cache problem, working on incognito mode ;-)
Working fine now I cleared the cache.
Thx for your help !

@p0psicles
Copy link
Contributor

Yeah, but when restarting medusa, it should provide you new js files.
Also the mako cache should have been refreshed. I asume you tried restarting medusa, and closed all tabs (as in not reusing old tabs). Then the only item I can think of that will survive that, is the local storage. Local storage is not shared with incognito tabs.

@OmgImAlexis
Copy link
Collaborator

@p0psicles isn't much we can do. All users will need to clear all caches and we can't really do that programatically.

@p0psicles
Copy link
Contributor

p0psicles commented Jul 27, 2018

Can you go through it with @Rwanou88 so we are 100% sure how to resolve this issue? Then we at least know for sure.

@OmgImAlexis
Copy link
Collaborator

Working fine now I cleared the cache.

Check the comment, they updated it.

@p0psicles
Copy link
Contributor

Sorry I missed that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants