Proper Process to Report Bugs?

[Bob Carver]

Though I've had TNG for years, I'm fairly new to TNG Wiki & this forum. Simple question: what is the appropriate means by which to report TNG bugs. I'm versed in PHP and SQL, so I'm generally able to examine code before throwing a "bug found" flag. Though I have often had email conversations with Darrin, I don't want to presume I should contact him directly if, in fact, there is an agreed upon process. Thanks!

[ADC]

I'm not aware of any particular process, but others may correct me.

I do know Darrin is open to email queries, as you have said.

I would suggest a sensible process would be to post any suspected bugs here (or to the email list, which I don't know anything about, sorry) and see if anyone else has the same problem or can reproduce the bug. If it turns out there is an actual bug, then contact Darrin directly. However, this is just common-sense advice rather than any defined process, so feel free to ignore it 😁

[Rob Severijns]

7 hours ago, ADC said:

I would suggest a sensible process would be ......

I agree

[theKiwi]

If you suspect you've found a bug you should report it to Darrin directly by eMail.

Do NOT post it here - Darrin doesn't monitor this forum at all.

Roger

[Bob Carver]

Thanks y'all. I have in the past sent such to Darrin directly. Just "checkin 'in" in case another process has been in play

[tngrlkrz]

7 hours ago, theKiwi said:

Do NOT post it here - Darrin doesn't monitor this forum at all.

I agree ultimately Darrin be the direct contact, but I also see nothing wrong with 'checking in' on this forum to see if others experience the bug or make other users aware of it.   That way no surprise to forum readers should they encounter the bug.  They know eventually Darrin will deal with it.

Ron

[Rob Severijns]

Exactly my thoughts too Ron.

[Bob Carver]

I have no problem posting bug info - checkin' in - but would "Questions and Answers" serve as appropriate landing pad? 

 

Here's what I sent Darrin:

Ref: General Settings -> Miscellaneous

Save & Stay option would seem not to refresh - at the very least - the two "What's New" settings.

1. Start with Days = 0 and Limit = 20
2. config.php properly shows
   $change_cutoff = "0";
   $change_limit = "20";

--------------------

3. Change Days to 10 and Limit to 5
4. Click Save + Exit
5. config.php properly includes
   $change_cutoff = "10";
   $change_limit = "5";
6. Return to General Settings > Miscellaneous
7. Properly, Days = 10 and Limit = 5

--------------------

8. Change Days to 9 and change Limit to 8
9. Click Save + Stay
10. Reopen Miscellaneous…
11. Days still shows 10 and Limit still shows 5
12. Yet config.php has
    $change_cutoff = "9";
    $change_limit = "8";

--------------------

13. Click Cancel and return to Miscellaneous…
14. Properly, Days now shows 9 and Limit shows 8

--------------------

15. Change Days to -5 and Limit to A (obviously no editing for sensible values, but…)
16. Click Save + Exit
17. config.php properly has
    $change_cutoff = "-5";
    $change_limit = "A";
18. Return to Miscellaneous
19. Properly, Days = -5 and Limit = A

--------------------

20. Change Days to 99 and Limit = -88
21. Click Save + Stay
22. config.php properly has
    $change_cutoff = "99";
    $change_limit = "-88";
23. Return to Miscellaneous
24. Improperly displayed: Days = -5 and Limit = A

--------------------

25. No changes made
26. Click Save & Stay
27. config.php has
    $change_cutoff = "-5";
    $change_limit = "A";
28. Improperly, but not unexpected by this time, Days = 99 and Limit = -88

--------------------

29. Changed Days = ?? and Limit = !!
30. Clicked Save + Exit
31. config.php, as expected, has
    $change_cutoff = "??";
    $change_limit = "!!";
32. Return to Miscellaneous
33. As expected, Days = ?? and Limit = !!

Conclusion: Save + Stay has a flaw (though perhaps only in regard to Days ($change_cutoff) and Limit ($change_limit)

[Bob Carver]

Epilogue: Symptoms were real, but the problem was resolved after fiddling around with the underlying PHP release. 🤪