Wix doesn't support long running processes like web sockets so what's going to happen here is the server will run for a short period of time and then terminate. Besides wix-realtime the other option you have is wix-http-functions https://www.wix.com/velo/reference/wix-http-functions/introduction . This can be used to define REST endpoints that your site can respond to.

If you're using Velo to do this you'll need to pass the lightbox context data that you can then use to set which image to display within the Lightbox's code. Send the lightbox data context when you open it with the data property: https://www.wix.com/velo/reference/wix-window/openlightbox Get that data context and then use that to set the image you want in the lightbox: https://www.wix.com/velo/reference/wix-window/lightbox/getcontext If you're not asking about Velo/JavaScript and this question is about EditorX only then you should ask here: https://www.editorxcommunity.com/

Per this section of the GCP article it sounds like "Visitor" may work for your case: https://support.wix.com/en/article/integrate-your-google-cloud-bigquery-database-with-your-wix-site#set-up-secrets

You can learn more details and signup here if you haven't yet: https://wixsaas.devpost.com/

Hey everyone! We’re excited to announce our first two Community MVP winners of the week who have also participated in the Wix Make-a-SaaS Hackathon. Congratulations to Kentin and Joris! Kentin has shown great initiative from Day 1, asking insightful questions that have helped the community get started on their hackathon projects; and been an active helper in our Discord. Meanwhile, Joris has also been a consistent helper on the Discord help channel, offering support and feedback to those who need it, and providing valuable bug reports that help us improve Velo for everyone. Remember, weekly Community MVP winners are eligible for a $200 prize, but only if they are also part of an eligible hackathon submission. So, if you want to be in the running for this prize, be sure to be an active community member and get started on your own hackathon project. Congratulations again to our winners, and let’s all continue to help each other build awesome SaaS products!

You can use this event handler to do something whenever the dropdown's value changes: https://www.wix.com/velo/reference/$w/dropdown/onchange

You can't dispatch custom events in Velo itself but if you're trying to do this for event based state management you could use something like https://mobx.js.org or https://github.com/shoonia/storeon-velo

For the first one queryCars() is also going to return a Promise since it is marked async. You can do the same await here: var carnr = await queryCars("opel"); For the queryCars2() it's essentially the same thing. Your .then() is a new Promise and it hasn't resolved so you can do var carnr2 = await queryCars2("opel"); Promises/async can take a bit to really stick so just keep at it and one learning source I like for all things JS is MDN: https://developer.mozilla.org/en-US/docs/Learn/JavaScript/Asynchronous/Introducing

Letting just anyone update content might be troublesome as any one user can now go and edit everyone's ratings. Some other ways to approach this: - Have this Data Collection admin only and expose a JSW endpoint that does the updating of ratings in the collection. - Have a Data Collection with Site Member permissions to add/read data and Site Member Author permissions to update it. Then do a wixData.query().count() on the data collection to get rating counts. Indexes can also help here with making counts faster. Or you can have a scheduled job that does the counts every day and updates the ratings. Just some ideas but I would really recommend against letting anyone change these ratings however they want to.

Please share your code so that we can see what the issue might be.

You'll need to query() the data collection directly with the same set of .eq() statements plus your filter for genes however that is defined. Then do a .count() on that. Essentially your Dataset doesn't contain all the data in your collection at any given time, it loads it dynamically as more data is needed to display. https://www.wix.com/velo/reference/wix-data/query

Can you share some example code? As long as you can get a postId on page load and then pass that to getPost in your backend it should work. Seeing some code would be helpful to debug what the issue could be.

You could use `wixWindow.getBoundingRect()`. I just tried and it appears to be aware of the scroll position for the base page/viewport and not the one that the Lightbox is in. https://www.wix.com/velo/reference/wix-window/getboundingrect

Looking briefly at this package it appears that it would need direct DOM access. Velo doesn't provide this access so this widget wouldn't work outside of an iFrame.

It does exist but you might be encountering this issue when trying to import this code on the frontend. This code is designed to only run on the backend of your website so you'll need to specify it there. https://www.wix.com/learn/courses/coding/velo-backend

You can use setSort() on your dataset to set an order: https://www.wix.com/velo/reference/wix-dataset/dataset/setsort

You can accomplish this (and any other validation) with the onCustomValidation event handler. https://support.wix.com/en/article/velo-about-validating-user-input-with-code https://www.wix.com/velo/reference/$w/textinput/oncustomvalidation

This doesn't appear to be a question about programming/coding with Velo/JavaScript. If so please use wix.com/contact

There's no way to set this default via Velo/JavaScript. Also if you're asking about Wix Bookings itself (ie. not a programming question) then you should reach out to wix.com/contact

It's hard to tell if this is the same issue without the code generating the issue or the full object/JSON but it's likely that this is a known issue and the team is currently working on a fix. At the moment the `mediaItem.src` you're getting back from `createOrder` is incorrect. It should be: `media:"wix:image://v1/id.jpg/file.jpg#originWidth=5760&originHeight=3840"` But it currently is: `media:"wix:image://v1/id.jpg#originWidth=5760&originHeight=3840"`