Hi,
I have been testing out the new editor X and have built a new website. The site has lots of custom code, some being complex. Upon logging in around 1 week ago I found an error on the developer console when my ITEM page is loading. This is the only page with the error
‘Could not fetch initial items from server TypeError: Cannot read property ‘items’ of undefined
[object Object]’
I have tried to find the issue through some diagnostic work but even if i remove all of thew code from the page, back end and site code, it still shows this error. I have also went pack 14 days via the site history and the error still shows. The page loads and functions fine but has this error. To my knowledge this wasn’t showing during the previous editing session. I have been in touch with the team at editor X, who say that it has been resolved, but it still persists and they said with any coding related issues to use the forum.
Any help would be much appreciated from any of the Wix team. Here is a link to the URL
https://mccallstephen1.editorx.io/scottishrocknwater/courses/Scrambling/Skye%20Cuillin%20Ridge%20Guided%20Traverse
Thanks
Stephen
I took a look, and I gotta admit that there’s a whole pile of code to wade through. Understand that we are unable to debug or rewrite complex code and page configurations. If you feel that there is a bug in Corvid, then please try to create a test page with the minimum scenario in which the problem appears. This will greatly us investigate the issue properly.
Hi Yisrael,
Thanks for getting back to me so quickly. I have tried to recreate the issue. If I remove ALL of the code the error still shows.
Even if I take the site history back to the first day of starting it still shows this error. It wasn’t there until 1 week ago… I don’t know what else to try, I have tried to find the error myself for around 16hrs as I was sure it must’ve been something that I had done at my end. After this time and findings it seems like there must be a bug?
@stephenmccall Hmm… Does the page work in spite of the error? If so, it might just be a “scary message”. That’s a technical term for messages that are displayed by the developers for their use, but that are not indicative of any “real” problem.
Thank again, if the page does not work, then this could be some sort of anomaly introduced in a new release of the system.
Let me know which scenario so I can direct this to the correct smart person at Wix.
@yisrael-wix yes it still works normally and all code functions as it should. It doesn’t provide confidence, even if it is just a ‘scary message’!
Let me know if there is anything that I can do in order to help diagnose the issue at my end.
@stephenmccall First of all, I’m glad that it’s working.
However, don’t let the “scary message” get to you. Realize that EditorX is a new product and the devs need to embed this stuff for diagnostic purposes. As someone who spends much of the time working with users, I’m sensitive to this issue and I’ve been encouraging a kinder and gentler way of displaying diagnostics. I’ll pass this on, but stay calm and don’t hold your breath.
@yisrael-wix OK, I will see what happens in due course and ask for any further help if needed. Thanks for your time
@stephenmccall I forgot to mention that Preview runs a bit differently since it’s sort of running inside the Editor. That creates a separate scenario and challenge for the devs. They have to be able to render the site both in the Live Viewer, and within the Editor. We should have compassion. 
