This is happening once in every 5 page loads #wixTurbo
The resource https://static.parastorage.com/unpkg/requirejs-bolt@2.3.6/requirejs.min.js was preloaded using link preload but not used within a few seconds from the window’s load event. Please make sure it has an appropriate as value and it is preloaded intentionally.
Is this something we can fix or only the Wix Dev team can from their side?
-Shan
I am also seeing this quite a bit. Did you ever figure out what is causing this?
EDIT: when this happens, the page goes white and stops loading so this isn’t exactly trivial. Any information about this would be great. If this happens when a new user comes to a site they are lost forever.
Same issue, any mitigation ?
@yangmael From what I see this is still happening just as frequently if not more than it was when this was posted.
Any solution to this? Any time I add even a single simple line code to the page, this error comes up and the code does not execute.
I am also getting this error. It works fine in preview mode but when the site is published, the error comes. I use repeater and populate its elements from database through code
“The resource https://static.parastorage.com/services/editor-elements/dist/componentSdks.db94e76e.bundle.min.js was preloaded using link preload but not used within a few seconds from the window’s load event. Please make sure it has an appropriate as value and it is preloaded intentionally.”
Does your site work correctly? If so, it might just be a message for the developers to monitor certain actions.
If your site is not working correctly, you will need to provide more information in order to get assistance. Please explain what you are trying to accomplish, what works and what doesn’t, and share any relevant code in a code block.
My site is not working correctly now. My page that has problem is:
https://gitaganapathy.wixsite.com/teststhira/hybrid-course-detail
The elements on this page are inside a repeater and are populated from different collections. It was working fine until the latest publishing.
I added some more elements to the existing page and to populated them, I added some fields to the existing collection, added two new collections and updated the page.
In the preview mode, the data is getting populated, working good.
But after I published and synced the sandbox to Live and visit the page from browser the behaviour is not the same.
The new collection and the old updated collection (schema change - new fields) data are not getting displayed though the console message shows that the values from the collections are available at the page.
If you see the page, the initial part, which is older one, is getting populated from the collection, but the newly added part with elements populated from new collections and updated collection is not showing up
@gitaganapathy I don’t know what you mean by “initial part” and “newly added part”.
I don’t understand what you are doing with #courseDetailRepeater. As far as I can tell you only have one item. What’s repeating?
One thing I see is that you have two errors flagged:
Hi! Thanks for the quick response.
First, I never got the errors that you have highlighted. Any coding error at my end I would first fix before coming for help. In the preview mode, I got no errors and all were working fine. Only when published, i found that for the newly added elements the data is not getting populated.
What I meant as the initial part is, this was page published earlier working without any problem, where the data from the database is populated in the elements which you can observe from the page. The new additions to the page is where the data is not getting populated. You will find blank table rows, the text box containing default initial text, the images are initial default ones.
I am using the repeater as per the suggestion in one of the discussions in this forum which I came across when I was stuck earlier while with populating the elements from database. The page containing elements populated from the database went blank. It was suggested to have a single item repeater and keep the elements inside the container and access them.
I had problem with corvid last month also, the site which was working fine started behaving unexpectedly. But in the preview it was all perfect. Then after sometime, a few days, without my doing anything it became alright. I suppose that was during the time some upgrading was happening in corvid.
The problem i am referring today has a similar behaviour. Works in preview mode but not in live.
