Hi Raj, I believe what you might be looking for is the onChange function of the dropdown, (onChange). Once you create this event handler, evertime the procedure is changed, you can run a piece of code to change the price drowdown below. If you want to change the Procedure prices using code, you'd be looking to use the .options property of the Dropdown element - https://www.wix.com/velo/reference/$w/dropdown/options

Can you share the full code on masterPage.js? If it was working, and you changed nothing at all, and it is no longer working it's possible that you have added some other code, maybe an import, that is causing an issue with other code which runs after it. It could also explain the error with $w(elementId).hide(), since the site code JS file always runs before the page code.

That looks very strange indeed, and may have been a Wix specific issue. Has it cleared up, and have you gotten to a solution?

The installer links for development apps can sometimes expire or become inactive. Also my friend Salman had moved on to other pastures since then. If you're looking for a simple Custom Elements alert component, I have one under development I can share with you

To add, since you're working through multiple promises before you get to your final call, you might be better off using the async/await syntax, which will reformat your code to be easier to understand and less cluttered with callbacks. So in your case it would become: import { fetch } from 'wix-fetch'; import wixWindow from 'wix-window'; const API_KEY = "aaabbb"; $w.onReady(async function () { const httpResponse = await fetch(`https://extreme-ip-lookup.com/json/?key=${API_KEY}`, { method:'get'}); if (httpResponse.ok) { const json = await httpResponse.json(); const loc = json.countryCode; if(loc === 'MX') wixWindow.openLightbox("MexicoLightbox"); } }); A couple of other things you can do : • Ensure that the API call is being correctly received by the Fetch function.

Great!

Sure, you can tag me in the #help channel on Discord at @ChristopherDerrell

It all looks good to me from the screenshots. Is it still not working in either preview or live?

Hey Matt. Just to start, if you'd like to copy code from the Database, you could pull it from the collection using wixData, and copy it using Wix Window's Copy To Clipboard - https://www.wix.com/velo/reference/wix-window/copytoclipboard. This allows you to avoid passing data back and forth between the site and your HTML element using postMessage. If you need it to be done within the HTML element, you could use the Async Clipboard API to do so. It works the same as Wix's Copy To Clipboard, but you access it using the native navigator in your iframe. - Demo - https://www.w3schools.com/howto/howto_js_copy_clipboard.asp - Documentation - https://developer.mozilla.org/en-US/docs/Web/API/Clipboard_API

Hi Luke, it might actually be better for you to start a new thread, since this question is over 2 years old now, and your scope is a little different.

No problem, major Kudos to you for implementing it the right way. 👏

https://www.wix.com/velo/reference/wix-data/updateHey José, You should be able to perform the update functionality once you have the full original object being updated (which I see the fields for in your screenshot), and the wixData.update function.

Hey there, What you're looking for is the sessionStorage API provided by Velo. That will allow you to check whether this is the visitor's first time on the site during that session or now. In your masterPage.js file, you'll want to check if they've visited before. If they haven't you'll show your lightbox and set the visited flag to true using the session API. Something like //masterPage.js $w.onReady(()=>{ cosnt hasVisited = session.getItem('visited'); //If hasVisited is null, then this is there first time. //If it has a value, then they have been on the site for this session before. if(!hasVisited){ //Checks if hasVisited is null using a NOT operator showLightbox(); //Your code to show the lightbox. session.setItem('visited','true');//Takes strings as values } }) The showLightbox() above is pseudocode, and would be replaced by your own code.

Image editing can be a complex sport. Generally, you have two methods, either using the browser canvas, like in your example above, or using WebGL. Canvas is part of the HTML5 standard so it works in browsers with regular JS & HTML, but direct access to DOM elements isn't available out of the box in Velo - e.g. const canvas = document.createElement('canvas'); won't work in your page code. You can approach it a few ways, but any method for image editing will require research. 1. Use Custom Elements to create a component with DOM access, which will get your code working with some modification 2. Use an npm library like node-canvas to simulate access to the canvas in your Wix backend code 3. Look for another editing library that makes use of buffers to do image editing, which is just the raw image data. Not leaving you high and dry, here are some resources to get started. Common Image Manipulation Libraries (you'll have to make sure the are available in Velo, or request them) - https://medium.com/on-discord/nodejs-image-manipulation-libraries-43a3f955cc67 Node Canvas - https://www.npmjs.com/package/canvas

It's good that you tried both the deep copy newItem, and the newProperty way, skips a couple debugging steps. I'm not seeing in your code where you actually tried assigning an object to newProperty, to see if that would work as opposed to overriding it. Based on the code above, it'll always be {}

Hey Steven, I've had to do something similar before with a dataset. Are all of your files pointing to the same referencedItemCollection? There are a couple of things you could do since the dataset doesn't natively give the referenced item. 1. You can .query() the full Referenced Collection, and store it locally in an object. That way you can more quickly reference each of the IDs. It's kind of like creating your own Cache of items for quicker retrieval. 2. You can set up a data hook for afterQuery that will create the object for you, and should come up in the dataset's query result. Both of these options should be a bit quicker than querying the referenced collection each time.

@Baris Onat To answer your accessibility question, both Wix editors' support accessibility out of the box. In both EditorX & Classic Editor, Wix does use the native HTML under the hood for the dropdowns. It's setup nicely for accessibility already. I do have some news for you though. If your goal is a must that you self-host the website on other servers, Wix would not be the platform to facilitate this. The hosting of the sites is part of the package when you get the rest of the ability to develop using Velo etc. I've had to make this choice myself, and keep finding myself choosing Wix hosting for most things :). Hope this helps you get to your goal.

Good catch! (pun intended). For the record, if you're using async/await in your code, you don't need to use .then() and .catch(), as it can be written a little cleaner, in my opinion, using await without the then callback. For example, the above code block could look like: try{ const queryResult = await wixData.query("Pairings") .eq("pod", gameData.pod) .eq("playerID", gameData.player) .eq("opponentID", gameData.opponent) .or(myQuery) .find(); if (queryResult.items.length <= 0) { //I think we can replace this with query.get instead of .find > check this later errorMessage("Error QP001: There appears to be a problem with the data that was submitted, please contact the system administrator as this error should not happen."); record.error = true; } else { record.dbRecord = queryResult.items[0]; record.submittedRecord = checkExistingScore(gameData,record.dbRecord,status); if (record.submittedRecord.error) { errorMessage(record.submittedrecord.error); record.error = true; } } catch(err){ errorMessage("Critical Error QP002: Pairing data does not exist. Contact the administrator as this should not happen.",err); }

Hey Marko, As you mentioned, what you're changing when you rename the field is really the label. So when you rename the field using the UI to "Building Number", it's keeping the original key as an identifier. Using the UI, I don't think there's a way to change the key as yet. What I had to do with labels (similar concept) was create a new label with the desired key using Find or Create Label and if you want, you can rename it right afterward using the returned key. In your case, if you want to migrate to a new CRM Custom Field (Extended Fields in the API), you could query all of the contacts, and run an update for each of the contacts with the new Custom Field.

If the lists of items are completely different, you could try using the Multi-State Box to do the switching in your video. That way there would be no delay between them. • https://support.wix.com/en/article/velo-setting-up-your-multi-state-box • Example/Tutorial - https://support.wix.com/en/article/velo-tutorial-working-with-multi-state-boxes-and-code As to why that would be happening, I'd check if you see it happening on the live website as well.