Should Themeco's bug fixing policy be improved?: Confirmed bug reported 18 days ago –that can be fixed in seconds– still present in last release (and its subsequent 6 point releases)

Support
#1

Hi,

Your support staff confirmed the existence of a bug I reported 18 days ago (Sep 27, 2018) in this topic (#44167). At that time I enclosed full information about how to fix it: the file affected, the exact line and what to do –only 2 double quotes deletion–. It is something that anyone can do in a matter of seconds. To my surprise I found out that the bug was not fixed in the Pro 2.3.0 release on Oct 4 nor was in the subsequent 6 point releases –the last one on Oct 12–.

I can understand that –because of its nature– it is a low priority bug and that you may have been focusing on solving the bugs related to the new introduced features but still, for a theme theoretically aimed towards pro users, and being a bug that your developers can solve literally in seconds, I think there is something that should be improved in Themeco’s bug fixing policy, even more if those bugs have been tested and confirmed by Themeco’s own staff.

This is not an isolated case as I have reported a code improvement to achieve HTML spec compliance –fast and easy to implement– that has not been addressed in the recent releases either, in topic 44416.

I understand the effort Themeco puts in each release in terms of new features –which I love BTW, bravo for such a great job!– but I think the reported and confirmed bugs –specially if they can be fixed in seconds– must be addressed in each release even if they are not related to the shiny new features.

Best regards
Diego

#2

Hey Diego,

Thank you for your all your feedback. I do agree that syntax errors needs to be fixed fast. Improvement or feature requests however needs time to consider many factors in product development and there’s no guarantee that they will be surely implemented.

I’ll label the previous report of my colleague as a bug. Maybe that’s why our development team overlooked the issue.

Please stay tuned for updates.

Thanks.

#3

Thanks @christian_y for your prompt response.

Please, I’ve just recalled there is another bug I reported that I think it hasn’t been addressed yet: topic 44222. Please notice that this is not an improvement, it is a bug as it’s causing invalid HTML being output.

Thanks.

#4

Thanks posting. I’ll follow up regarding that case as well.

#6

Thanks @christian_y!

#7

Thank you for your understanding :slight_smile:

#8

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.