A user tknospdr reported an Internal Server Error when trying to edit tag groups under a category, despite being able to manage tags and edit tag groups in admin. The error occurred when clicking the “+ Add required tag group” button, with the browser console showing a 500 error on /tag_groups/filter/search. After troubleshooting with tobiaseigen and checking logs, Moin identified the issue: the site setting max_tag_search_results was set to 3, which caused a validation error in fetch_limit_from_param because the default limit must be between 0 and 3 — but the code expected a minimum of 5. tknospdr confirmed that changing the setting back to 5 resolved the issue. Moin traced the bug to a hardcoded limit in the tag group controller and submitted a fix, which has since been merged into Discourse here. The bug was confirmed reproducible and is now resolved.
When attempting to manage a tag group under a category, I get a generic Internal Server Error pop up window.
I can manage tags under the category, and I can edit tag groups under admin just fine.
It’s just under ANY category if I click the wrench, then click tags, I get the error when attempting to choose a tag group under either:
Restrict these tag groups to this category: or
Require new topics to have tags from tag groups:
+ Add required tag group
I’m not sure where to look to find a log of this error.
We’re supposed to go live with this forum in the next few days, I would be most appreciative if someone can help me quash this in time to debut it.
We really need to be able to require some tags in a particular category prior to launch.
I get: Failed to load resource: the server responded with a status of 500 () ... https://connect.checkinpos.com/tag_groups/filter/search?q=&limit=3
I have 3 different tag groups available, but it doesn’t get as far as showing me the groups available. The pop up happens as soon as I click on the button.
2
[DiscourseJsProcessor] DEPRECATION: The parts property on path nodes is deprecated, use head and tail instead
2 Jun 2:27 pm
Job exception: Unsupported command argument type: FalseClass
Mo 1:47 pm
Job exception: Unsupported command argument type: FalseClass
Mo 3:10 pm
RuntimeError (default :limit is not between 0 and 3) app/controllers/application_controller.rb:1027:in `fetch_int_from_params' app/controllers/application_controller.rb:1020:in `fetch_limit_from_param
9:24 am
4
[DiscourseJsProcessor] DEPRECATION: The parts property on path nodes is deprecated, use head and tail instead
9:33 am
2
[DiscourseJsProcessor] DEPRECATION: The parts property on path nodes is deprecated, use head and tail instead
9:33 am
16
RuntimeError (default :limit is not between 0 and 3) app/controllers/application_controller.rb:1025:in `fetch_int_from_params' app/controllers/application_controller.rb:1018:in `fetch_limit_from_param
I’ll give it a shot in a bit. The other groups are assigned to different categories already and continue to work so I’m worried about not being able to reassign them after destruction and recreation.
Can you roll back to an earlier version of Discourse? I did a backup right before updating this morning.
Thanks for perservering to get to the bottom of it.
