WixTurbo rollout breaking code

#WixTurbo
I’ve seen many people posting about code breaking randomly though it was previously working over the past couple of weeks, and now it has happened to me.

In my case, it broke some animations on items where I was using a hybrid GUI and code approach, but I was able to quickly fix that by making it all code.

However, the other thing it broke was simple html formatting on text and styling on boxes…
The code hasn’t been altered, and this stuff is so basic there’s no way it was my doing. Code on other pages has also been broken that’s more complex and I might update it once I figure out what’s going on, but this has got to be a bug on Wix’s side.

@yisrael-wix @yoav-wix @ohad-laufer @alexander-jdanov @chaim-kram Could you please inquire about this/inform us on progress?

UPDATE 4/4:

  1. Fix for failing #wixLocation links:
    Instead of :
const itemLink = itemData.link;
wixLocation.to(itemLink)

Use this, which is far better practice anyway:

const itemText = itemData.text;
const itemLink = itemData.link;
$w('#text').html = `<span><a href ="/missingUrlString+${itemLink}">${itemText}</a></span>`;
  1. Fix for #wixData connections: ???/Super inconsistent.

  2. Fix for broken animations: Use code only. Link to API.

  3. Fix for hidden/collapsed elements not being triggered: ???/f*ck around with your design and code until something works. I tried a whole bunch of other stuff but this was the only thing that worked in the end.

  4. Fix for iFrames: As @tabraham found, they’re not refreshing consistently on dynamic page load. So use postMessage without waiting for onMessage, or else try this to refresh the iFrame:

if (wixWindow.rendering.env === "browser") {
    var iframe = $w('#html1');
    iframe.src = iframe.src;
    await iframe.src;
    setTimeout(function() {$w("#html1").postMessage("yourmessage");}, 50);
    }

If you don’t have the time to parse through all this, feel free to contact me.

UPDATE 4/1:
1.#Wixlocation seems to be buggy because there is flat-out no canonical url, which can result in some weird behavior highly dependent on where you are pointing your links. It’s also affecting buttons without code in some cases.
2.#WixData connections are still failing on a page loaded with a url query.
3. I’ve corrected all animations, and it’s no longer an issue for me.
4. HTML formatting is fine, just be careful with template literals using wixLocation for reason above.

5. This is the most annoying. I’ve tried everything I can while maintaining my desired style choices, but no go. Code once working for triggering multiple collapsed/hidden elements has just sh*t the bed.

6.#WixVideo seems to be fully functional again.
7.#iFrames I’ve been putting off on fixing, but I’m pinning what appears to be @tabraham 's very helpful answer from down below. Will update once I’ve tested:

Previously, the recommended practice was to wait for a onReady message from a iFrame HTML component before doing a postMessage to send data from the page code to the HTML component.

But now, it looks like Wix is no longer reloading iFrame Html Components on Dynamic Pages – as such the onMessage event is not triggered except for the first load of the Dynamc Page (something similar is perhaps going on for the rest of the issues).

So the fix is to directly call postMessage without waiting for an onMessage event as was the recommended practice.

UPDATE 3/29: More things are broken now.
Here’s what I’ve seen on my end:

  1. #Wixlocation.to seems to be breaking on some sites because urls have changed, but the API is still going by the old urls. This can be fixed by comparing the url you’re being directed to vs the working url and manually correcting.
  2. #WixData connections are breaking sporadically if you’ve connected through the GUI, while connections through the code seem to be much more reliable.
  3. Animations are breaking if you have a combination of GUI and code on the same element. Easily fixed by making them code only.
  4. The HTML/style formatting broke for a day before fixing itself.
  5. Still having problems with triggering collapsed/hidden elements with onClick, not sure what the problem is there yet.
  6. #WixVideo elements aren’t playing when dynamically connected through the GUI or through code. This was tested with uploaded media and Wix stock media.
  7. #iFrames on dynamic pages are not working currently.

I’m all for faster load speeds, but Wix needs to say something about this. Customers can’t be hung out to dry, especially if they don’t know how to fix these sorts of things on their own.

6 Likes

I am having the same issue my many codes stop working automatically from last few day I had raised the complain on the forum but wix code team is not replying and I called the wix support about this but they say they don’t now about this.

3 Likes

Wix support has never helped me. Yisrael is much more reliable along with the other mods here.

2 Likes

Same issue at my end – published site code stopped working earlier today. Wix Support was unable to help. Interesting thing is that code still works in editor preview mode but live site does not work.

More details at this link (and posting here hoping Wix moderators will come across at least one of the threads)

#wixTurbo

1 Like

Same here, my wixLocation.to seems to have stopped working and now my site has ground to a halt and is essentially useless as the whole thing revolves around peoples accounts and dynamic pages using userId’s etc.

Anyone else experiencing similar problems due to the Turbo roll out?

Thread has been updated. Please post if you’re having problems as well, maybe we can help each other.

1 Like

I’m having problems with site elements that have animation and are hidden (without code) but this has been confirmed as a bug and the developers are aware of it.

3 Likes

David, thanks for collating all the problems being reported into your post above. I would add:
HTML Components within Dynamic Pages have also stopped working . They work fine within Editor Preview but do not work in Live Site (except for the first load). More details at this link

Have seen several variants of the above across the forum.
Thanks again and hopefully Wix responds soon – the radio silence from Wix is very disheartening.

1 Like

@tabraham Hmm, thanks for that. I have an iFrame on a dynamic page I haven’t tested. I’ll look to see if I’m having any issues with it as well.

Even just sending out a quick guide via email with easy solutions like the ones I posted would go a long way.

UPDATE: I tested and you were right. I added it to the list.

1 Like

Good to know, thanks shan. Do you have any thread for these updates or is it person to person communication?

1 Like

Update:

It’s definitely my #wixLocation. My wixLocation.to uses my members userId to navigate the site to their dynamic pages and it’s finding their Id numbers just fine.

  1. I’ve checked the URL’s of the destination sites and they match up. I’ve have even manually typed the URL from the saved database itself into the search bar and it all pops up just fine.

  2. The preview site is working just fine with the wixLocation.to links I have on it

Another issue to note, is that even the buttons that are connected to Data in my repeaters where I set it to “click action connects to…” don’t read either. I’m guessing WIX uses wixLocation.to to re-direct those as well.

Any more updates on wixLocation.to would be much appreciated when people get them. My site is now just a popup saying “we’re updating a few things”.

The strangest thing was, it was down for a day, then randomly the wixLocation came back online for about an hour and worked properly, then went back offline again…

Not great…

@skmedia Thanks much - debugging this issue I noticed that the iFrames are not being loaded on dynamic page transitions and the message handlers are also not being called for the iFrame (which essentially prevents the 2-way interaction between the iFrame and the page code).

I am actually stunned by the lack of response from Wix. What is the point of having a feature like Wix Code if no one is willing to offer timely support.

500 timeouts on dynamic pages most of the time, if the page loads at all - site cannot be reached most of the time. Repeaters are not loading 100% of the time or taking an age (over 30 seconds) to load

Hi, so I have a fix for one of the issues post above (#7 Iframe’s in dynamic pages).

Previously, the recommended practice was to wait for a onReady message from a iFrame HTML component before doing a postMessage to send data from the page code to the HTML component.

But now, it looks like Wix is no longer reloading iFrame Html Components on Dynamic Pages – as such the onMessage event is not triggered except for the first load of the Dynamc Page (something similar is perhaps going on for the rest of the issues).

So the fix is to directly call postMessage without waiting for an onMessage event as was the recommended practice.

$w.onReady(function () {
	$w("#dynamicDataset").onReady(() => {
		let currentItem = $w("#dynamicDataset").getCurrentItem();
		itemID = currentItem.itemID;

		let indicatorArray = ['id1', 'id2', 'id3'];
		remotedb_getData(itemID, indicatorArray)
			.then((dataPntArray) => {
			
			//Since wix is no longer reloading HTML component (and it appears as if
			//it is already present we can directly do a postMessage to the component.
			$w("#arrayChartHtml").postMessage(JSON.stringify(dataPntArray));
			
			//Strictly speaking the onMessage block is not needed (at least as of now) 
			//on the published website, but you may choose to retain it because 
			//otherwise the iFrame is not rendered in the Editor Preview mode. 
			$w("#arrayChartHtml").onMessage((event) => {
				console.log(event.data.type);
				if (event.data.type === 'ready') {
					$w("#arrayChartHtml").postMessage(JSON.stringify(dataPntArray));
				}
			});
		})
		.catch((error) => {
			console.log(error.message);
		});
	});
});

More details here at this link for background.

Updated once more. It’s clear people behind the scenes are working to stay on top of things, which I think we are all grateful for. Unfortunately, Wix’s PR/communication team does not seem to have their back or ours. I would not expect forum mods like @chaim-kram or @yisrael-wix to be the ones responsible for this, but the radio silence from Wix directly leaves them and people like @givemeawhisky to be the only helpful ones for Wix’s own customers.

Having the skills to fix this stuff on my own, it doesn’t affect me nearly as much as it affects people whose websites simply broke and got no response. I hope Wix learns to address these sorts of things as they happen rather than post-mortem in the future.

2 Likes

Same experience. Code works on editor preview but not on published site.

4 Likes

@tabraham I’m curious if you’ve tried to delay the onMessage() loading by adding some sort of timer, loop, or async function inside the iFrame to counter the fact that the dynamic page isn’t loading as it did before?

@mariedyth-gayas me too…

5 Likes

I am also having issues with things working correctly in Preview but not on the Published site. I have a moving header that was working for the past few months that no longer works. I have also connected a collection as a reference field to the built-in Members collection and now I can no longer access my live data for that collection. I certainly appreciate that Wix is listening to the community and adding functionality but some of these inconsistencies make it so difficult to work with. I consider myself a beginner to intermediate user so it is hard for me to tell if I am doing things the correct way when I do not get desired results and I am unsure whether it is my code or a bug.

1 Like

I get it poolshark, extremely disillusioned with respect to the available support with Wix. In the same breath equally grateful for the Wix Code community here.