I've got to ask. What is going on? There was a stage where bugs would be assigned or at least responded to and now nothing?
If you gentleman are on a Summer break I can understand this but I've reported several bugs and they are all sat stale?
To highlight just a few that I myself have reported not even mentioning others... I get it documentation is important and AI is the new baby. But what about bugs that have been left to stagnate? I've noticed a few regulars missing lately and when I speak with them this is the issue. Bugs are not being fixed and suggestions for improvement are being ignored in the pursuit of documentation and AI features. I understand there are only the three of you in the Team and Wappler is a big endeavor and ever growing and improving but there really needs to be some attention paid to bugs that are months old.
I'm surprised I have to highlight this. Where has half the Community gone? Why is no one else saying anything? I don't wish to be seen as some moaning irritating User (although many probably consider this the case). I just want to bring attention to it. I'm not saying this to p+ss anyone off either. I'm just running in to the same bugs I had months ago and they are still bugs to this day... New bugs go without a response like the one I posted yesterday and now that will just slowly descend down the topics and in to obscurity (that is how it is beginning to feel).
Nothing but love for Wappler and the effort that goes in to it but I have to say something. Please can we have bug fixes before documentation and new features. PLEASE.
An idea. How about several of us 'power' Users go to work with the Team? We go bug hunting and crush them before they get to the end User... A focus group of sorts. I'm happy to burn inference on solutions to make my own life easier but those fixes are no good if Wappler overwrites them every-time I save something. They need to be integrated in to the core. We have some incredibly talented people within the Community. I'm sure they would jump at the chance to work on Wappler. Much like me I doubt they are in it for money. We just want to help! Aid in alleviating some of the pressure on the Team. I wanted to say this as to end on a positive note that is all (after the above post)...
Some bugs have been open for too long and we should have followed up better. I understand the frustration, especially when people take the time to report things properly.
Most of the work right now is focused on the next major Wappler version, so there probably won’t be another regular full release before that. But we can still release inline extension updates where possible, where we fix bugs.
We’re always trying to balance bug fixes, docs and new features. It’s not always easy: when we focus on new features, people ask about bugs; when we focus on docs, people ask about new features; and when we focus on bugs, people ask when the new things are coming.
Not saying that as an excuse, just explaining the situation.
The reports are still useful and they are not ignored. When an issue is clear and reproducible, it helps us see what can be fixed through an inline extension update, without waiting for a full Wappler release.
Considering the severity of some of the bugs I would have thought fixing them would be prioritised above all else.
It appears that the Wappler strategy is to attract new users. Surely creating a new project and publishing it to a server is one of the first objectives for most new users and this is where I have had the most difficulty.
I have had and continue to encounter issues causing my projects to break due to ssh, ssl and docker and spent weeks trying to get them running again.
Thankfully I have recieved incredible support from the Wappler ambassadors… in particular Cheese and if wasn’t for them I would cut my losses and run.
Please inform us of potential issues ie upgrading to the latest release of docker, (reported back in April) and focus on the basic essential functions within wappler. Thanks
I'm surprised that my post only got a single like (and I'm not after them in any way whatsoever). That speaks volumes in my eyes. A few months back would have had quite a few as there were Users around that really did care about Wappler thus would have probably been a few responses too. What is going on here?
I do understand. I am incredibly frustrated though. I'm looking forwards to Wappler 8 but we are using Wappler 7 for work. At least a few of us actually work for Clients and we go to their offices to sit with them. They see the same bugs time after time when they ask me to make changes for them. And they ask why haven't 'they' (meaning Wappler) fixed that yet as my time runs in to more hours doing the same thing I've done a dozen times as it is still broken.
I hate to be negative I really do. But I REALLY APPRECIATE THAT COMMENT right there! Seems no one else does though... I don't mean the Team. I mean the lack of support this topic has received. Embarrassing. Not for me but for those that don't have the minerals to bring this stuff up on the Community.
My sentiment too! I'm glad I'm not the only one to speak up. Thank you @brad and @JBM
It is with deep concern I am raising these issues!! It is with respect for the product. It is out of concern for the Community. Yet I am the bad one for raising it and trying to change things for the good, and spending hours helping Users here fix issues they should not be encountering.
Wappler is definitely not going anywhere. We are full steam working on Wappler 8, and that is where most of the team’s focus is at the moment. That can sometimes make things look quieter than usual from the outside, but it is not because development has slowed down or because Wappler is being left behind.
Quite the opposite - a lot of work is happening, just not all of it is visible yet.
We are actively working on the next major version, and we are fully committed to it.
Thank you again Teodor. We were used to seeing you guys responding and being around everyday. Those of us that have been here a while at least. It is what made this place incredibly special to us. New Users don't see it these days. We don't see you as regularly any more. That is the concern some of us share. You gentleman are the glue holding us all together.
BUT, issues with Wappler 7 need to be addressed in the meantime. Before we begin the Wappler 8 Beta trials and tribulations... Otherwise problems will just grow exponentially.
Also this is not quite true. We’re online even outside the typical “working hours”, except when we are on a holiday, but even then we closely monitor the community.
(Should i mention i am replying from the craft beer bar, after my working hours are over? )
Like I said sometimes I am wrong and I'll take responsibility for it. I apologise for getting it wrong. It just feels this way, like there has been a shift. Hence my gobby self ranting on and on. Nothing but love for you all and the work you do!
Ahhhhh but that is why we have the love for you!
I'm now going to cease and desist as have said how I feel, outlined my concerns, and called out one or two people. A fine days work in ostracising oneself once again!
Thanks for bringing this up @Cheese I have noticed some major bugs, like the fact that I can’t even switch projects at all. That said, I’ve been so busy with working in Wappler that any bugs that don’t break the app, I just push through cause I can’t take the time to send them all. That’s my fault for sure, but they are so big I assumed someone else submitted them and I was waiting for updates. I’m guessing these are some of the bugs you’re referring to.
I have been kinda MIA from the community due to life being crazy but I still USE and DEPEND on Wappler EVERY day.
Don’t let the lack of replies here discourage you. Some of us have just been busy.
Hopefully life slows down for me soon and I can become a regular here again. That said, I’m busy because of Wappler coding work.
Nice to see you @TwitchBlade! This is exactly what I was hoping to achieve to see some old faces return. Totally understand how life takes over. Thank you for your input and response. We all need to work together here.
I’ve got a list of bugs too. I know they have been brought up before. We need to get on these bugs other wise they will just get carried forward to the new version 8.
Late to the party here, but do want to throw in support for your viewpoint @Cheese . Been around since Wappler 4 days and have always upgraded to the penultimate version of Wappler (5.8, 6.8) at every version completion. 7.9 is the first penultimate release I’m not doing this, simply because I know too many bugs are still running rampant. No hate here, just applied patience. But the viewpoint is indeed valid.
I'm thinking about this topic from a while, and being honest, I was about to create it few weeks ago..
I love to see how Wappler grows but:
Obviously, speaking for myself I prefer fixed bugs and FR applied than a new Wappler version.. It's about the stability of a software I use literally every day and to name a few: (more than 100 created by me and still open) I can't copy and paste an element on the app connect, the tree collapses everytime I drag and drop a component, remote socket url doesn't work..
I understand that new versions are important for the future of the platform, but I would love to see a stronger balance between innovation and maintenance..
Again, with the best intentions here, just a personal opinion and love to see that Wappler is not going anywhere
Don’t think this is about hate at all…it’s about frustration and fear that this product is broken and as a result letting down my paying clients. Surely we all want the product we pay for to work properly?
I apologize for interrupting the conversation, but I’d also like to ask if there will be any response to my bug report. I spent several days trying to figure out the problem and think I’ve found the cause. The fix is very simple. I’ve fixed it in my own project, but Wappler now tries to revert the changes every time I load it. This creates uncertainty, which is a major issue if you’re using Wappler for more than just a toy. If there’s no response to the issue I’ve found, it demotivates me from looking for bugs, and so on.
I really like Wappler, but I’ve encountered bugs on more than one occasion that prevent me from using Wappler in serious projects. Once, a bug was fixed promptly, for which I’m very grateful. Sometimes I choose an alternative approach, and that compromise allows me to continue working. But when there’s no obvious alternative and the bug is ignored, it’s frustrating. I understand that developing Wappler is no easy task, but taking advantage of our free efforts to find bugs is a big help. I think it would be a good idea to create a queue of reported bugs that are scheduled to be fixed.
Hi Freemath totally agree with everything you said, howver what does concern me most is your comment
I really like Wappler, but I’ve encountered bugs on more than one occasion that prevent me from using Wappler in serious projects.
I also love Wappler and have registered as a pro user with the cost implications incurred, however I have found, increasingly, that using Wappler for professional projects is becoming less of a viable proposition, what do you use for your professional projects?
Someone here brought up the fact that Wappler is dying. That would be a shame. Wappler has a very sound concept—it may not be as flashy as no-code systems, but it’s reliable, unlike no-code systems. It’s also ideal for implementing AI. For me, Wappler is a convenient wrapper around code. On the one hand, you can write code, and on the other, manage the project in a graphical interface. Since it’s full-fledged code, AI can easily manage it. I think this is the best solution imaginable. But bugs can ruin any tool. For example, I tried using AI—the paid version was too expensive, and the local version didn’t work because of bugs. I spent some time on it and have put it on hold for now. And it’s great that Wappler can work with AI, or without it. I can work in the graphical interface, or I can give ChatGPT a task, and it will write the API and HTML for me, which almost always integrate perfectly into my project. That’s exactly the kind of development tool I was looking for when I found Wappler. But when Wappler starts messing up the project, it really worries me—I’m afraid that at any moment the project could crash and I’d be stuck….
and if wasn’t for them I would cut my losses and run.
