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

[BUG] Error after upgrading to 1.1.0 #559

Open
ogmaxbone opened this issue Jun 5, 2024 · 8 comments
Open

[BUG] Error after upgrading to 1.1.0 #559

ogmaxbone opened this issue Jun 5, 2024 · 8 comments
Assignees

Comments

@ogmaxbone
Copy link

ogmaxbone commented Jun 5, 2024

So after i updated evershop via npm install @evershop/evershop@1.1.0
it gave me this error. Even if i downgrade to 1.0.0 it gives me same error but if i disable azure then it works again on the old version. Before azure used to work on the old version as well.
To Reproduce
Steps to reproduce the behavior:

  1. NPM run build
  2. npm run start

Screenshot 2024-06-05 at 9 02 39 AM

@ogmaxbone
Copy link
Author

also it says evershop@0.1.0 so idk if i upgraded correctly

@ogmaxbone
Copy link
Author

after i downgraded to 1.0.0 azure is working again and no error. however i want to upgrade to 1.1.0 to fix the blank checkout screen

@treoden
Copy link
Collaborator

treoden commented Jun 6, 2024

Hi @ogmaxbone ,

Are you using the evetheme? if yes please upgrade your theme. You can download the latest version from GitHub:

https://github.com/evershopcommerce/evetheme/

@ogmaxbone
Copy link
Author

Screenshot 2024-06-09 at 7 24 47 PM

I upgraded the theme and still this error, however the site runs now

@ogmaxbone
Copy link
Author

@treoden

@treoden
Copy link
Collaborator

treoden commented Jun 17, 2024

Hi @ogmaxbone ,

Are you using the Azure file storage extension? Please upgrade that extension too

@ogmaxbone
Copy link
Author

ogmaxbone commented Jun 29, 2024

Updated all the extensions, still error
Screenshot 2024-06-28 at 8 27 30 PM
Screenshot 2024-06-28 at 8 27 42 PM
Screenshot 2024-06-28 at 8 28 12 PM

@ogmaxbone
Copy link
Author

fixed it it was the error variable in my extension

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

No branches or pull requests

2 participants