Lately it seems to me that in the race to add new things, a lot of what worked before has been broken. And it is clear that there is probably not enough attention to support and obvious problems are not resolved for quite a long time.
I don’t know about you, but I’m at a bit of a dead end right now - in my projects some things simply cannot be modified or I have to edit the same thing over and over again. Maybe the team should take a break and fix the most critical bugs?
I just miss deadlines and spend a lot of unpaid time dealing with these bugs, I wonder if this is just my problem?
I personally have no problem with the rate of new features. I just think that the new features being introduced over the last couple years with the exception of the fantastic Expression Builder have been very niche market. I would like to see more focus on front end features as there has been nothing new there for a couple years other than dark mode toggle.
I find as long as I keep my projects and Wappler up to date each week I have very few problems. Perhaps because I haven't had a need for any of the new features for quite awhile my projects are using pretty stable versions of older features. And the ones that did come up were fixed very quickly.
Is it mostly newer features you are having issues with?
We run the latest version of Wappler across our Projects and have no issues whatsoever even with the most complex of Actions and Layouts. Wappler is the best it has ever been in our eyes. Blisteringly fast, great rendering for SEO, build and deployment on demand, functionality, security, and stability. We have no complaints nor require any fixes as it stands (6.6.0), Ubuntu/Node/Docker.
Yep, much the same here apart from the AutoComplete issue which was partially addressed in today's update but isn't quite sorted. Hoping for a mini-update ASAP.
For example, due to a problem with the new filter editor in DataView, it is impossible for me to either fix old ones or create new filters normally. The old one worked great and I still didn’t understand what the point was in changing it.
Or else - quite a long time ago they added work with arrays to SC - this is of course good, but why haven’t they done so all this time so that their structure for working with fields in expressions is normally visible on the front?
Have you submitted Bug Reports for the issues you are experiencing Vladimir? If so give them a friendly bump, and if not then create reports for them. Without the Bug Reports it is really hard for the Team to keep track when they are in threads and replies in numerous topics.
The worry, of course, is when something breaks but you don't know it has. The autocomplete No Results issue caught me out because I didn't realise it was affecting existing projects until a user pointed it out. I know it's hard to be sure nothing will break, and there are enough Wapplers and Wappler projects out there to hopefully flag up issues quickly, so we should be OK.
So I ran into an issue with the filters as well and it's because I do a lot of editing directly in code view. This leads the meta config file that Wappler creates to not have the proper fields for the filter editor.
Is it possible you are editing in code view as well?
I also often find it easier to do things with code rather than with this weird visual expression editor. But the whole problem is that in the new version they simply deprived us of the ability to set an expression simply with code - and this ugly editor does not have access to the variables on the page and generally sometimes behaves logically unpredictably. It would be nice to be able to simply disable it.
