Hi
last months i was so happy work with wix and i think its great product.
But last days was very strange. I had problem with error which i find out after few nights of work. At wix support they didnt answered me for few days and after lots of remainders they said that better i ask at wix code forum. So at wix forum nobody knows what is happening and its problem becasue if i have site i get money from , my clients would get crazy. Last night i started rebulding page after page to avid error. but its not solution. there is a bug and
if anyone is intrested read exacly where.
- one day my page started get like 100-200 errors at some pages(i didnt touch those pages).
- after lot of time searching i found function disable() and enable() is responsible for it
- suddenly some of elemnts on page that has id get " Cannot read property ‘compId’ of undefined. " and in live mode much more different
- i can show at paga KARTOTEKA. If someone has access to my editor. Go there and switch on function “input 20” disable(). You will see error than. If You go to PRZEBIEG IMPREZY page You will see 200 errors becasue i didnt have time to check it. Switch off // function disableall() and enableall() and there is no errors :). At KARTOTEKA page its easy becasue only 2 elements make arrors so maybe some savy developers will find out whyonly those.
- if someone is more intrested i can show exacly where, chat or by phone
After considerable searching, I discovered one of the components, #button71, in a repeater. The reason that you are getting the message “TypeError: Cannot read property ‘compId’ of undefined” is because the component ID (compId) is undefined. There is no #button71 because the repeater has not yet been populated. And furthermore, even if the repeater had been populated you cannot address repeater item components using the global $w context selector.
Repeater components are managed only in the following functions: onItemReady( ) , forEachItem( ) , and
forItems( ) . The components in a repeater item are accessed using the $item context selector.
The errors that you are getting are logical and are not errors in the system. They are logic errors from your code attempting to access components that do not exist. Once the repeater is populated, the components in the repeater items can be accessed using the $item context selector.
See the Repeater API for more details.
In KARTOTEKA PAGE button71 is not inside repeater therefor there is $w. Input20 is inside and its a problem as I took it out and no errors as You said
so when i use $w(element1) it doeasn mean i diable all elements1 in repeater? With $item i understood i acces palticular one in event for example If so i understand my mistake and i’m sorry for bothering You.
But trust me i would never give my site to people with such errors. I was giving pages one after another and for sure there was no errors. 2 Weeks ago i finished page to put peaople to tables at party and it was going smooth and beautiful and later errors. They appeared like weak ago for all pages therefore i was angry because if there is error during making page i know its my fault and i look for it. But if they appear after month without touching them its strange and scary. Becasue means i need to to be alert all the time and check it.
Understand me a bit 
If You are in Poland any time You are invited to CEGLARNiA
Hey Krs,
Well, here’s a screen shot of the Repeater, and it appears to me that #button71 is inside of the Repeater.
I will ask QA why this happened to you all of a sudden. It might be that development fixed some incorrect behavior that was working for you, and now it won’t work at all for you causing a problem.
Regarding your question, “$w(element1) it doeasn mean i diable all elements1 in repeater?”. Well yes and no. I did this myself on one project and was told that “you can’t really do that”. However, it worked fine for me. Maybe this is what was fixed and now it’s longer possible. I have to go back to my project and see if it’s broken.
I’ll let you know if I hear anything.
Thanks for the invite. Looks like a beautiful place! Who knows, maybe someday we can share a few beers. 
I was writing before about Karoteka page and 71 was outside in Przebieg Imprezy of course is inside. Now i will find all such behaviors and will change it. At least i know what i need to change and dont have to rebuild everything I did it at all pages becasue people are clicking like crazy when site is slow and when they click during function makes errors. Thanks again for help
Well, on the Karoteka page, I see that #input20 is in the Repeater. If I comment out the line
$w(‘#input20’).disable();
then the compId error disappears.
Tell me something… Is the site still working even though it’s getting these errors?
Hey Krs, I just tried my site that uses $w in order to access all instances of that component in a Repeater. It seems that something was “fixed” and that this is no longer available. It makes sense really to no allow this as it is in fact correct. We were both using what could be considered a “hack”. That is, using something that’s not “official” to get something done more easily.
Sorry, but it looks like we can no longer use the global $w context selector to access components in a Repeater. Now I’ve got to redo my site. 
Yes Site is working but some of my clients tell they have problem. But most of my clients are wedding couples and i coudnt find out what because its difficult by phone to find out what when someone tells me “its not working” - What- “i dont know” At safari and mac was some compliens but i’m not sure becasue some people dont know what system they have and what browser. For sure it was slower becasue everybody compliend. At chrome it was working. But i dont want to leave it like this because one day some browser can treat it like dangerous and stop for sure. At One ofmy my page where i have 100 elements gets 500 errors and i will not risk. greetings
in wixcodeapi there is sentence that what we did is possibe. I think somone should change it then. CHris 
Yes, I know. I’m currently investigating this issue with the help of the developers. One of my sites has also been affected by this and I’m trying determine the exact scenario so the developers can do their thing.
