Groups Dropdown Isn't Functioning

[tempsaint]

Describe the bug
I've added a Group to a service body but when I try to view it to edit it the dropdown box is greyed out. I can see that the group exists by going to a service body and trying to include the group along with volunteers.

What version of Yap are you running?
Running 4.4.2

What PHP version are you running?
8.2

Is this happening in a live environment or a test environment?
Both live and test environments

Is this causing the system to be degraded in a way that makes in unusable?
Not really but possible degradation of abilities.

Did this happen on prior versions to the one you are running (if so what version)?
We don't have a prior version

To Reproduce
Steps to reproduce the behavior:

1. Login to Yap
2. Go to Groups
3. Select the "root" service body which is what I selected when I created the group.
4. Try to use the dropdown to see the group.

Expected behavior
I expect to see the Group I created and be able to add volunteers to it.

Screenshots

[dgershman]

Are there any javascript errors?

[tempsaint]

Absolutely nothing in the console.

[dgershman]

Please email your database and config.php.

…

On Tue, May 20, 2025 at 8:01 PM Adam Hechler ***@***.***> wrote: *tempsaint* left a comment (bmlt-enabled/yap#1339) <#1339 (comment)> Absolutely nothing in the console. — Reply to this email directly, view it on GitHub <#1339 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAOD3O6M3Y6QH3G26DWINUD27O63ZAVCNFSM6AAAAAB5RZEDZKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQOJWGA4TAMZUGM> . You are receiving this because you commented.Message ID: ***@***.***>

[dgershman]

I could not reproduce the issue you are having. It works fine for me.

[tempsaint]

So what could be the issue? Something with our hosting? I've tried from desktop and mobile. I've tried on our primary yap and demo/test instance and got the same result. If it's not our Yap DB or config, and not js errors, what could it be?

…

On Tue, May 20, 2025, 9:35 PM Danny Gershman ***@***.***> wrote: *dgershman* left a comment (bmlt-enabled/yap#1339) <#1339 (comment)> I could not reproduce the issue you are having. It works fine for me. — Reply to this email directly, view it on GitHub <#1339 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJEMRBPBNL4BECOTQVR7JA327PJ57AVCNFSM6AAAAAB5RZEDZKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQOJWGIYDONBXGM> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[dgershman]

can you get me a login?

[dgershman]

I've identified the issue. This is a type handling inconsistency between different database versions (MySQL 5.7 vs MariaDB 10.6) that affects how numeric fields are returned in JSON responses.

The problem occurs because:

1. In MySQL 5.7, numeric fields are preserved as integers in JSON responses
2. In MariaDB 10.6, these same fields are being converted to strings
3. This causes the group dropdown to not function properly because the type comparison fails

I've implemented a fix that ensures consistent type handling by:

1. Explicitly casting numeric fields to integers at the database repository level
2. Maintaining type consistency in the controller response
3. Handling the differences between MySQL and MariaDB in how they handle numeric types

The fix has been applied to both the GroupController to ensure proper type handling throughout the application flow. Changes to ConfigController haven't been made yet, since there could be other side effects.

The issue will be fixed in Yap 4.4.5

[dgershman]

please test