saleor / saleor-storefront

A GraphQL-powered, NextJs-based, PWA storefront for Saleor. IMPORTANT: This project is [DEPRECATED] in favor of saleor/react-storefront soon to become our default demo and storefront starter pack.

Home Page:https://demo.saleor.io/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Product information not updating

pnpaes opened this issue · comments

I am using the store front 3.0.0-b.2.
The product details page is not updating it automatically when price or other product information changes int he dashboard.
I can try to bust all local data or use private mode and it is the same behaviour.
It only updates if I stop/start the next server...
Seems that some static information is being rendered when the server starts and the product page doesn't fetch "fresh information". If i look into the browser network there is no api request in the product page, only in the product listing.
Which means the product listing get the latest updated price, but not the product page itself.

Is there a configuration that I can adjust or something that I can tweak to avoid that?
Locally i am just running npm run startso there is not export build with static html being generated.

Appreciate any help here.

Same here using the same version of store-front

Products are not visible under the category, shows zero records

Try experimenting with the INCREMENTAL_STATIC_REGENERATION_REVALIDATE environment variable. Per default I think it is set to 60 minutes (3600 seconds). After that time, if you refresh the page, the data get refreshed. This, however, only works for the next server. In case you use the Dockerfile as provided in the repo, it will use a static export of the site and serve it with an nginx server and never refresh any data.

Oh dear. Sure that you tried it with "next start"? For me it works locally. But when deployed with docker, I get error messages when it tries to refresh the product pages: At least one of arguments is required: 'id', 'slug'. I think I'll open up a new Issue for this - although it feels like this repository is somewhat neglected, considering the activity in the other two repositories..