General Request regarding bugs

Beta
#1

One of the pain points I have with Pro is the lack of updates to “stable releases”.

There are bugs in Pro 5.1.5 that have been around for more than a year. There are many but one example of this would be the Form Element not working with Ajax for Gravity Forms. This was reported in a thread in Feb '21 and again in October '21. To have this broken for more than a year seems crazy. There are many more examples of small things that should be resolved but just ignored.

Form AJAX option has no effect with "Form Integration" - classic ok - Feb 21
Form Integration - Gravity Forms Ajax not working - Oct 21

It would be awesome if there was a schedule to update and resolve bugs in the current version of Pro as they arise.

By example, Avada has a patcher where they release patches for bugs in the current version of the theme even if the new version is in development. (Yes, I maintain some legacy sites that were built with Avada).

5 Likes
#2

One of my pain points is the bugs that have been in the sliders since they were released and not fixed. It’s a bit embarrassing when I try to make a professional site for a customer and something so basic as a slider seems to have a life of it’s own.

4 Likes
#3

Indeed, periodic maintenance updates would be welcomed. I’m curious to know why there always is this long period of radio silence after a major update has been released.

2 Likes
#4

Frankly with me joining we are in a bit of transition period so a bit of this might be growing pains. Internally we have talked about the need to push out updates quicker, smaller releases, with less time in-between releases so it is definitely a priority for our team. After we are through this release you’ll see this come into play and I thank you all for your patience in this period. Sliders have been on our radar for some TLC. From our audits some of these older bugs will be gone, but please always send us your thoughts on what needs to be prioritized just like this.

4 Likes
#5

I appreciate the feedback. I don’t really see this as a current problem and certainly don’t think the blame is with the transition. This is an ongoing issue since as long as I’ve been using the theme.

When there are bugs and issues on the “stable release” while you are in development of the next cycle, the bugs and issues don’t get resolved.

What we need is for the current branch to still have bug fixes sorted out while you are in development of the next release.

3 Likes
#6

We hear you all and plan on doing better. Not much more to say beyond that.

As of right now, being in the middle of this extended cycle there is nothing we can do at the moment, which is why our top priority is getting this beta out the door as quickly as possible and buttoning things up with this feature set so that we can begin working to clean up lingering issues and implement a “clean branch” of the codebase that can always be ready to receive hotfixes / bug updates as needed.

Thanks for your understanding and patience while we continue to work through this cycle.

2 Likes