Question Configuration problem after an upgrade from K6.3 to K6.4.2

The issue happens on sites which have the cache enabled, there will be a fix for that in the next release (K6.4.3). The JSON in the table #__kunena_config is broken is the reason why it show the default value.

anonymous01 wrote:

... frankly, I simply don’t have the time for this. ...

Me neither and although I faced this issue myself but worked around it after the upgrade, I took the time to do a deep dive into this issue: Took me 4 hours of my time that are non-billable but was able to reproduce, find the root cause and produce a fix that is merged into the new (to be released) version. Thankful for the people that put in their spare time and helped test this fix because that is something I as a developer cannot / should not do.

Initially after reading this thread I thought: why bother... but rolled up my sleeves anyway.

You are welcome!

Created a separate topic with the original question here: www.kunena.org/forum/k-6-4-0-support/168...5-3-and-kunena-6-4-2

 

ruud wrote:

Thankful for the people that put in their spare time and helped test this fix because...

 

Really? Well, okay. But unlike you, I have a different view of the testing process. Testing that fails to catch an elementary bug during release preparation, forcing me to spend two weeks (check the topic's start date) convincing the development team that the bug actually exists—this isn’t testing, it’s a mockery of development. So, I can’t share your enthusiasm. Nevertheless, I wish you further success.

Pinkeltje wrote:

Unable to reproduce. 

 

rich wrote:

I spent most of the afternoon today testing upgrades. I never encountered the configuration error. The error did not occur in pre-release testing either.

 

 

xillibit wrote:

The issue happens on sites which have the cache enabled...

anonymous01 wrote:

Really? Well, okay. But unlike you, I have a different view of the testing process. Testing that fails to catch an elementary bug during release preparation, forcing me to spend two weeks (check the topic's start date) convincing the development team that the bug actually exists—this isn’t testing, it’s a mockery of development. So, I can’t share your enthusiasm. Nevertheless, I wish you further success.

When you reported the issue, I spent several days trying to reproduce the error, but unfortunately I wasn’t able to. Sometimes, these kinds of bugs are incredibly elusive.
Thankfully, @Pinkeltje was eventually able to identify the cause, after also putting in significant time and effort.
I understand your frustration, still, I believe it’s not entirely fair to say that we don’t test enough. Everyone involved is genuinely trying their best to ensure that Kunena remains stable and reliable.

I think we’ve now covered all relevant points, so I’ll consider the topic closed.

No problem. By the way, I noticed that today I can’t log into the Kunena support forum from my IP. And, of course, it’s just a coincidence, I had no doubts. Bypassing this restriction isn’t hard for me, but I won’t bother doing it in the future: I like Karkocha, but the clownish antics of a programming team that can’t test their code properly and takes pride in that incompetence are dull. Please delete my account on that forum; I won’t need it anymore.