I am having trouble getting server side rendering to “stick”
We noticed that any code executed on the server side is not persistent. ie, the second the browser renders, it replaces the SSR data by the interface default.
We thought it might have been something to do with the big art gallery site we’re building, where we want to use SSR to improve our load time on repeaters.
So we built this little test site to check. You’ll see the SSR flicker and then revert to default. I’ve also written the code on screen so you can see what’s driving it.
Can anyone replicate, or teach me a better methodology?
https://kbwebs.wixsite.com/serverrenderingtest
#SSR #ServerSideRendering #Repeaters
That is one weird sample. Reverting to the default prevents the whole idea of SSR in the first place. Let me invite @yisrael-wix from Wix and @uval-blumenfeld-wix that has the connections to make sure this question in investigated and answered to you as it is beyond my knowledge.
1 Like
Requiring Wix help please.
Will bump the team hold on
Hi,
The reason you get this behavior is by design - changes to elements done on the server side rendering are reset during client side rendering.
In order to persist the changes done on first render it’s advised to use warmupData and make sure that in case the page is in fact rendered twice (server + client) all changes done on the first render are re-applied on the second one.