This page is to coordinate fixing regression bugs to help with the release of 28.0
Semi-related: How to Have Fewer Bugs in Tiki (If we systematically avoid regressions, we solve a big part of the problem).
Priorities
- Regressions from 27x to 28x
Non-priorities
We can do this after 28.0
- General bugs
- Bugs on new features
- Regressions from other versions (26x, 24x, 23x, 22x, 21x, 20x, 19x, etc.) to 28x. Why?
- We must focus
- Our testing infrastructure is designed for 27x to 28x, and it adds work to set up other versions (like 24x to 28x)
- Regressions from 26x to 27x should have been solved as part of the 27x release process. If you didn't handle it there, it could mean that it wasn't important enough.
How to report regressions
- They should appear on the current page, either as wiki text (make sure to indicate your name so dev can coordinate with you), or Add a wish with the "Regression from 27.x to 28.x" category
- The ideal case is to contrast behavior between a 27x *.tiki.org site and Pre-dogfood servers for Tiki 28 release process
- If you can't contrast on *.tiki.org
- Add a show instance to a wish
- If you can't demonstrate on a show instance (ex.: it only happens on your infra, so perhaps a bug for a different OS or dependencies): we can look at this if you supply out developer with SSH access to a system where it works with Tiki27 and SSH access to a system where it doesn't work with Tiki28.
- If you are not sure it's a bug, and want to discuss first, you can ask on https://gitter.im/tiki-org/community
- But don't abuse this. And it remains your responsibility to add the regression in a way where it appears on the current page.
Regressions reported in wiki page
2024-10-31: https://themes.tiki.org/ is now 28x, so you can test there now.
2024-11-11: https://doc.tiki.org/ is now 28x, so you can test there now.
(Add your issue here)
| #Code | Feature (option) | Issue(s) | URL(s) | Submitted by | Volunteered to solve | Status (Open, Pending, Solved) | Merge request/Comment | In 28.x ? | |
| 1 | Trackers | Submitting an issue on the Make-a-wish page on dev.t.o fails with the error message "The following mandatory fields are missing Category ". | https://copydev.tiki.org/Make-a-wish | Rodriguez Nyiringabo | King Kambale | Open | To unblock us from receiving bug reports the mandatory flag was removed from the Category field ID 43 (temporary workaround) | ||
| 2 | Wiki | Adding object permissions (aka individual permissions) to a wiki page (tested on HomePage, and a Test page), has no effect on the object (global perms work, confirmed by Benoit, see the Matrix/Gitter discussion on https://tki.sk/iz0Tfm ) | @luciash d' being 🧙 | @Adrien | Pending | https://gitlab.com/tikiwiki/tiki/-/merge_requests/6649 | |||
| 3 | Trackers | Wishlist items on dev.t.o cannot be viewed anymore (might be because of the failure on the field related to show.tiki.org) which is rendering a fatal error (Error 500) | @luciash d' being 🧙 | Rodriguez Nyiringabo | Solved | The issue was due to insufficient balance in the account at the hosting provider of shw2.t.o | |||
| 4 | Record RTC | Record RTC requires https connection over SSL (right-hand module) | https://dev.tiki.org/ | marclaporte | Joseph Ushindi | open | |||
| 5 | Wiki pages | Typed property Search_Formatter_Builder::$formatterPlugin must not be accessed before initialization | https://doc.tiki.org/Documentation | marclaporte | open | https://gitlab.com/tikiwiki/tiki/-/merge_requests/6461 | |||
| 6 | Trackers | After the issue #1 been fixed and test the item creation it throws array_diff_key(): Argument #1 ($array) must be of type array, string given | https://copydev.tiki.org/Make-a-wish | Rodriguez Nyiringabo | King Kambale | Open | |||
Open
Pending
Closed
EvoluData
EvoluData will assign its team of developers to attempt to address all responsibly reported regressions from 27x to 28x. The goal is that no Tiki site admin is blocked from upgrading from 27x to 28x because of a regression. This applies to all non-deprecated and non-experimental features.