Hi, We recently got a similar inquiry via our contact form, not sure if it is you? Either way - we added a new tutorial to the docs that tries to address the scenario you asked about. You can check it out here: https://www.notion.so/PDF-Generator-d564022a26d548a79c5fdb709663e9be#0fea0672c4c3807a986fc71e89bd70b0 Best, Eitan

Hi Daniel, Sure thing, can you please provide the details of how you set up the "Wait for page data" and corresponding widget? At what point did you begin using the Widget? Best, Eitan

Ahh I see.. To my understanding "customLineItems" is unrelated to the "Custom Catalog SPI", rather for creating line items on the fly that don't exist in a any catalog. Glad to hear you figured it out though!

Hi Naba, If I understand correctly, your issue is most likely this: link = document.createElement('a'); link.href = pdfDataUri; line.download = 'CharacterBackstory.pdf'; document.body.appendChild(link); link.click(); document.body.removeChild(link); Wix doesn't allow DOM manipulation in the page code/client side/frontend. Assuming your url is a download url you can navigate to it using WixLocationFrontend. Otherwise you may have to upload the PDF to Wix and download it from there. Best, Eitan

Hi James, Velo is based on JavaScript, so any string manipulations you want to do would be in that language. The split() method is likely what you are looking for in this case: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String/split Hope that helps! Eitan

Hi Hassan, If you would like a scholarship for the Udemy course, please reach out to support@thewixwiz.com and explain your situation. Best, Eitan

Hi Calin, I mention this API in the most recent What the Wix?? post. It is not 100% ready yet and has bugs. I think you are right about the elevation in general but otherwise hard to tell. What are you using for the APP_ID and productId? Eitan

Hi CT, All you need to do is: 1. Get the data of the selected item 2. Push it into an array with the copied data 3. Assign that array to the copy repeater For example: let copiedData = []; $w("#originalRepeater").onItemReady(($item, itemData)=>{ $item("#copyButton").onClick(()=>{ copiedData = [...copiedData, itemData]; $w("#copyRepeater").data = copiedData; }) }) //this assumes another onItemReady has already been set up for the copyRepeaterHope that helps! Eitan

Hi Tiffany, A percentage based fee can be calculated using the options that are passed into the calculateAdditionalFees() function. The total price can be aggregated from all the line items and multiplied by the percentage. https://dev.wix.com/docs/velo/api-reference/wix-ecom-v2/service-plugins-spis/ecom-additional-fees/calculate-additional-fees For example: import wixSiteBackend from "wix-site-backend"; const FEE = 0.3; //30% fee export const calculateAdditionalFees = async (options) => { let additionalFees = []; const currency = await wixSiteBackend.generalInfo.getPaymentCurrency(); const {lineItems} = options; const totalPrice = lineItems.reduce((total, item)=> Number(item.price)*item.quantity, 0); additionalFees.push({ code: "percentage-fee", name: "Percentage Fee", price: String(totalPrice*FEE), taxDetails: { taxable: true, }, }); return { currency, additionalFees, }; };Note - the above code is untested. Best, Eitan

Hi Rifumo, I'm assuming you are referring to this API: https://dev.wix.com/docs/velo/api-reference/wix-payment/service-plugin-spi/wix-payments/payment-provider/connect-account What I would probably do in this case is use the client_id for username and client_secret for the password. If you have any more info about what you are trying to implement that would be helpful. Best, Eitan

Hi Graham, It's hard to know without taking a look at the site itself. Are the fields visually populated after this code runs? Are these all the fields in the form? Best, Eitan

Hi, The fonts in that section may depend on the fonts you choose in the product page settings (on the page itself). If not, it may only be possible to change when creating a custom product page. Best, Eitan

Hi, thanks! The principle should be exactly the same just that query returns an array of objects so you need to single out an item (items[0] for example) to populate the elements with. const queryResult = await wixData.query("Collection").find(); const item = queryResult.items[0]; $w("#name").text = item.name; $w("#city").text = item.city; Best, Eitan

Hi Daniel, Thanks for being a channel member and purchasing the app! I took a look at the server and we experienced a few crashes over the past two days related to the "Wait for page data" feature. Have you recently begun using this feature? If yes I would recommend disabling it until we resolve the issue or double checking that you implemented the Data Load Widget correctly. If this is not the case, your generator may have briefly stopped working during one of the downtimes (usually only a few seconds). We will follow up on your email tickets as well but I'm posting this for visibility in case anyone else is experiencing a similar issue. Best, Eitan

Hi, This is an API specific thing which means one would have to review the documentation for the API you are integrating as well as the code you have written. Best, Eitan

Hi, I would be helpful to add a description or screenshot of what's not working, error messages you are getting and the url to your site with instructions how to test. Eitan

Hi, great question! I've heard rumors of WixSearch introducing semantic search but that wouldn't hold for a custom search experience. There are a few approaches I can think of when building a custom search experience - 1. Utilizing AI for semantic search: this would include generating vectors for the searchable data as well as the query. Best done with a vector database. 2. Utilizing an API: I'm imagining an API which takes a term and returns possible alternative spellings. You can then query for those alternatives instead of the misspelled word. 3. Handling it internally: For example if the search term doesn't return any results you can break the search term down and query for those parts. So for bok - no results show up so you query for "bo" and "ok" instead. These are just off the top of my head but it's an interesting topic to explore! Eitan

Hi there, The Velo certification comprises of a knowladge test and a project that can be completed here: https://www.wix.com/learn/certification/velo I do a brief walkthrough of the requirements here: https://youtu.be/jla2x0xHeQs?si=MOhM-V2HEcpZGtaB There is also a new developer certification for Wix Studio which follows a similar format: https://www.wix.com/studio/academy/wixstudiocertifications/developer Best of luck! Eitan

Hi James, If you use the Wix Members login widget, this should exist out of the box (for members without a profile picture). If you are trying to build a custom icon, you could utilize the currentMember method in 'wix-members-frontend' to get a logged in members info. With that info you can then use Velo to get the first character from the first and last name and set the text value of a text element as the initials. It would look something like this: import { currentMember } from "wix-members-frontend"; async function setInitials(){ const member = await currentMember.getMember(); const firstInitial = member.contactDetails.firstName.substring(0,1); const lastInitial = member.contactDetails.lastName.substring(0,1); $w("#initialsText").text = firstInitial + lastInitial; } Good luck! Eitan

Hi Pierre, Are you a developer ? This may be a bit of a challenge with no prior development knowledge. You will need to call the goCardless API in a backend file and return a url that redirects to the payment page. This is then passed to the createTransaction function as the redirectUrl.