Why not every element do not provide a label ? What abbout So we can cleary see, that we even have the option to change the S-Tag-Elemnt's label, ...but looking onto the VELO-API-DOCS.... ....there is no given possibility to manage the label of the Selection-Tags. WHY ???? So why the label-property is not included ???

ERROR: Request throttled, too many requests by RegisterIpThrottler On one hand it makes sense, but in my case i am using the registration-process to add a new BADGE to an existing user. Is there a way to bypass PROTECTION-FUNCTION, which turns on after several registration attempts? 1) And what exactly is the max limit of attempts to register the same member? 2) Or do the protection also woks, when registering several different members?

This error occurs, when you have to many fails while registering a user with same e-mail.... How to reset this, when the error occured??? 1) How to prevent such error? 2) How to reset such error? 3) What is the max limitation of failed registration-attempts? 4) Where to find all these info?

myElements [1].onChange(()=>{if(myElements [1].valid) {myElements [1].style.backgroundColor=colorValidityOk;} else{myElements [1].style.backgroundColor=colorValidityNotOk;}}); myElements [2].onChange(()=>{if(myElements [2].valid) {myElements [2].style.backgroundColor=colorValidityOk;} else{myElements [2].style.backgroundColor=colorValidityNotOk;}}); myElements [3].onChange(()=>{if(myElements [3].valid) {myElements [3].style.backgroundColor=colorValidityOk;} else{myElements [3].style.backgroundColor=colorValidityNotOk;}}); myElements [4].onChange(()=>{if(myElements [4].valid) {myElements [4].style.backgroundColor=colorValidityOk;} else{myElements [4].style.backgroundColor=colorValidityNotOk;}}); myElements [5].onChange(()=>{if(myElements [5].valid) {myElements [5].style.backgroundColor=colorValidityOk;} else{myElements [5].style.backgroundColor=colorValidityNotOk;}}); myElements [6].onChange(()=>{if(myElements [6].valid) {myElements [6].style.backgroundColor=colorValidityOk;} else{myElements [6].style.backgroundColor=colorValidityNotOk;}}); myElements [7].onChange(()=>{if(myElements [7].valid) {myElements [7].style.backgroundColor=colorValidityOk;} else{myElements [7].style.backgroundColor=colorValidityNotOk;}}); myElements [8].onChange(()=>{if(myElements [8].valid) {myElements [8].style.backgroundColor=colorValidityOk;} else{myElements [8].style.backgroundColor=colorValidityNotOk;}}); myElements [9].onChange(()=>{if(myElements [9].valid) {myElements [9].style.backgroundColor=colorValidityOk;} else{myElements [9].style.backgroundColor=colorValidityNotOk;}}); myElements[10].onChange(()=>{if(myElements[10].valid) {myElements[10].style.backgroundColor=colorValidityOk;} else{myElements[10].style.backgroundColor=colorValidityNotOk;}}); myElements[11].onChange(()=>{if(myElements[11].valid) {myElements[11].style.backgroundColor=colorValidityOk;} else{myElements[11].style.backgroundColor=colorValidityNotOk;}}); myElements[12].onChange(()=>{if(myElements[12].valid) {myElements[12].style.backgroundColor=colorValidityOk;} else{myElements[12].style.backgroundColor=colorValidityNotOk;}}); myElements[13].onChange(()=>{if(myElements[13].valid) {myElements[13].style.backgroundColor=colorValidityOk;} else{myElements[13].style.backgroundColor=colorValidityNotOk;}}); myElements[14].onChange(()=>{if(myElements[14].valid) {myElements[14].style.backgroundColor=colorValidityOk;} else{myElements[14].style.backgroundColor=colorValidityNotOk;}}); For example somehow push this though a LOOPING ? Somwone any idea of how to mage this in a more dynamic way, instead of coding it static onto the page for each of the event-triggers?

Found error in PAGE ---> on --> CHILDREN-PROPERTY..... let myChildren = $w("#page1").children; console.log(myChildren); Result.... This should normly not happen! Where is the whole OBJECT ??? That works, but not enough! let firstChild = myChildren[0]; console.log(firstChild); Please fix that bug! Thanks!

This happens, when doing to many registration-attempts How to reset this, when the error occured??? 1) How to p r e v e n t such e r r o r? 2) How to r e s e t such error? 3) What is the max limitation of f a i l e d r e g i s t r a t i o n - a t t e m p t s ? 4) Where to find all these info?

Sorry Amanda, i did not see your post.... What was the message?

Hello everyone! I have a problem to get my PayPal-REST-API to work. My problem is about the PayPal-Authentication-process using Wix-Fetch. Let's take this example here, where you try to get ACCESS-TOKEN from PayPal... export async function getAccessToken() { const response = await fetch("https://api.sandbox.paypal.com/v1/oauth2/token", { method: 'post', headers: { "Content-Type": "application/x-www-form-urlencoded", "Authorization": "Basic " + "" }, body: "grant_type=client_credentials" }); let jasonResponse = await response.json(); return (jasonResponse); } The "Authorization"-part in the "headers"-section, is the problematic part. I know what kind of type is expected and which parameters, but putting all the needed parameters directly into the CODE, does not work like it should. The authorization-process asks for a STRING-combination of.... "Basic " + "<Client-ID-Here> + ":" + <Secret-ID-Here> Should be something like... "Authorization": "Basic " + "Client-ID-Here" + ":" + "Secret-ID-here" Regarding the CURL-CODING... So, expected is a BASE64-encoded ClientID-Secret-combination separated by a ---> ":" 'Authorization: Basic {Your Base64-encoded ClientID:Secret}' Using POSTMAN, everything looks good and you get the ACCESS-TOKEN without any problems.... You get something like.... { "scope": "https://api.paypal.com/v1...., "access_token": "A21AAIESP7kstuC1o-5aIA8...", "token_type": "Bearer", "app_id": "APP-80W284485P...T", "expires_in": 32399, "nonce": "2022-09-12T15:05:08Z..." } ...including the token-type and the token itself. But when doing it directly without the usage of POSTMAN, you get a complete different response... ...something like.... Response: {...}jsonWixCode_Console_Table_ViewWixCode_Console_Copy_JSON url: "https://api.sandbox.paypal.com/v1/oauth2/token" status: 200 statusText: "OK" headers: {...} ok: true body: {...} bodyUsed: false size: 0 timeout: 0 _raw: [...] _abort: false Where you are able to find some buffered binary-data... So still a step missing?

Since there were these post here... I think many of you will have problems to work with the following APIs... 1) Authentication-API: login() onLogin() perhaps register() ,too. 2) CurrentMember-API: getMember() These are the two APIs which are involved in the described issue of the posts (on my opinion). And after some further analasying researches, i want try to explain the issued sutuation. To answer the following questions: Why does the new Member-API do not work 100%? What exactly is the reason for the instability of the new Member+Authentication-API? How to fix the problem, without beeing forced to use the old and depricated Wix-Users-API? Well to be able to explain the issued situation a little bit better, i have prepared a little TEST-ENVIRONMENT, which should simulate the issued situation, when it comes to the usage of the Wix authentication + wix-members-API. So give Mr-Persident a like, if he could help you to solve your issue ....😆🤣... How to use the example to see the ERROR? 1) Login with the given LOGIN-TEST-ACCOUNT. Take a look onto console. Log out again. 2) Activate the SWITCH of the currentMember-API and do the same again, do not forget to take a look onto the given CONSOLE-LOG-RESULTS! Log-out again! 3) Now activate both SWITCH-BUTTONS to activate all included APIs and run the test again. Take a look onto given CONSOLE-LOG-RESULTS! To understand what this example wanted to tell you --> you can show additional information by a click onto --> SHOW-DETECTED-ERRORS-button. So, i hope this example makes the issued situation more understandable for everybody. I already tried to explain this in several different posts, but i think i was not able to give a precise and good understandable answer. One person was already able to use this knowledge as a workaround... Back to the questions.... Why does the new Member-API do not work 100%? Well, like you perhaps have seen in the example, you don't have any chance to get the ID after login the direct way. The authentication.login - function.... https://www.wix.com/velo/reference/wix-members/authentication/login import { authentication } from 'wix-members'; $w('#login').onClick(async () => { const email = $w('#email').value; const password = $w('#password').value; try { await authentication.login(email, password); console.log('Member is logged in'); } catch (error) { console.error(error); } }); Don't give you anything back as result, after you have logged-in. Because of that, you will have to use (additionaly) --> the getCurrentMember() - function/API.... https://www.wix.com/velo/reference/wix-members/currentmember/getmember import { currentMember } from 'wix-members'; // Sample options value: // { // fieldsets: [ 'FULL' ] // } currentMember.getMember(options) .then((member) => { const id = member._id; const fullName = `${member.contactDetails.firstName} ${member.contactDetails.lastName}`; return member; }) .catch((error) => { console.error(error); }); To get informations about the current logged-in user. But even this do not work --> 100%. The example demonstrates exacly this issue. Using the following SETUP... ...you still won't be able to get the --> ID <-- of the current logged-in-member .... ...because --> .then((member) => { <-- do not provide any results after loggin! !!! AND THIS IS PERHAPS EXACTLYTHE POINT, WHERE THE ISSUE STARTS !!! !!! And here --> onLogin()-function comes into game !!! https://www.wix.com/velo/reference/wix-members/authentication/onlogin import {authentication} from 'wix-members'; authentication.onLogin(async (member) => { const loggedInMember = await member.getMember(); const memberId = loggedInMember._id; console.log(`Member ${memberId} logged in:`, loggedInMember); }); Using the example and log-in with both activated functions, the login-starts to work and gives back USER-ID and all other data as RESULTS.... @Marlowe (Wix) Perhaps you can connect to the right developement team, to test my example and proove my theoretical thoughts. My conclusion: Either the VELO-API-DOCs have to be changed, or the API itself has to be optimized --> regarding either the login()-function of the --> AUTHENTICATION-API, or regarding the --> getMember()-function of the --> CurrentMember-API (Members-API).

How to understand this error? The repeater works just fine, and is feeded by the result-items of a DB-Query. Is this ERROR neccessary? let collectionData = await get_AllCollectionsData(); .then((res)=>{//console.log("RES-COLLECTIONS: ", res); if (res.items.length>0) {console.log("Collection-Data found!"); let items = res.items; return (items); } else {console.log("No Collection-Data found!"); return ([]);} }).catch((err)=>{console.log(err);});

Is the query-limitation on Wix-Stores/Products = 100 ? 1) Query-50 (standard-limited-query): 2) Query-100 (increased query-limit to 100) 3) Query-101 (increased query-limit to 101) !!! What's going on ? No 1000-limit ?

Wix whats going on? This simple code do not work anymore, just few hours ago, everything worked well.... $w.onReady(function () { $w('#swtReverseView').onChange(()=>{console.log("Switched!");}); }); This is a simple code for a - - > SWITCH-BUTTON. This is (not)working on a totaly blank TEST-PAGE. And here the RESULT.... And in PREVIEW-MODE --> everything OK! @Marlowe (Wix) Could you pass this on to your team?

Surely today will be my lucky one! 😅😁 Wish me luck --> I should play a round of the lottery today!

What does tell me this error exactly, which i get since today, without have done any changes on my editor?