Calling Developers!
We are reenergizing our code contribution process! Learn More

What are the Slack Archives?

It’s a history of our time together in the Slack Community! There’s a ton of knowledge in here, so feel free to search through the archives for a possible answer to your question.

Because this space is not active, you won’t be able to create a new post or comment here. If you have a question or want to start a discussion about something, head over to our categories and pick one to post in! You can always refer back to a post from Slack Archives if needed; just copy the link to use it as a reference..

My backoffice all of a sudden stopped working, nothing related has been changed. Ideas?

U03T08LE3CP
U03T08LE3CP Posts: 185 πŸ§‘πŸ»β€πŸš€ - Cadet

My backoffice all of a sudden stopped working, nothing related has been changed. Ideas?

Comments

  • Yuriy Gerton
    Yuriy Gerton Front End Technical Lead Sprykee Posts: 49 πŸ§‘πŸ»β€πŸš€ - Cadet

    Try updating the @spryker/oryx-for-zed dependency to 2.13.0 in the root package.json file.
    And execute commands
    npm i
    npm run zed

  • U03T08LE3CP
    U03T08LE3CP Posts: 185 πŸ§‘πŸ»β€πŸš€ - Cadet
    # docker/sdk cli npm run zed
    -->  DEVELOPMENT MODE   
    
    
    
      spryker-b2c-demo-shop@ zed /data
  • Yuriy Gerton
    Yuriy Gerton Front End Technical Lead Sprykee Posts: 49 πŸ§‘πŸ»β€πŸš€ - Cadet

    Then remove the node_modules folder and try to update to version 2.12.0

  • U03T08LE3CP
    U03T08LE3CP Posts: 185 πŸ§‘πŸ»β€πŸš€ - Cadet

    this executed successfully, but the original backoffice error remains. The sidebar items don't open

  • U03T08LE3CP
    U03T08LE3CP Posts: 185 πŸ§‘πŸ»β€πŸš€ - Cadet

    cleaning everything and rebuildin assets worked