Wix Please Prioritize What You Are Doing - New Dynamic Pages Entry Points Are Useless

Ask the community
,
1

Sorry for the rant but I don’t know who is approving all the new changes and additions instead of concentrating on fixing existing bugs in the system (If you want a list of active and known bugs please let me know, I know some which are 10 months old and I can demonstrate it on recorded videos)

New dynamic page entry points are useless. We are in the business of making custom web applications and sites and we will NOT be using the generic dynamic page prefix, page template that you guys are generating now.

Every time I have to make a dynamic page I need to delete one of the two unnecessary dynamic pages that are generated and delete elements on the one page that I will use along with changing the prefix.

I also need to delete an anchor which is created on my main site menu for this dynamic page.

Repeaters are falling out of balance; Wix Users .register() api is interrupting sign up processes by popping a new “Confirm Email” window which makes custom paid subscription based web apps useless; constant bugs and glitches on Dynamic pages; problems with Routers firing the function twice. I can go on if you wish but I doubt someone will even notice.

Between all this I don’t know how the Corvid development team are setting up meetings and approving allocating resources for building unwanted features instead of concentrating on fixing stuff. Sorry guys its getting really out of hand at this point and if I don’t start making an issue about this I think this will keep continuing. If this is experimenting then it will be experimenting with my career, my teams career and the jobs of all the Corvid developers who do this for a living. Please, the only thing I ask is for you guys to take a little responsibility here.

I raised an issue with the repeater element back in February with Wix Support and received a canned reply which completely overlooked my issue. Again I created a ticket two days ago and also shared the bug with the Wix Partners community on Facebook. This time someone took a look and created this article: https://support.wix.com/en/article/1-april-2020-repeater-height-is-collapsed-and-cannot-be-expanded-in-the-editor

The shocking thing is within 24 hours of making this support article, the issue was resolved. Now why did an issue which was months old and reported by multiple users take less than 24 hours to be resolved once it was actually taken seriously? This can simply mean that no one cares or bothers to look into active issues until we make a complete commotion about it. This cannot suffice as this means everytime I encounter a bug I will need to go complete ham before it will be taken seriously. Bugs should be taken seriously no matter how small or big they are.

EDIT 1: Another bug for the record, probably a permissions issue tied to the dashboard pages issue (Already reported dashboard pages issue for more than a month now) A db collection permission “Write” set to Admin does not work. Even if the user is an admin/owner the wixData.insert() throws an error. When I remove the permission and set to “Anyone” it works. Like seriously, what’s happening?

EDIT 2: Sometimes we have no option to insert a data hook, I know we can code the hook manually on the data.js file but hey since we are talking about watering things down for non technical users then this is another bug to add to the list. I need to refresh the editor 5 or 6 times before the icon appears.

4 Likes
2

X2

3

Well said @Shan, i thought you guys (Corvid Ninja’s and Master’s) would have been consulted on these kind of changes and certainly had impact on identified bugs. After all, you guys consistently use corvid and assist others in this community.
@wix where you have experts in the community, its’ a good idea to sound them out before new launches and follow up on issues.

4

I totally agree, I’ve reported many bugs ages ago, and yet no solution was given, I said it in a previous post, they’re building new buggy features and apps instead of fixing the existing bugs, and I don’t think that’s gonna happen soon.

5

Yes. I agree with Shan.

ALSO … Opening the database collections ‘wix dashboard’ style is very inefficient .

Much more difficult to re-arrange the order of columns because:

  • we cannot drag them easily to a new location.

  • we have to drag them a a couple of spaces at a time

  • if we have over 40, 50 or 100 columns this would take a CRAZY amount of time to arrange columns

The entire window gets in the way when trying to publish. The entire window takes too long to load in general.

Now we need to:

  • wait for window to load

  • add new fields

  • close window

  • click publish button

  • open window again

  • wait for window to load

  • click sync

  • close window

This means we are taking minutes to do something that we used to be able to do in seconds. Time adds up.

I ATTEMPTED to save on time by creating my fields in a database, and import schema as CSV … but this did not work either because when importing fields we only have a limited of field types. For example, I cannot select TAG FIELD from the dropdown list when important. Meaning I STILL have to go back, open the window, wait for it to load, search for the column, change the column type and repeater until I am done changing the columns. Then close window, publish. Reopen window and continue working.

I think you get the idea.

4 Likes
6

@shan I’ve got to disagree with you on this one, at least partially.

Wix is aimed at non-professional designer. Having dynamic page bootstrapped with elements is a good thing for beginners to start working with them. Many users, even Wix partners, don’t know how to work with dynamic pages.

So I believe this is a good feature for most of Wix user. I do agree it would be nice to have the choice between the bootstrapped page or blank when the dynamic page is created

1728×843 169 KB

Wix is a big company and knowing what to prioritize and when can be extremely complex. Many teams need to coordinate in order to deliver a feature, and what you see deliver now might have been planned months ago.

But I do agree that bug management is a must as more and more companies rely on Wix for doing business and it’s critical that we can delivery app with confidence. (And if we can avoid losing hours on glitches that would be also good :stuck_out_tongue: )

7

I understand what you are saying but what is Corvid aimed towards (not Wix)? Is it developers or is it the same audience as Wix or are you mixing both up and trying to cater to both?

When Corvid was launched as Wix Code a few years ago, in the seminar they did (I will try to find the video link) they talked extensively about aiming for developers so it really brings me back to the question, towards whom is the Corvid platform aimed?

While I understand about making things easy and absolutely it is a must, there must be some consideration towards the developer experience rather than a general audience. Please, don’t get me wrong, make things as simple as possible but not at the cost of developer experience and not at the cost of making the platform more heavy and buggy.

Also the screenshot you have put, I do not have that option, never saw it before. Whenever I create a dynamic page it automatcially generates 2 dynamic pages, one with a generic prefix and dynamic item id along with an anchor for the dynamic page on my site menu.

Again, I have no clue of the dynamic entry point and process you show in the screenshot and I have never received a blog, update, any kind of email notification or an update on the Corvid Tips and Updates category on dynamic pages entry points so my post is from my experience of dynamic pages.

Also , I am in complete agreement with you on your 1st point. Keep the new entry points, that is perfect for beginners like you said but please give us an option to start with a blank template like we used to and the option to open the Database Collection inside the Editor as Nayeli points out in her comment.

8

I completely agree with Shan.
The new dynamic pages entry points are a pain for developers. While I can see for a beginner user this might help them, but for us is just a pain…

New database view also. In my opinion wix needs to find the right balance and understand the difference between the developer and a simple user.

What the database view provides on live, for the simple users to use is awesome , you can customize it exactly as you want it for your client to use it and so you might not need to build a custom dashboard if the database view does the job and seems like a dashboard itself.

But when it comes to the editor database we don’t need any of the tools they provide for the live database view… I mean come on . What developer will use list view or card view when working on a database? We all use the table layout which easily allows us to manage things…

I also agree with the bugs reporting and handling. They need to be taken more seriously. We can’t expect big guys to come use a platform that doesn’t have a sufficient bug handling system…

9

Dear Shan and Wix,

I agree with you. I have been asking Wix for over a year now to provide a better solution for bug handling. Let’s take a look at how Facebook platform handles this.

So we need a ‘Bugs’ page which requires you to be logged in. On this page we can see the following:

  • Bugs i have reported

  • Bugs i have subscribed to

  • Report a Bug button

  • List of recent bug reports and the status (with a search bar and filter for Open, Assigned to Dev team, Resolved.

8000×4500 997 KB

Okay, now we need a ‘Report a Bug’ page.

8000×4500 468 KB

In this screen we need the ability to select a site (list of sites should show based on if you email address on the Corvid site matches a Wix account).

Step 1: Select the Wix site you are talking about
Step 2: Select the API / Product in corvid you are talking about
Step 3: Brief Description of the Issue
Step 4: How to reproduce the bug
Step 5: Any additional information & files/images/videos
Step 5: Review your info, and submit

What happens next? Okay. Now it will go to ‘open’ status on the list of bugs, and will be reviewed by a Wix QA/development team and it will now look like this on it’s own dynamic page:

8000×4500 934 KB

The Wix team will take a look, and reproduce or ask more details and depending on the findings will now change the status of the bug report to ‘Assigned’ - which means a Wix developer has been notified and can see the request and will provide an update on the bug report to say “Hi Robert, i have been assigned your bug report and can confirm we are looking into this…blah blah blah” - once it’s fixed, the developer will now move it to the ‘resolves’ state. In all of these stages, the user should be notified which stage their request has been updated too.

Everyone can see these bug reports and comment and upvote them.

Wix keep telling everyone how simple it is to build applications ‘faster and efficiently’ with Corvid by Wix but don’t seem to be showing any results based on their own words. If such solutions (and even harder solutions) can be built in a week or two weeks with Corvid, then why is Wix (who has hundreds of engineers, designers and developers) taking so long to provide such a solution for its users. We need this and we need this fast.

Would you like to hire me to lead this project, Wix? :joy:messing…

Also on top of this, we have been promised a new ‘Coming Soon’ section too which has yet to be delivered. This can be built with Corvid in a couple of days.

We simply need ability to see what is:

  • Shipped

  • In Development (Upvote Feature Needed)

  • In Backlog (Upvote Feature Needed)

  • In Beta

Like i have said before, check out the Webflow Wishlist section. It’s very good.

10

Hey Team:

First off I want to say thank you to everyone for this honest feedback. It is very important that we have a place to openly discuss topics such as this. So again; thank you for your well thought out and detailed comments.

We take these conversations very seriously and many of you have brought up some really great points. There are a lot of items of discussion and a lot to digest here. I want all of you to know I have reached out to several folks on the team and they will be responding.

Again, these are good ongoing conversations and I encourage everyone to continue to provide feedback and engage. The voice of the community is incredibly important to Wix, and we (at Wix) only want to continue making the best products on the planet with you and your feedback in mind.

11

I have already passed the message regarding the sandbox database UX, I will leave this here too
It’s good to have better easy to use UX for a live database but in sandbox database, wix dev should be focusing more on performance than a fancy design
I like the old database layout cause it just works perfectly the new one is looking good but not useful if it takes 5-6 sec just to double-check a field key.

Again I understand @plomteuxquentin point wix is made for a non tech savy people but corvid is for intermediate to advanced user and wix lacks or ignores to provide a better solution for the developer, freelance and agency.

i don’t think building a better bug report system will be helpful i think how wix handle is more important. They need to ship quality code then quantity.

12

I agree with @salman here, performance and functionality should outweigh pretty design when it comes to Dev tools. This is my main reason for using the local editor.

I’ll also admit that as a developer i would prefer an ugly UI that “Does the job” and lets me dev faster than a pretty UI that has performance issues. The Iframe is exactly that, a performance nightmare.

I also however understand @plomteuxquentin s point that its based at not tech savvy users and therefor an easier entry point is a valid reason to add this.

It may seem like i’m sitting on the fence here but more importantly there is a lot of other bugs and issues that require attention prior to the addition of a nicer UI. These would start high on my list with Performance and the mobile editor at the top.

There is also more pressing changes within the Wix Corvid environment that could be implemented first including API’s for hotels, restaurants ETC.

In my personal opinion i think Maybe E/X is the place where developers and Designers would shine? It is a more advanced platform so i think a higher performance development tool and leave the standard editor to the drag and drop users?

In regards to a roadmap, i think Leo at Plutio does an amazing job of this, his roadmap is exactly what would work. With a roadmap we can advise clients on what is the issues and if its worth using a workaround or should we grab a beer and wait.

https://plutio.plutio.com/p/roadmap

13

Hey Adam, Personally i look at the Corvid Masters as more of a resource to you guys. I can only speak for myself here but when time permits i love helping and its a big point on my behalf to be a CM to help the forum grow and the knowledge of Wix Code to grow along side it.

14

Agree with your points, but not the one about the bug system. It’s contradicting. You are saying there is no need for a bug report system? Well…let the bugs and issues keep building up more and more then because the way It’s getting handled right now is not efficient enough bro.

“I don’t think building a better bug reporting system will be helpful” - there is no current bug report system, only Wix Support, who have no clue how to handle these types of questions, who to assign it to or whatever, so how can we build a better one?

“I think how wix handle is more important” - yes exactly, point proven a bug reporting system.

You simply CANNOT handle all of these API and Corvid platform issues by putting a post on this forum. A system needs to be put in place which works similar to Facebook Developer Tools bug reporting system. This is vital man.

However, I do agree with you that Wix need to ship quality code in the first place to prevent these bugs and issues - but let’s face it, with any platform, that’s never gonna happen.

15

@robert-mccormick
“I don’t think building a better bug reporting system will be helpful”
what i mean by that? Is wix is focusing on adding more features quickly than fixing bugs already reported (via support or forums). Bugs occur if the app is not tested sufficiently before the release and i think wix should be focusing more on the testing of the feature before they deploy to everyone. Bug report is helpful to prioritize which bugs need to be fixed first and I understand building a reporting system for public user will be helpful. This bugs like repeater height auto-resizing it’s not hard to find and we simply don’t need a reporting system to know there is a bug. It’s code that is not well tested and being deployed and i think wix should slow down a little bit, fix it and then add a new feature which is well tested before release to beta and also should take a step bug if wix knows there is a bug asap, if the bug is deployed to everyone. so, it doesn’t affect the day-to-day users
TL;DR
This is what i meant by handling the bug? testing it and downgrading the version and re-releasing it again to everyone once it’s fixed.

This just my 2cents to handle the bug #peace

16

@salman-hammed yeah i get you and i agree, i guess we maybe perceive it as two different things lol? Anyway the moral of the story is…extensive testing before releasing and if there is a bug, roll back the change/version.

17

@robert-mccormick @salman-hammed You both are right.

I think what Salman is trying to say is that its no use having a Bug Reporting System if Wix will not take it seriously.

Let’s say we get that but Wix decides to keep focusing on new features. Then the Bug Reporting System will be just pilling up with bug reports.

The ball is in their court, they have to take this seriously. Like Salman said its not difficult to find some bugs but once you find them what do you do? Push it in a ticket internally somewhere and done? I’ve reported a bug 10 months old and its still there today.

18

@digital-edge We will never get a roadmap for bugs/issues like this. 100% because for some marketing people having a bug list for your system means you are showcasing flaws in your product. It makes no sense to be against having a bug/issue list as 100% of saas, game development studios and other development companies have that, its called being transparent but what to do.

19

Hi everyone, thank you for putting the time into this feedback. Wix delivers products to millions of users with different needs and prioritizes accordingly, we’re listening and constantly improving our products on all fronts. Our product team is reviewing this category on an ongoing basis to make sure we take it into consideration in our roadmap and deliver what’s needed the most for our advanced users.
In order to provide better visibility into our roadmap and the status of top requests, we’ll be releasing very shortly a new version of the roadmap + release and updates + wishlist (new) sections in the Corvid Site, that will allow you to upvote requests and understand their current status (in dev, planned, released etc).
We’ve also expanded our Corvid support team in the last quarter and are heavily invested in solving issues that may arise as you go.
As for specific issues noted here, we’ll review and reply. Feel free to add more below if you feel there are critical issues that aren’t being addressed and were not raised in the feature request category.
Thanks,
Ayelet

20

Thank you @ayeletgv

Its a becomes a bit frustrating when you are working ~12 hours in front of your screen and keep having the same bugs for weeks if not months without any clear answers or ETA to a fix. Wix Support does not help majority of the time with Corvid related bugs as they mostly reply back with answers completely overlooking the context of the problem reported.

We are very grateful towards Wix for expanding their Corvid Support Team in the last quarter and also for the roadmap that Wix have been crafting.

I understand that Wix needs to prioritize based on majority but I am also grateful that the product team will review and consider the points mentioned on this thread.