The elements which were set on the first rendering cycle are reverted to default values on the second rendering cycle

Ask the community
,
1

Hello Wix team,

In last days we observe major issue with rendering cycles.
The problem is following:
The elements which were set on the first rendering cycle are reverted to default values on the second rendering cycle.

Actually it causes all performance improvements which were done with regards to rendering cycles to work wrong, since all the page elements which were rendered on backend have now the default (placeholder) value.

Please take a look at the following site as example: https://dmitrybi32.wixsite.com/issue-reproduce/render-cycle-issue

The code you may find in the page is following:

import wixWindow from 'wix-window';
$w.onReady(function () {
	//TODO: write your page related code here...
	if(wixWindow.rendering.env === "backend") {
			$w("#res1").text = "Backend";		
	}
	else if(wixWindow.rendering.env === "browser") {
			$w("#res2").text = "Browser";
	}
});

You may see that once

$w("#res2").text = "Browser";

had run, $w(“#res1”).text gets the default text value set in editor.

In addition, we observe Timeout (500) error sporadically on some of the pages, which wasn’t happening before.

Please assist with solving the problem asap.

Thanks,
Dima

2 Likes
2

Hello Dima,

This seems like a bug in our side.
Thank you for the well explained scenario, and for the issue reproducing site, I’ll pass these along.

Thanks again,
Idan.

3

Thank you, Idan.
Would be great to hear some update on this.

Thanks,
Dima

4

Gladly.

Investigation has already started.
can you please also provide the actual site which you’ve experienced the same behavior with? It can be helpful.

Thanks,
Idan.

5

Hello Idan,
The actual site is in work now, as well it harder to point to the problem I observe.
This is the reason I created dedicated reproduce site, with minimal amount of code, to see clearly the discussed issue.
On the test site the issue reproduces 100%, so I don’t think there is a need in another reference.
If you have any specific questions I will be glad to help if I can.

Thanks,
Dima

6

Hi @idan-attias !
Is there any update on this issue?
Thanks,
Dima

7

Hi @_dima ,

The issue is still in progress, I will let you know as soon as I have an update.

Thank you for your patience,
Idan.

8

Hi @_dima ,

Sorry it took such a long time to get an answer.
After a long debate, it has been decided that in term of product this feature needs to be reconsidered, as it can be defined in a several ways.

I suggest using a slightly different version of this feature, as shown here .

Again,
Sorry for the delay and the inconvenience.

Liran.

9

Hi Liran,

However warmupData is the feature I’ll take a look at, I tried to use the rendering cycle 1 for less complicated purpose - just to set some element which already accessible on 1st rendering cycle (text for example). But since it is reverted on the second rendering cycle, I have to set same text twice, which look to loose the purpose of this optimization.
Is WIX’s direction to redesign this feature? Or fix the current misbehavior?

Thanks,
Dima

10

Liran,
I tried warmupData feature you suggested, but looks it doesn’t work. At least I didn’t succeed to use it properly, this property always returns null.
I see that similar issue was already reported, but never answered by WIX:

Dima

11

I’d like to note I have the same issue. In my case it’s surrounding expanding/showing elements in the onReady() that are collapsed/hidden by default.

When I set it to only expand/show during renderCycle 1, and it has two cycles, the net effect is the elements remain hidden/collapsed. I suspected the same issue that the second cycle overrides what’s done in the first.

I do agree this nullifies some of the value that server-side rendering can offer.

It’s been a few months since the last post here. Is there any update on the direction Wix plans to go?

12

Hi WIX team,
Any update on this bug? I still see it happening.
Thanks,
Dima

13

Hello Wix,

I’m echoing each of the issues that’s been brought up in this thread.

As of May 21, 2019, any elements that I set during the backend render revert when the browser render occurs. In addition, warmupData always returns null.

What is Wix’s plan to fix this Corvid issue? I am attempting to speed up the loading of my website, and Corvid’s published feature for doing so does not work.

Thanks,
Roger

14

I have a similar issue with filter values stored in session, when clearing the filters on the 2nd render cycle it loads de dropbox value and not null.

15

I understand that no update is expected, since according to documentation both renderCycle and WarmupData are deprecated and will no longer work as you expect them to:
https://www.wix.com/corvid/reference/wix-window.rendering.html

16

Yes both of those have been deprecated, however you can still use the env function.
https://www.wix.com/corvid/reference/wix-window.rendering.html