Hello all, I'm writing to express concern about the restrictions imposed by the new Wix Premium Plans on Velo, to be released on June 5th. A detailed look at the plans shows that a series of new restrictions are imposed by the new plans. There are now restrictive quotas on: Monthly Data Requests (Down to only 10,000 writes per month!) Number of Collections (Only 20 for the intro plans!!!) Number of Collection Items Number of Secrets Stored (only 3 for most plans!!!) Number of Jobs (only 3 for most plans!) Number of Dashboard Pages (only 3 for most plans!!!) And much more! Since Velo (first Corvid) was introduced, such limits were never in place. There were only short-term (minute-long) quotas on backend and data requests. Take a complete look at the PDF provided to Wix Partners. It's disappointing to see that our loyalty to Velo and Wix is being exploited, and I hope that Wix staff reverses course!

Hi all, I've successfully used the job scheduler with site-specific files in the backend. However, I tried to use a backend function contained in a Velo package file with the usual syntax (shown below). @<username>/<package_name>-backend Is there a way to use functions in Velo packages? If so, what should I put in the "functionLocation" param of a scheduled job object? Thanks.

Hello, It appears that the wix importFile API has thrown an "unsupported file extension" for a normal png file - a profile photo retrieved via Google's APIs. I am wondering what the source of this error is, as the file is clearly a png and thus supported according to Wix. It appears that this same import was sidestepped in a Velo example relating to using the Google OAuth flow with Wix Members, where it suggests setting an image element's source as the profile photo rather than uploading the profile photo directly. Any help would be appreciated. Thanks.